Zum Inhalt springen

FAQ

Dieser Inhalt ist noch nicht in deiner Sprache verfügbar.

Yes. Peek requires an active WooCommerce installation and does nothing without it.

On the shop page and product archive loops, categories, tags and taxonomies, after each product. Optionally also in the related-products and up-sell loops on single product pages. It does not change the single product template itself.

Peek’s own front-end script is vanilla JavaScript with no jQuery dependency, deferred and loaded in the footer. So that variable products work the moment the fragment loads, Peek enqueues WooCommerce’s bundled wc-add-to-cart-variation script (which itself uses jQuery) on pages where the quick view can appear, then re-initialises the variation form on the injected markup.

No. The modal is fully hidden until opened and scrolls internally, so opening it overlays the page instead of reflowing existing content. There is no Cumulative Layout Shift.

Yes. It uses role="dialog" with aria-modal, traps focus while open, closes on Escape or a backdrop click, and returns focus to the trigger on close. The icon-only button style keeps its label as an accessible name.

The featured image, gallery (with a configurable thumbnail count), title, SKU, price, stock status, short description, the native add-to-cart form (including variable products) and a link to the full product page. Each part is an independent toggle, and empty fields hide automatically.

Yes, if the add-to-cart toggle is on. Variable products use WooCommerce’s own variation script, so options, price and availability behave inside the modal just as they do on the product page.

Can I place a trigger outside the shop loop?

Section titled “Can I place a trigger outside the shop loop?”

Yes. Use [peek_quick_view id="123"] (or its alias [peek]) anywhere, with optional text and style attributes. Peek loads its assets on any request where a shortcode is present.

How do I make the trigger overlay the product image?

Section titled “How do I make the trigger overlay the product image?”

Set button placement to On the product image on the Peek settings screen. The trigger then appears on hover and keyboard focus. With reduced-motion preferences, it stays visible rather than fading in.

Can someone preview an unpublished product through the AJAX endpoint?

Section titled “Can someone preview an unpublished product through the AJAX endpoint?”

No. The quick-view endpoint is open to guests, but it only returns published products, or ones the current user is allowed to edit. A draft, pending or private product cannot be previewed by guessing its ID; the request returns a 404 with your “product not found” text.

Can I override the modal template in my theme?

Section titled “Can I override the modal template in my theme?”

No. Peek renders the loop button, modal shell and product fragment from its own templates/ folder; copying them into yourtheme/peek/ has no effect. To change the output, use the template action hooks (peek_quick_view_before_cart, peek_quick_view_after_cart, peek_quick_view_content_end, peek_quick_view_modal_dialog_start) or restyle with the --peek-* CSS custom properties. See Configuration.

Where are settings stored, and does deleting the plugin clean up?

Section titled “Where are settings stored, and does deleting the plugin clean up?”

All settings live in a single peek_settings option, there is no custom table and nothing is sent to an external service. Deleting the plugin from wp-admin runs the uninstall routine, which removes peek_settings and peek_db_version. WooCommerce data is untouched.

The free edition is the complete quick view, AJAX modal, variation-aware add-to-cart, below/overlay placement, shortcodes and full settings. Peek PRO (planned) adds variation swatches in the modal, a related-products carousel, custom modal sections and quick-view analytics, not basic modal access.