Description

Saito Navi gathers several customer engagement modules for WooCommerce
behind a single floating button (gear icon, corner of the screen):

Cookie consent — GDPR banner, Google Consent Mode V2, preferences
modal, logo auto-detected from the site identity if no URL is set.
Accessibility — language switcher (WPML-compatible, falls back to
GTranslate if WPML is absent), text size, high contrast, enlarged
cursor, underlined links.
Sticky add-to-cart — a panel that follows the visitor on the
WooCommerce product page, works with simple and variable products, a
keyboard-accessible swatch selector, compatible with WCBoost Variation
Swatches, and a custom CSS selector setting for themes not covered by
the built-in fallback chain.
Stories — up to 4 video bubbles per product (YouTube or an
uploaded MP4), a dedicated tab on the WooCommerce product page, a
desktop panel with a pure-CSS phone mockup (no external image), and a
mobile full-screen stories-style view. Displayed by default after the
product gallery, or wherever you like via the [navi_stories]
shortcode.

Built from the ground up to welcome new modules without touching the
core: each module registers itself and talks to the central button
through a generic event, and no module knows about the others.

Everything is configurable from the Back Office (Navi menu): colors,
corner radius, button position, and for each module its own “Show on
desktop” / “Show on mobile” setting.

Sibling of Navi for PrestaShop
— same name, same spirit (one hub rather than independent widgets), two
separate implementations adapted to each ecosystem.

External services and embedded content

Google Consent Mode V2: the Cookie consent module pushes the
visitor’s choices into window.dataLayer (the standard Google Tag
Manager/gtag.js mechanism). The plugin itself never sends any request
to a Google server — the site must already have gtag.js/GTM in place
for this signal to be used.
YouTube (“no-cookie” mode): the Stories module displays configured
videos via youtube-nocookie.com in an iframe, only on product pages
where a YouTube story has been configured by the site administrator.
See the YouTube privacy policy.
YouTube thumbnails: when an administrator sets a YouTube story
without a custom preview, the plugin makes a server-side HEAD request
(3s timeout, no data sent beyond the request itself, no account or API
key involved) to img.youtube.com to check whether the HD thumbnail
(maxresdefault.jpg) exists for that video, falling back to a lower
resolution (hqdefault.jpg) if it doesn’t — this avoids storing a
broken image URL for videos (mostly YouTube Shorts) that only have the
lower-resolution thumbnail. This request only happens when a product is
saved with a YouTube story configured, never on a visitor’s page load.

Screenshots

Navi > Navi, General tab: floating button position, plugin language,
appearance (colors, corner radius). — Navi > Navi, General tab: floating button position, plugin language, appearance (colors, corner radius).

Cookie consent tab: banner settings, with concrete Google Tag Manager /
Consent Mode V2 setup instructions. — Navi > Navi, General tab: floating button position, plugin language, appearance (colors, corner radius).

Blocks

This plugin provides 1 block.

Navi Stories

Installation

Upload the saito-navi folder to /wp-content/plugins/, or install directly from Plugins > Add New.
Activate the plugin from the Plugins menu.
WooCommerce must be installed and active (required for the Sticky add-to-cart and Stories modules; the Cookie consent and Accessibility modules work without it).
Configure the modules from the new Navi menu in the Back Office.

FAQ

