Skip to content
Gaurav TiwariChangelog

All products

Changelog

Every release across our products, newest first.

RSS feed

Showing 73–84 of 542 releases

  1. Stable

    GT Extensions for FluentCart 2.8.2

    Requires FluentCart. Invoices and the other store modules require FluentCart 1.6.4 or later. The agent skills also need the free Site Agent plugin with PHP execution on.

    Read full notes 5 changes
    • The invoice editor shows the total with tax beside the form and updates it as you type. Issue the invoice from that panel, right under Save your draft. It saves your changes and issues them in one step, and refuses to issue if the total changed while saving. You no longer save the draft first.
    • A draft linked to a quote request shows Send proposal in the same place instead. Pick the valid-through date, and the panel saves your prices and emails the proposal for acceptance in one step.
    • New AI agent skills for invoices and quotes. Download them under Invoices → Automation as ZIP files for Claude Code and other agents that read SKILL.md folders. They connect through the free Site Agent plugin, save drafts freely, and ask you before issuing an invoice or emailing a customer. The ZIPs contain your site's address and no passwords.
    • New gtfc_agent() PHP function for trusted integrations: list, create, update, issue and email invoices, and create, prepare, send and withdraw quote proposals as the signed-in user, with the same checks as the admin screens.
    • A proposal that the customer already accepted can no longer be sent again.
  2. Stable

    Core Bookings 0.20.0

    WordPress accounts, outgoing webhooks, a rebuilt email set and a large workspace update. Storage upgrades to schema 6 (additive). See [customer accounts](docs/customer-accounts.md), [webhooks](docs/webhooks.md), [emails](docs/emails.md) and [admin workspace](docs/admin-workspace.md).

    Read full notes 35 changes

    ### Booking form, manage page and dashboard

    • Customer accounts Optionally link customers to WordPress accounts. Logged-in customers have their details filled in and see their bookings in the dashboard without an emailed link ([core_bookings_dashboard]).
    • Customer accounts Require login per site or per service, enforced on the server. Create accounts at booking (checkbox or automatic, subscriber by default) without revealing existing accounts.
    • Customer accounts Accounts link only after the email is proven (Core Bookings created the account, or the customer confirmed an emailed link), because WordPress lets users change their email without confirmation. "Trust WordPress account emails" is an opt-in for sites that verify emails at registration and never applies after a user changes their email.
    • Customer accounts Managers can create, link or unlink a customer's account with a reason. Deleted users are unlinked; privacy export and erasure include the link.
    • Customer accounts Where accounts apply (login required, account creation on, or FluentCart), logged-in customers book under their account email; elsewhere they are prefilled and may book for someone else.
    • Outgoing webhooks Send booking, payment, customer, session-pack and waitlist events to Zapier, Make, n8n, FluentCRM or any HTTPS address from Settings > Webhooks, in a standard or flat format.
    • Outgoing webhooks Requests are signed (Standard Webhooks), limited to public HTTPS addresses, and retried for about two days. Each endpoint has a delivery log with Resend and turns itself off after repeated failures, emailing the admin.
    • Outgoing webhooks Payment holds that expire unpaid now appear in the timeline and notify integrations; pack, waitlist and customer changes emit events for developers too.
    • Emails Readable statuses ("Awaiting payment") instead of internal codes.
    • Emails An editable email per event (confirmed, awaiting payment, request received, approved, declined, rescheduled with the previous time, cancelled, refunded, balance paid), each able to follow the general template.
    • Emails Calendar (.ics) files attached to confirmations and reschedules.
    • Emails Optional staff and admin emails for new, cancelled and rescheduled bookings; approval and calendar-conflict emails include booking details.
    • Emails From name, From address and Reply-To settings. Waitlist and session-pack emails use the selected delivery provider.
    • Emails Completed and no-show updates no longer email the customer.
    • Emails Starts on the first bookable date, respects notice and horizon, lists common timezones first, shows the hold time and the amount on the payment button, and marks errors on their fields.
    • Emails Optional phone and notes fields and a per-service booking policy saved with each booking.
    • Emails Customers can add a cancellation reason and release an unpaid hold; change and cancel buttons hide inside the cutoff.
    • Emails The dashboard has Upcoming and Past tabs, editable profile fields, session-expiry notice, and only offers "Book again" for bookable services.
    • Emails The standalone page uses the site logo, shows the amount due and lists only active hosts.
    • Workspace Add phone and walk-in appointments, with an optional customer email, recorded payment, or an override with a reason.
    • Workspace Reopen completed or no-show appointments, confirm a payment-review booking after checking the provider, reschedule from available times, resend confirmations, edit customer contact details and copy the manage link.
    • Workspace Filter by staff, date range and any status; upcoming views list the next appointment first. CSV export follows the filters with fuller columns.
    • Workspace Group sessions, date-specific hours and FluentCart extras are edited as rows, with weekly repeats.
    • Workspace Customers list linked account, bookings, next appointment and credits; rosters get a session picker, capacity, CSV and print; the waitlist shows service and staff.
    • Workspace Remove saved credentials, copy webhook and redirect addresses, 18 more currencies, and optional customer details in staff Google events.
    • Workspace Setup checks cover the background worker, its schedule, the encryption key, FluentCart and the Stripe publishable key. Operations shows readable names, and old finished records are cleaned up after 30 days.
    • Fixes Refunds on confirmed bookings no longer drop pending reminders (Stripe and FluentCart).
    • Fixes The background jobs schedule re-creates itself if it goes missing.
    • Fixes The refund form stays available after a partial refund.
    • Fixes Block text and many interface and validation messages are now translatable; admin muted text meets contrast guidelines.
    • Fixes Rate limits can trust your own proxies, and next-slot searches no longer use up booking submissions.
    • Fixes Imports and exports keep the new service options and booking contact fields.
    • Fixes Privacy export and erasure include booking phone numbers and notes.
    • Fixes Webhook address checks cover IPv6 records and pin each request to the checked address; calendar attachments are written to a private temporary folder.
    • Fixes A failed database upgrade shows an admin notice and retries instead of stopping the site.
  3. Stable

    Core Bookings 0.11.0

    Take deposits at FluentCart checkout and collect the remaining balance later from the private booking page through a separate FluentCart cart.

    Read full notes 8 changes
    • Take deposits at FluentCart checkout and collect the remaining balance later from the private booking page through a separate FluentCart cart.
    • Sell session packs through FluentCart checkout, with activation, expiry, and refund handling matching Stripe packs.
    • Read FluentCart refunds per order item: refunding an extra no longer affects the booking, partial appointment refunds record the exact amount, and deposit and balance refunds add up.
    • Accept same-site checkout links for balance and pack payments in the booking and customer scripts.
    • Give every workspace input, select, and textarea one consistent field style with a visible focus ring; selects keep room for their arrow.
    • Use one reason field per operation or payment-event row, shared by its retry and dismiss buttons.
    • Lay out the service and staff save bar on one row: change reason, Preview changes, and Save.
    • Strip redundant semicolons in the CSS build so the admin skin stays within its 8 KB budget.
  4. Stable

    GT Extensions for FluentCart 2.8.1

    Requires FluentCart. Invoices and the other store modules require FluentCart 1.6.4 or later.

    Read full notes 2 changes
    • New option to number invoices with FluentCart's invoice numbers. Choose it under Invoices → Invoice appearance → Invoice numbering. An issued invoice and its FluentCart order then show the same number, such as INV-1253, instead of two different numbers. Invoices and store orders share one series, so the next store order takes the number after the invoice.
    • The number stays with the invoice when the customer pays in another currency or you edit and reissue it, and a cancelled invoice keeps its number. Invoices issued before you change the option keep their numbers. GT Extensions numbering stays the default.
  5. Stable

    Site Agent 0.3.0

    Bundle read-only builder skills for Gutenberg, GenerateBlocks, Elementor, Bricks and Divi, with list-skills and get-skill tools, active builders in site-context and the storing builder in get-content.

    Read full notes 7 changes
    • Bundle read-only builder skills for Gutenberg, GenerateBlocks, Elementor, Bricks and Divi, with list-skills and get-skill tools, active builders in site-context and the storing builder in get-content.
    • Add an opt-in Bricks tools group that serves Bricks 2.4+ abilities on Site Agent's endpoint: Bricks' fast-path tools under their own names, bricks-abilities and run-bricks-ability, with per-password limits, audit history and a PHP execution requirement for Bricks' PHP ability.
    • Refuse Elementor, Bricks and Divi layout meta in content writes, because raw writes skip each builder's validation and cache refresh.
    • Return the text of the user's autosave from get-content on request, and whether it is newer than the post, so staged edits can be verified and chained.
    • Refuse to stage edits to templates and template parts, which core cannot autosave by post ID, with a clear error instead of a REST failure.
    • Detect Bricks layouts without an editor mode, GenerateBlocks Pro blocks and GenerateBlocks global styles and conditions.
    • Fix the documented default page size of list-terms.
  6. Stable

    GT Extensions for FluentCart 2.8.0

    Requires FluentCart. Invoices, Page Access, Checkout Enhancements, Product Enhancements and the other store modules require FluentCart 1.6.4 or later.

    Read full notes 12 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.
  7. Stable

    GT Extensions for FluentCart 2.7.2

    Requires FluentCart. Invoices, Page Access and the newer store modules require FluentCart 1.6.4 or later.

    Read full notes 6 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.
  8. Stable

    Uranium 0.2.0

    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.

    Read full notes 17 changes

    Demos: WooCommerce store and FluentCart store

    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.

    SHA-256: 87761b2be1523ba46575c05d441d6b0d3c110b02bddfa3d98e6116be4bf3446f

    • New
    • 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.
  9. Stable

    GT Extensions for FluentCart 2.7.1

    The lesson, "Unlock Pages and Links for Buyers", covers setup, published and private pages, who gets access, links on other sites and common problems.

    Read full notes 1 change

    Requires FluentCart. Page Access, invoices and the newer store modules require FluentCart 1.6.4 or later.

    • Open the Page Access course lesson from the module's guide links. They opened the course index before.
  10. Stable

    GT Extensions for FluentCart 2.7.0

    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 notes 5 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.
  11. Stable

    GT Link Manager 1.9.1

    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 notes 7 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.
  12. Stable

    Core Bookings 0.10.0

    Core Bookings 0.10.0 improves booking and payment recovery and adds the tools needed to manage customers and resolve failed operations.

    Read full notes 5 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.

    • Fix balance-checkout races, refund reconciliation, reminders, recurring approvals, waitlist terms, meeting cleanup, privacy erasure, and daylight-saving/rescheduling errors.
    • Add searchable operations, customer history and metadata, group rosters, reasoned credit adjustments, and verified waitlist controls.
    • Add next-available appointment search, schedule previews and revision history, conflict-safe edits, opt-in staff-managed availability, and guided setup checks.
    • Add a compact Tabler-based Default UI. No UI Style disables customer-facing styling only; admin screens remain styled.
    • Reduce catalog queries, prioritize expiring messages, separate calendar work, and add regression coverage.