Changelogs

Multi-currency correctness

• Cart totals were converted twice. FluentCart fires cart/can_purchase before cart/item_price against the same in-memory variation, so the price filter re-applied the exchange rate to an already-converted amount and a ₹480.00 line rendered as ₹46,219.00.
• Every product-page price now converts, not only the one FluentCart exposes a filter for. The compare price, header price range, and variant cards previously kept store-currency amounts, so a converted price sat beside an unconverted one. Manual price-book entries still win over the exchange rate.
• The currency symbol follows the selection across the whole storefront, not just checkout, so the cart drawer no longer labels converted amounts with the store currency’s sign.
• Receipts and order confirmations report the currency the order was charged in. FluentCart’s receipt renderer formats every amount with no currency argument.

Features that were silently disabled

Seven hooks were registered under names FluentCart does not use:

• cart/validate_add and cart/validate_update do not exist — can_purchase is the gate Cart::addItem() actually runs, so minimum/maximum quantity limits and guest purchase blocking were enforced only in the browser and a direct cart request bypassed them.
• fluent-cart/product_stock_availability was hyphenated; product/buy_now_text, product/show_add_to_cart, variation/data and admin_js_vars do not exist at all.
• is_singular('fct_product') tested a database table prefix rather than a registered post type, so module CSS printed on every page of the site while the matching scripts ran on none.

External Product admin screen

Rebuilt: saves over AJAX with inline status (the no-JS form post still works), card layout, dependent fields that disable while redirection is off, client-side URL validation, a live button preview, and a readout of the exact rel attribute that will ship. FluentCart’s product navigation is now styled, since FluentCart does not load its admin stylesheet on a custom submenu page.

Performance

A variation’s whole price book is read in one query and reused. The currency selector’s stylesheet, script and cart lookup load only where a price can appear, and its uncacheable status request no longer fires on pages with no selector.

Requires FluentCart 1.5.5 or newer. Verified against FluentCart 1.6.1.

What’s Changed

Fixed

• Inlined block stylesheets shipped unminified source. acf_blocks_minify_loader_src() only runs when a sheet is printed as a <link>. Styles registered from block.json also carry path data, and wp_maybe_inline_styles() reads that file straight off disk and prints its bytes into the page without the URL ever reaching style_loader_src — so every page rendering one of those blocks carried the readable source. It hit the four blocks whose block.json declares style as an array (Callout, Feature Grid, Post Display, Table of Contents); a string style is pre-registered by acf_blocks_register_styles() under the handle WordPress would have generated, so core bails before attaching path. acf_blocks_minify_registered_styles() now rewrites both src and path on plugin-owned registrations before the inline pass. Rewriting the registration rather than the printed tag keeps the inlining, so pages still avoid the extra request and just carry less of it — measured on a published Table of Contents post, 2,279 inlined bytes down to 1,494.
• ACF blocks now keep their baseline rhythm in the block editor. acf_blocks_register_layout_styles() attaches tokens.css and block-layout.css with wp_enqueue_block_style(), which only fires when a block renders on the front end — the editor canvas never received them. A heading following a Table of Contents block sat flush against it while editing and had 1.5rem of air once published. The sheets are now also enqueued on enqueue_block_assets in admin, the hook WordPress injects into the canvas document. Front-end delivery still goes through wp_enqueue_block_style(), so pages only pay for the sheets when a block is actually present.
• block-layout.css matches the editor’s markup. The front end renders the block element itself carrying .acf-block, while the editor wraps the same output in .wp-block and puts acf-block-component / acf-block-<name> on the wrapper — so .acf-block matched nothing inside the canvas even once the sheet loaded. The rule now carries a second selector for the wrapper. The two cannot match the same element, so the margin is never doubled. That second selector deliberately does not use :where(): the block editor sets its own margins on .wp-block elements, so a zero-specificity rule loses to them. Measured on a Table of Contents block followed by a heading — 0px with :where(), 24px without, against 24px on the published page.

Commits

• 2.11.0: serve minified CSS for inlined block stylesheets (ae06e79)

Stats

• Commits: 1
• Changes: 7 files changed, 212 insertions(+), 4 deletions(-)

Plugin Info

• Blocks included: 29
• Requires WordPress: 6.0+
• Requires PHP: 7.4+
• Requires: ACF Pro 6.0+ or Secure Custom Fields

Installation

1. Download acf-blocks-plugin-*.zip from the assets below
2. Go to Plugins → Add New → Upload Plugin in WordPress admin
3. Upload the zip file and activate

Full Changelog: https://github.com/wpgaurav/alpha-chat/compare/v0.4.1…v0.5.0

Full Changelog: https://github.com/wpgaurav/alpha-chat/compare/v0.4.0…v0.4.1

Full Changelog: https://github.com/wpgaurav/alpha-chat/compare/v0.3.2…v0.4.0

Full Changelog: https://github.com/wpgaurav/alpha-chat/compare/v0.3.1…v0.3.2

Full Changelog: https://github.com/wpgaurav/alpha-chat/compare/v0.3.0…v0.3.1

Full Changelog: https://github.com/wpgaurav/alpha-chat/compare/v0.2.1…v0.3.0

Full Changelog: https://github.com/wpgaurav/alpha-chat/compare/v0.2.0…v0.2.1

Full Changelog: https://github.com/wpgaurav/alpha-chat/compare/v0.1.8…v0.2.0

Full Changelog: https://github.com/wpgaurav/alpha-chat/compare/v0.1.7…v0.1.8

Core Forms 4.7.5 fixes duplicate field IDs and reworks MailerPress consent handling.

• Schema-rendered field IDs are now unique per form instance, so labels and descriptions stay correctly associated when multiple forms appear on one page.
• The MailerPress action defaults to double opt-in, preserves existing subscribers and suppressed contacts, and records form-level consent metadata. Confirmation is resent only when a pending or previously unsubscribed contact submits again.
• The legacy FluentCart-to-MailerPress bridge no longer creates subscribed contacts when its settings are empty.