Is WooCommerce required?: The core and the Cookie consent / Accessibility modules work without
WooCommerce. The Sticky add-to-cart and Stories modules are tied to the
WooCommerce product page and therefore require it to be active — a
notice is shown in the Back Office if WooCommerce is missing or inactive.
Where are uploaded MP4 story videos stored?: Story preview videos are picked or uploaded through the standard
WordPress Media Library (the same picker used everywhere else in the
admin), so they’re stored like any other media file, never inside the
plugin folder — the latter can be overwritten on every plugin update,
unlike the uploads folder.
Does the Accessibility module’s language switcher work without WPML?: Yes: if it detects the GTranslate plugin installed, it falls back to it;
otherwise the language switcher simply doesn’t appear (the other
accessibility settings remain available).
Does the sticky add-to-cart work with my theme?: A fallback chain of CSS selectors covers standard WooCommerce markup and
the most common themes. If your theme has an unusual structure, a
“custom CSS selector” setting per field (price, name, image) is
available under Navi > Cart.
Does the sticky add-to-cart work with block themes (Site Editor)?: Yes: WooCommerce’s default block-based Single Product template still
renders the classic variations form under the hood, which the sticky
cart already detects. The one exception is WooCommerce’s own
experimental “Add to Cart + Options (Beta)” block (fully JavaScript-
driven, no classic form) — not supported while it remains in beta.
Can I place the story bubbles as a block instead of a shortcode?: Yes: the “Navi Stories” block does the same thing as [navi_stories],
with a “Product ID” field in the block settings.
Can I control where the story bubbles are displayed?: By default they appear right after the product gallery. Use the
[navi_stories] shortcode to place them anywhere else instead (post
content, a page builder, or a theme template) — add
id=”123″ to target a specific product, or leave it empty to use the
current product page. To avoid showing the bubbles twice, turn off
“Afficher automatiquement” under Navi > Stories if you use the shortcode
exclusively.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“Saito Navi” is open source software. The following people have contributed to this plugin.

Troteseil Lucas

Translate “Saito Navi” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

0.7.2

Stories now integrates with the companion Navi FAQ plugin when it’s
active: both share a single “Navi” panel on the product edit screen
(one internal tab per feature) instead of each adding its own separate
entry under “Product data”. Without Navi FAQ, Stories keeps its own
“Stories (Navi)” tab under “Product data” as before.

0.7.1

WordPress.org review: replaced every inline <script>/<style> block
with wp_register_script()/wp_enqueue_script()/wp_localize_script()
and wp_enqueue_style()/wp_add_inline_style() (hash-preserving
referer field, Google Consent Mode injection, admin dashboard tabs,
Stories settings live preview, Stories product tab). No behavior
change.
Documented the wp_remote_head() call to img.youtube.com (YouTube
HD thumbnail availability check) in the “External services and
embedded content” section.

0.7.0

Story preview video is now picked directly from the WordPress Media
Library (restricted to MP4 files) instead of a raw file upload field —
no more dedicated upload folder to manage or clean up on uninstall.
Fixed: YouTube fallback thumbnail could stay broken for Shorts
(vertical videos without a maxresdefault.jpg) — now falls back to
hqdefault.jpg automatically.
Expanded PHPUnit test suite (Stories validation, Accessibility language
fallback, module registry).

0.6.0

“Navi Stories” block (Gutenberg), alongside the [navi_stories]
shortcode.
Onboarding: one-time redirect to Navi > Navi after activation, “First
steps” card on the General tab.
Verified compatibility with WooCommerce’s default block-based Single
Product template (see FAQ).

0.5.0

Shortcode [navi_stories], configurable bubble appearance (solid or
gradient border, size), WordPress.org submission readiness.

0.4.0

New Stories module: product video bubbles (YouTube/MP4), desktop
panel, mobile full-screen view, appearance settings under Navi >
Stories.

0.3.0

Appearance parity with Navi for PrestaShop: configurable corner
radius, per-module visibility by device, plugin logo as the admin
menu icon.

0.2.0

Sticky add-to-cart module: simple and variable products, swatch
selector, custom CSS selector settings.

0.1.0

Initial release: core (3-state floating button), Cookie consent and
Accessibility modules.

Description

External services and embedded content

Screenshots

Blocks

Installation

FAQ

Is WooCommerce required?

Where are uploaded MP4 story videos stored?

Does the Accessibility module’s language switcher work without WPML?

Does the sticky add-to-cart work with my theme?

Does the sticky add-to-cart work with block themes (Site Editor)?

Can I place the story bubbles as a block instead of a shortcode?

Can I control where the story bubbles are displayed?