Requires FluentCart. Invoices, Page Access, Checkout Enhancements, Product Enhancements and the other store modules require FluentCart 1.6.4 or later.
Read full notes12 changes
New Checkout Enhancements module. Turn it on under FluentCart → GT Extensions, then set it up under FluentCart → Checkout enhancements.
Consent checkboxes above the payment methods: privacy policy, marketing emails (unticked), the EU digital content withdrawal waiver, age confirmation, or your own wording with links. Each can be required and shown for every cart, physical carts, digital carts, or one product. The order keeps the exact wording, its version, and the time, and the order activity log records it. Customers see a message under any required box they missed.
Shorter checkout for digital orders: hide street, apartment, city, postcode, state, or phone when nothing in the cart ships. Invoice payments keep every field.
Rename checkout fields, the billing and shipping headings, the account and shipping checkboxes, the order note heading and placeholder, and the Place order button. Required-field messages use your names.
Trust block below the payment methods with a heading, up to six lines, a payment logos image, and a link to your refund policy page.
Order notes, Fields & add-ons answers, the delivery slot, and consents now appear on the receipt, in the customer's order view, and in a Checkout details panel on the admin order screen. Add {{order.gtfc_checkout_details}} to an email template to include them there.
New Product Enhancements module. Open a product in FluentCart to fill its Product details card: choose Physical product, Digital download, Book or ebook, Software or plugin, Course or service, or custom details only. A product shows its table once its details are saved, so turning the module on changes no product page by itself.
Brand, weight, dimensions, file type, file size, number of files, last updated date, and language are filled in from FluentCart and your site settings. Type over any of them, or hide one from the page. Enter either ISBN and the other is worked out; barcodes and ISBNs are checked before saving.
Give any detail a different value for each product option. The table updates when the customer picks another option.
The details table appears after the product description, or only where you place the Product Details block or the [gtfc_product_details] shortcode. A product's table prints once per page, whichever placement comes first, and starts on the option FluentCart selects by default. Details go into the product's structured data: brand, GTIN, model number, color, material, size, weight, dimensions, condition, and the rest as additional properties.
Each module's guide links open its new course lesson.
Checkout Builder layouts show ticked checkboxes, the selected shipping method and saved address labels in the layout's accent color. They were white on white before, including FluentCart's terms checkbox.
Requires FluentCart. Invoices, Page Access and the newer store modules require FluentCart 1.6.4 or later.
Read full notes6 changes
Redesigned invoice items. Each item is a card with its image, name, a four-line description, delivery type, quantity, unit price, and line amount. One search finds store products and saved items, and the subtotal, discount, and shipping update as you type.
Save custom items as invoice-only items, on by default for new custom items. They appear in invoice item search and under Invoices → Saved items, and never in your store. Saving an item with the same name and currency updates it.
The invoice title is optional. A blank title becomes "Invoice" and the invoice number, such as Invoice INV-42, when you issue it.
Billing addresses are optional on invoices, whatever FluentCart's checkout requires. Customers can fill blank address fields at checkout while the issued tax stays fixed. A blank invoice address no longer clears a saved customer address.
New option to let the customer pay in any currency enabled in Multi-Currency. The invoice shows a currency choice beside Pay. Amounts convert from the issued invoice at your rates and markup; the invoice number and link stay the same, and editing the invoice restores the currency you issued it in.
Shorter invoice links: a 10-character code and a 16-character key replace the 36-character ID and 64-character key. Links sent before this update keep working until the invoice is edited.
Core Approvals 0.5.0-beta.1 is the first beta, for staging sites and controlled pilots.
Read full notes4 changes
Install this beta once from your purchase account. Later releases arrive as ordinary WordPress updates after you activate the license.
Requires WordPress 6.9+, PHP 8.3+, InnoDB, and PHP fileinfo. Back up the database before upgrading from a development build. Network activation is not supported; activate per site.
Validation: PHPStan level 8 and 38 unit tests; the packaged suite (333 assertions) on WordPress 6.9 and 7.1.2 / PHP 8.3, including an upgrade from the 0.5.0-dev build; and MariaDB concurrency races and 31 multisite isolation checks on WordPress 7.1.1 / PHP 8.5.
License activation and updates from GauravTiwari.org under Core Approvals > License. The key is encrypted and bound to the site, so a copied site must activate itself. Updates come only from the store or its private download bucket, and each package must match the release before it installs. Requests, reviews, and records never depend on the license.
Stock approval pages get a plugin-owned design without theme headers, footers, or unrelated scripts.
A redesigned workspace with grouped navigation, responsive request lists, a separate review panel, and an expandable workflow editor.
Reapproval, self-review, parallel-recovery, and reviewer-pool fixes from an audit, plus assignment filters, saved sorting, and an operator-only health screen.
Uranium 0.2.0 adds 13 patterns, a Landing page template and blog options, and fixes a set of accessibility and right-to-left problems found in an audit.
This zip is the direct build. It updates itself for free from gauravtiwari.org, with no account or license key. Sites already on 0.1.2 from the product page get 0.2.0 as a normal WordPress update. 0.1.2 shipped only through the product page.
13 patterns: product opener, specification sheet, model comparison table, service plans, customer quote with figures, case study, status strip, photo grid, latest articles, breakdown call checklist, a closer with next steps, and complete Product and Landing pages. The inserter now has 54.
Landing page template: it uses its own minimal header and compact footer. Both are template parts you can edit in the Site Editor.
Blog options in Appearance > Customize > Uranium blog: rows or cards for article listings, plus an author note and up to three related articles under each post.
Block styles: Badge, Checklist and Comparison, plus a download icon for buttons.
Starter content on a fresh install: the six page layouts as real pages, a front page, a posts page and a primary menu.
Footer legal links: a menu assigned to the Footer legal links location replaces the default Privacy and Terms links.
Search results label pages and products by type instead of showing a publish date.
Fixed
In right-to-left languages, arrows flipped back to pointing right on hover.
With reduced motion turned on, row arrows still moved on hover.
The closed WooCommerce Mini-Cart drawer stayed in the keyboard tab order on every page.
The add to cart button on a variable product dropped below AA contrast before options were chosen.
FluentCart sale prices and price filter values failed AA contrast, the filter badly so in dark mode.
Utility bar, footer and breadcrumb links had tap targets as small as 15px. They now reach 30px.
The comment form's consent checkbox was squeezed, and related rows repeated the author's name.
Install: Download uranium-0.2.0-updater.zip below. In your dashboard, go to Appearance > Themes > Add New Theme > Upload Theme, choose the zip and activate Uranium. Uploading it over an older version replaces it.
Page Access is off until you enable it under FluentCart, GT Extensions. Turning it off later opens restricted pages to the public again; your page and product choices stay saved.
Read full notes5 changes
Requires FluentCart. Page Access, invoices and the newer store modules require FluentCart 1.6.4 or later.
New Page Access module. Choose Page access from a product's menu, or Customer access in the page editor, to unlock pages for the customers who buy that product. Published pages show an access notice with sign-in and product links; private pages stay hidden from everyone except buyers and your team.
Access follows FluentCart orders: paid one-time purchases until the item is fully refunded, and subscriptions while active, trialing, completed, or past due, including the rest of a paid period after cancellation. A setting keeps subscription access after the first payment instead.
Buyers see their pages under My pages in the FluentCart customer account, or on any page with the [gtfc_my_pages] shortcode.
Give buyers links on other sites, such as a Notion template or a shared folder, from the same Page access screen. Buyers see them under My pages; the screen explains that these links cannot be paywalled and how to keep them unlisted.
Restricted pages are noindex, uncached, kept out of site search and sitemaps, and give SEO plugins the notice title instead of an automatic description from the content.
Fixed: after an automatic update from 1.7 or earlier, every short link could return 404 until someone opened the dashboard. Database updates now run on the first request after an update.
Read full notes7 changes
Fixed after an automatic update from 1.7 or earlier, every short link could return 404 until someone opened the dashboard. Database updates now run on the first request after an update.
Fixed Quick Edit could rewrite a regex pattern or direct path as if it were a slug. Changing only the destination of ^old/(.*)$ saved the pattern as old, which then matched every URL containing "old". Renaming a link also changed its slug, and saving with Advanced redirects off turned direct and regex links into standard ones. Existing links now keep their slug, path or pattern.
Fixed with a persistent object cache, one failed database lookup could keep a short link returning 404 until it was edited.
Privacy: analytics keeps minute-level detail only as long as individual click records (seven days by default), then reduces each day to daily totals, existing data included. Country-rule outcomes are recorded only when countries are on, and empty or scripted user agents are no longer counted.
Fixed analytics stopped collecting at 100 MB and blamed stale reports. Collection no longer stops for size; past a storage warning level you set, Delete old data removes old days and frees the space. CSV export now works on long ranges and exports daily totals; its time column is now date.
New Top links shows each link's destination URL.
Improved the links list works on phones, rows are shorter, and the admin has clearer icons, status notices and an Edit Link title.
Core Bookings 0.10.0 improves booking and payment recovery and adds the tools needed to manage customers and resolve failed operations.
Read full notes5 changes
Requires WordPress 6.9+, PHP 8.3+, and MySQL/MariaDB with InnoDB. Schema 5 upgrades existing data additively. Back up the database before upgrading.
The product remains in beta. Provider integrations require your own accounts and staging validation. This release does not automatically deploy to an existing site.
Core Forms 4.11.1 restores the complete All Submissions screen for users without saved views and improves the admin workflow introduced in 4.11.0.
Read full notes4 changes
Update from 4.11.0 to resolve the submissions-screen error. Existing form and submission records are preserved.
Empty, malformed, and numeric saved-view keys are handled safely.
Spam stays in the submissions tabs; old bookmarks redirect correctly.
Delivery recovery has a clear empty state, contextual task cards, guided outcome confirmation, and guarded retries.
Form Theme Customizer adds wrapper padding, defaulting to 10px. Zero and CSS spacing values work consistently in the customizer, form preview, and frontend.
Core Forms 4.11.0 adds reusable field groups in a searchable popup, team inbox assignments and private notes, workflow rehearsal, draft publishing, protected uploads and optional retention, and signed webhooks.
Read full notes
It also strengthens calculated prices, login and capacity checks, draft recovery, payment confirmation, fulfillment and refund recovery, attachment ownership, and concurrent editing.
Existing-form authoring API mutations now require the current fingerprint. Historical renewal refunds with missing entitlement terms require administrator reconciliation. Retention remains off by default.
Validated with 619 PHP tests, 75 JavaScript tests, WordPress/database checks, browser authoring, multipart downloads, and lifecycle cleanup checks.
Core Support 0.2.0-beta.1 is a beta for staging and controlled pilots.
Read full notes
This release adds signed inbound email replies, incoming-message review, encrypted originals, delivery recovery, and safer ticket workflows. Stock support pages use their own design, outgoing subjects are shorter, and the plugin includes FluentCart licensing and WordPress updates.
Requires WordPress 7.0+, PHP 8.2+, and sodium for encrypted email and license storage. Inbound email requires the included customer-owned relay and mailbox configuration. Direct Gmail/Microsoft connections and production validation remain open.
