| 开发者 | lucastsl |
|---|---|
| 更新时间 | 2026年10月20日 23:47 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[navi_stories]
shortcode.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-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.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.saito-navi folder to /wp-content/plugins/, or install
directly from Plugins > Add New.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.
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.
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).
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 Saito > Navi > Cart.
Out of the box it reads colors from WCBoost Variation Swatches if that
plugin is active. For any other theme or plugin displaying its own
per-variation thumbnails (image or color), set the "Sélecteur CSS de la
vignette de variation" field under Saito > Navi > Cart to a template such as
#{value} (with {value} replaced automatically by each variation's
value) pointing at your theme's markup — an image found inside is used
first, otherwise its background color.
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.
Yes: the "Navi Stories" block does the same thing as [navi_stories],
with a "Product ID" field in the block settings.
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 Saito > Navi > Stories if you use the shortcode
exclusively.
<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.wp_remote_head() call to img.youtube.com (YouTube
HD thumbnail availability check) in the "External services and
embedded content" section.maxresdefault.jpg) — now falls back to
hqdefault.jpg automatically.[navi_stories]
shortcode.[navi_stories], configurable bubble appearance (solid or
gradient border, size), WordPress.org submission readiness.