| 开发者 | sparkcoreio |
|---|---|
| 更新时间 | 2026年11月5日 00:03 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
FluentCart elements that render customer state (Cart, Checkout, Account, Receipt) must never be served from a full-page cache: doing so risks showing one visitor's cart contents, account details, or order receipt to a different visitor. This plugin already defines DONOTCACHEPAGE and sends nocache_headers() on any page that renders one of these views, which most cache plugins respect automatically. As a second line of defense, still add your site's cart, checkout, account, and receipt/thank-you page URLs to your cache plugin's exclusion list:
No. A page whose only FluentCart element is the Mini Cart stays fully cacheable. The mini cart is not one of this plugin's route-no-cache contexts (only Cart, Checkout, Account, and Receipt are), so it never sets DONOTCACHEPAGE and never sends no-cache HTTP headers. The mini cart is normally placed in a header or footer template and renders on every page of the site, so treating it like a full customer-state view would make the entire site uncacheable at the HTTP layer.
Instead, the server-rendered mini cart markup has any session-specific values (item count, subtotal) stripped out before a cache plugin ever stores it, so the cached shell is identical for every visitor. After the cached page loads in the browser, a small script calls FluentCart's own public cart bootstrap to fetch the current visitor's real cart and paint the item count and subtotal into that shell. No cart math, pricing, or currency logic lives in this plugin: the hydration script only calls FluentCart's own methods and writes into FluentCart's own documented mini cart elements.
The placeholder tells you which of four situations you are in: the element renders correctly on the live site and is only hidden from the builder preview (enable its "Live editor preview" option to inspect it here), no product has been chosen for this element yet, the chosen product or variation no longer exists, or an actual error occurred (a required FluentCart shortcode is missing, or rendering threw an exception). Each state has its own placeholder style so the difference is visible at a glance.
No. Every commerce action (add to cart, checkout, payment, subscriptions, stock) is rendered through FluentCart's own shortcodes and PHP renderer classes. This plugin only supplies the Breakdance element wrappers, design controls, and context resolution around them.
style field holds the CSS text, and the override wrote the raw object, which reaches the stylesheet as the literal text Array. The browser accepts that as a variable value but then rejects the property that reads it, and falls back past our default all the way to the browser's own. A button set to a 20px radius with 18px padding was drawn with no radius and no padding at all. This affected every element offering a button, including Add to Cart, Buy Now, the buy section and the gallery's See More button, each of which carried its own copy of the fault.style field. The button sweep did not reach these two preset files because each held its own copy of the code.return; makes the value of Breakdance's include check null, which it reads as a missing file; the buffered output was then flushed to an arbitrary place in the page. All eleven occurrences now return true, with a tokenizer-based test that fails on any future bare return.%%CURRENTPATH%% placeholder, which is required to reference a sibling field inside a repeater row. The price threshold field is now conditional as well, using the is one of operand.