Linux 软件免费装
Banner图

SparkCore Commerce Elements for FluentCart and Breakdance

开发者 sparkcoreio
更新时间 2026年11月5日 00:03
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

ecommerce page builder elements breakdance fluentcart

下载

0.7.2

详情介绍:

Adds a FluentCart category to the Breakdance element library with native product parts, product actions, cards, collections, full product output, mini cart, cart, checkout, customer account, and receipt views. Required third-party plugins This plugin is an integration layer and does nothing on its own. It requires both of the following, which are developed by other companies and are not affiliated with or endorsed by this plugin: FluentCart and Breakdance are trademarks of their respective owners. This plugin is an independent integration and is not affiliated with, endorsed by, or sponsored by either company. Commerce behavior remains native to FluentCart: this plugin never reproduces payment, checkout, cart, stock, or subscription logic in its own code. Every element renders through FluentCart's own shortcodes and renderer classes, so add-to-cart, checkout, and account behavior work exactly as they do on a page built with FluentCart's own blocks or shortcodes. The integration is source-validated against the exact versions installed on the reference site used to audit and build it, most recently FluentCart 1.5.5 and Breakdance 2.8.1. Every FluentCart internal (shortcode, renderer method, model field, dataset key, JS event) this plugin depends on is recorded, with file and line evidence, in a central contract registry with runtime version checks, so a future FluentCart update that changes one of those internals fails visibly and safely rather than silently. Editor placeholders distinguish four states so page builders always know what they are looking at: an element that resolves and renders correctly live but is only hidden from the builder preview, an element with no product chosen yet, a chosen product or variation that no longer exists, and an actual contract break (missing shortcode or a render exception).

安装:

  1. Install and activate FluentCart and Breakdance.
  2. Upload and activate SparkCore Commerce.
  3. Open a Breakdance document and use the FluentCart category.

屏幕截图:

  • Every element has native Breakdance controls, here FC Product Price with its product source and price settings.
  • A single product template built from separate product elements: gallery, title, price, excerpt, variations and buy button.
  • FC Search Bar and FC Products render a searchable product grid straight from FluentCart.
  • FC Checkout renders FluentCart's own checkout, so payment gateways, coupons and subscriptions work as usual.
  • The FluentCart Health page checks every FluentCart interface this plugin relies on after each update.

常见问题:

Which pages should I exclude from full-page caching?

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:

  • FlyingPress: Settings > Cache > Excluded URLs, add the cart/checkout/account/receipt page paths (or the FluentCart page-setting slugs if customized).
  • LiteSpeed Cache: Cache > Excludes > Do Not Cache URIs, add the same paths.
  • Any other full-page cache plugin: look for a URL-exclusion or "do not cache" list and add the same paths.

Do I need to exclude the mini cart too?

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.

Why do some FluentCart elements show a dashed placeholder in the builder?

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.

Does this plugin implement its own checkout, cart, or payment logic?

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.

更新日志:

0.7.2 0.7.1 0.7.0 0.6.0 0.5.0