Fixed: right after updating to 0.6.0, the upgrade could run on many requests at once and queue the background relearn many times. The upgrade and the relearn now run once, under a lock, and a new relearn replaces one still waiting.
Read full notes1 change
Fixed right after updating to 0.6.0, the upgrade could run on many requests at once and queue the background relearn many times. The upgrade and the relearn now run once, under a lock, and a new relearn replaces one still waiting.
New: How Chat answers. Answer length, topic scope (including "only what this site's content covers"), clarifying questions, pointing to the contact form, and up to 20 rules of your own.
Read full notes11 changes
NewHow Chat answers. Answer length, topic scope (including "only what this site's content covers"), clarifying questions, pointing to the contact form, and up to 20 rules of your own.
NewModels for each job. Follow-ups, titles and unanswered-question summaries can use their own model or none.
NewLimits. Message length, questions per conversation, a daily token budget, a honeypot against bots, and a per-IP limit.
NewTalk to a person. The contact form sends the whole conversation with it.
NewRetention and privacy. Old conversations are deleted on your schedule; WordPress's privacy export and erase tools cover Alpha Chat.
NewKnowledge. Learn post types automatically; headings, excerpts, terms, custom fields and store product facts (WooCommerce, FluentCart, EDD) are learned; a 30-minute check keeps passages current; password-protected posts are never learned.
NewSearch. Fused meaning and keyword ranking, a keyword-only mode that needs no embeddings key, and background relearning when you change the search model.
NewTest connection, live model lists, Insights for unanswered questions, launcher placement by page type and path, sealed API keys and ALPHA_CHAT_CONFIG in wp-config.php.
Changed conversations belong to a server-issued token instead of IP and user agent; open conversations start over once after updating.
Changed existing sites keep conversations forever and have no token budget until they set one.
Fixed sources were never matched to the reply; Cloudflare's client-IP header is trusted only from Cloudflare.
From customer feedback. A drop-in update from 1.1.1; invitations gain a duration column (form schema 2), added automatically on update. Core storage stays at schema 8.
Read full notes5 changes
Added Declining a customer's reschedule can keep the original booking. Check Keep the original time until the new one is approved under Customer reschedules: both times stay reserved while you decide, approving releases the original time, and declining (or not deciding before the original time) keeps the booking at its original time instead of cancelling it.
Added Private booking links over the REST API: create, list, read and revoke invitations at core-bookings/v1/admin/invitations, with API key scopes read and bookings:write. An invitation can fix one of the service's durations, in wp-admin too, and then books only that duration.
Added Developers: booking.reschedule_declined webhook and reapproval_declined booking event; core_bookings/repay_hours; approval_reschedule_keep on the service abilities.
Fixed Approving a card hold confirms the booking only once Stripe confirms the charge. If the charge fails (the hold was released or expired), the booking goes back to awaiting payment for the approved amount instead of being confirmed unpaid, the customer is asked to pay again, and staff get a Payment failed email.
Fixed Cancelling a booking, or any change that leaves it unconfirmed, removes its queued reminders, so reminders for appointments far ahead no longer hold up erasing a customer's data. The hourly cleanup also clears reminders left behind by earlier versions.
New: design settings under Appearance > Customize > Stackless: Design. Primary, text, heading, background and card colors, the reading and wide widths, body and heading fonts (system stacks or your own), logo width and an optional fade between pages. Only changed values print, as a few custom properties, and the editor and theme.json palette follow them.
Read full notes12 changes
New design settings under Appearance > Customize > Stackless: Design. Primary, text, heading, background and card colors, the reading and wide widths, body and heading fonts (system stacks or your own), logo width and an optional fade between pages. Only changed values print, as a few custom properties, and the editor and theme.json palette follow them.
New a footer text field with {year} and {site}, and fields for code in the head and before the closing body tag (administrators who may post unfiltered HTML only), under Stackless: Footer and code.
New Full width (no title) and Canvas (no header or footer) templates for pages, posts and other public post types (not WooCommerce products or EDD downloads, which keep their store layouts). Full-width blocks, covers, background groups and raw HTML sections run edge to edge; text and other blocks keep the reading width with space around them.
New a Layout panel in the editor to hide the title, the site header or the site footer, or to lay the header over the first section until the page scrolls. Over a dark cover the header switches to light text (filter stackless_theme_header_on_dark for other heroes). Products and other classic-editor screens get the same options in a side box.
New Page Blocks Builder support. Blocks placed in the header or footer regions replace the theme's own (filter stackless_theme_region_mode to keep both); the hero, before content, after content, sidebar and 404 regions print in place, and two theme regions sit above the WooCommerce shop grid and the download grid. The builder template runs edge to edge and the builder preview uses the theme's type and colors.
New Appearance > Stackless tools. Export the theme settings as JSON, import them on another site, and restore one of the last three backups taken before each import.
New Marketers Delight importer (also under Tools > Import). It previews, then moves the logo, colors, widths, fonts, header and footer scripts, menu locations, widgets, the footer copyright, MD page templates (PBB Template, Builder, Full Blank, Premium Builder) and per-page header, footer, headline and transparent-header settings. It lists what Stackless cannot take over: MD page blocks (with a link to Page Blocks Builder's own importer), MD shortcodes and blocks in content, dropin post types and MD-only features. MD's data is never changed.
Improved the WooCommerce stylesheet (46 KB) loads only on store screens, pages with WooCommerce or Stackless blocks and shortcodes, and pages with WooCommerce widgets, instead of on every page. Blocks and shortcodes it cannot see in advance still pull it in.
Improved the Stackless module layer loads on store screens or when a Stackless module queues its own styles, and the EDD header-cart script only where the header cart prints.
Improved related posts are cached per post and refresh when any post is published, edited or unpublished.
Fixed headings inside a group or column with its own text color take that color, and full-width groups, columns and covers with a background run square to the screen edges.
Changed the site header and footer markup moved to template-parts/site-header.php and template-parts/site-footer.php. Child themes that copied header.php or footer.php keep working; override the new parts to change the markup.
Fewer database queries on every page for stores without a persistent object cache.
Read full notes2 changes
Requires WordPress 6.7+, WooCommerce 9.9+ (tested with 11.2) and PHP 7.4+.
Fixed on stores without a persistent object cache, each Stackless setting left at its default no longer costs a database query on every page. Stackless loads them all in one query, so a page runs one query more than WooCommerce alone instead of 20 or more.
Fixed Subscriptions no longer reads each product's custom fields with a query of its own on shop, product and cart pages.
New module: Google Product Feed. A Google Merchant Center feed of your downloads at /stackless-feed/google.xml, for free listings across Google and for Shopping ads. Each download, or each price option of a variable-price download, is one item with its price, featured image, category and brand. It is rebuilt a few minutes after downloads change, and once a day.
Read full notes3 changes
New module: Google Product Feed. A Google Merchant Center feed of your downloads at /stackless-feed/google.xml, for free listings across Google and for Shopping ads. Each download, or each price option of a variable-price download, is one item with its price, featured image, category and brand. It is rebuilt a few minutes after downloads change, and once a day.
The Product feed screen under Stackless shows the feed URL, when it was last built, a Google category for each download category, and every download or price option left out with the reason: free, a service, sold on another site or price on request, not buyable by visitors who are logged out, a subscription billed more often than yearly or with a set number of payments, or no featured image. Exclude or include a download from there.
Downloads in an ebook category stay in free listings and are kept out of Shopping ads, which don't allow ebooks.
Added: Build forms in the Block Editor. Start from the new "Build in the Block Editor" card or switch an existing form on its Fields tab. Add fields, choices and a submit button as blocks, and lay them out with columns, groups and headings. Settings, actions and submissions work the same, and a form can switch back to the HTML builder at any time.
Read full notes6 changes
Added Build forms in the Block Editor. Start from the new "Build in the Block Editor" card or switch an existing form on its Fields tab. Add fields, choices and a submit button as blocks, and lay them out with columns, groups and headings. Settings, actions and submissions work the same, and a form can switch back to the HTML builder at any time.
Added In the Block Editor, edit choice options on the canvas, mark fields required from the toolbar, and see a "Before you publish" check for missing submit buttons, field names and labels.
Added The Submissions tab shows a clear empty state until a form receives its first entry.
Changed A tidier Submissions tab, Revisions table and submission screen, and Privacy and retention now sits with the other settings above Save Changes.
Fixed Send Reply on a submission now sends the reply instead of saving the form.
Fixed Restoring a revision no longer removes headings, help text, separators and images from the form.
Yearly subscriptions in the Google product feed no longer carry subscription_cost, which Merchant Center disapproved.
Read full notes1 change
Fixed Google Product Feed no longer sends subscription_cost for yearly subscriptions. Google accepts that attribute only for phone and telecom contracts, so Merchant Center disapproved yearly software plans and treated them as payment plans limited to one country. Yearly plans are now listed at the price of their first year.
Adds Google Product Feed, a Merchant Center feed for free listings and Shopping ads, with a strikethrough sale price in product structured data.
Read full notes5 changes
New Google Product Feed builds a Merchant Center feed at /gtfc-feed/google.xml, one item per variation with price, sale price, stock, images, brand, GTIN or MPN, condition and categories. It is rebuilt a few minutes after products change and once a day, and Merchant Center fetches it on a schedule.
New The Product feed screen shows the feed URL, build status, Google category mapping per FluentCart category, and every product or option left out with the reason. Exclude or include a product from there.
New Items Google doesn't allow are left out: services, external products, hidden or zero prices, payment plans, and subscriptions billed more often than yearly. Ebooks stay in free listings and are kept out of Shopping ads.
New When a variation has a compare-at price, the product page's structured data gains it as a strikethrough price, so the page shows the same sale as the feed. Turn this off in the feed settings.
New WP-CLI commands wp gtfc feed build, wp gtfc feed status and wp gtfc feed item.
Adds Google Product Feed, a Google Merchant Center feed for free listings and Shopping ads, with every left-out product and its reason.
Read full notes5 changes
Requires WordPress 6.7+, WooCommerce 9.9+ (tested with 11.2) and PHP 7.4+.
New Google Product Feed builds a Google Merchant Center feed at /stackless-feed/google.xml, one item per product or variation with the price the product page shows, sale price and dates, stock, images, GTIN, brand, condition and categories. It is rebuilt a few minutes after products change and once a day, and Merchant Center fetches it on a schedule.
New Stackless → Product feed shows the feed URL, build status, Google category mapping per product category, and every product left out with the reason. Exclude or include a product from there.
New products Google doesn't allow are left out: external and service products, hidden or zero prices, payment plans, and subscriptions billed more often than yearly. Ebooks stay in free listings and are kept out of Shopping ads.
New WP-CLI commands wp stackless feed build, wp stackless feed status and wp stackless feed item.
New for developers: subscription product terms include length, the number of renewals after the first period, and Service Products answers the stackless_is_service_product filter.
Starter content and clearer settings. A drop-in update from 1.1.0 with no storage changes.
Read full notes3 changes
Added Starter content: add the demo's services, four sample staff, draft pages with booking forms, a service directory, popup buttons and a customer dashboard, and optional sample customers and appointments, from Settings > Import / Export. Preview it first; nothing is added until you confirm, no email is sent, existing records are never changed, and dates are built from the day you import. Services that need a module are left out until it is on. Remove starter content deletes exactly what it added and keeps any service a real customer has booked since.
Improved Page settings show the address they open, as a link, and follow the dropdown before you save: Customer dashboard page (the chosen page or the built-in dashboard link) and the staff portal's Portal page (the chosen page or the standalone address).
Improved Private file storage says why the automatic check could not verify the folder, links to a harmless test file you can open yourself, and lets you confirm the folder is refused when the site cannot request its own address. The setup steps match the detected web server (Apache, LiteSpeed or Nginx), with copy buttons for the Nginx rule and the wp-config.php line.
From customer feedback and a review of other booking tools. Core storage stays at schema 8 with new service settings; the Developer API module and CalDAV write-back add their own tables when switched on. A drop-in update from 1.0.1.
Read full notes20 changes
Added Approval services on Stripe can authorize the card at booking and charge it on approval. Set Payment for approval requests to Authorize the card at booking, charge on approval. Approving charges the usual amount, a smaller amount you enter, or nothing (0 releases the hold). Rejecting the request, the customer withdrawing it, or the approval window closing releases the hold, so the customer is never charged. Stripe keeps a card hold for about seven days, so the approval window ends an hour before that.
Added Deposits can be a fixed amount instead of a percentage, for the service and for each extra duration.
Added Customer reschedules can need approval again. With Customer reschedules checked, a customer who moves an approved booking sends it back for approval; it keeps its payment and its time until you decide. Staff moves, and moved sessions of a recurring series, stay confirmed.
Added Stripe, Turnstile, Google, Zoom, Microsoft 365 and Brevo keys, and the license key, can live in wp-config.php instead of the database. Settings screens show them as set in wp-config.php.
Added Approval can apply only when it matters: requests that start within a set number of hours, first-time customers, or requests above a price. With no rule set, every request still needs approval.
Added Approval services on Stripe can also charge at booking and refund automatically when a request is rejected, withdrawn or not decided in time, for decisions that take longer than a card hold lasts.
Added Services can limit how many times a customer moves one booking online. Staff can always move it.
Added The customer dashboard sign-in email now carries a six-digit code as well as the link, so customers can sign in on the device they started on. Five wrong guesses end the code.
Added The booking form block has theme presets: Soft, High contrast, Dark, and one that follows the visitor's light or dark setting. Colors picked on the block still win.
Added Booking events reach Google Analytics, Tag Manager and Meta Pixel when they are already on the page: cb_booking_requested, cb_booking_confirmed and cb_booking_paid, without names or emails. Switch it off under Settings > General. The page also fires a core-bookings:event browser event.
Added Show the booking form on websites that don't run WordPress. List the allowed sites in Settings > Embed and paste the snippet for a service. The form resizes itself, and the embedding page receives booked, paid and approved events without any customer details. Embedding is off until you list a site.
Added The staff portal can be installed as an app, shows the last agenda without a connection, and can send notifications to each staff member's devices when a booking needs their approval, including card holds waiting for approval.
Added A new Developer API module adds revocable API keys for server-to-server access under Settings > API keys. Each key acts as a chosen staff member or manager, is limited to the permissions you pick (read, bookings, customers, settings), can expire, shows when it was last used, and is shown only once. It also adds JSON routes to list bookings and customers, read a customer, add staff appointments and read booking settings, an OpenAPI 3.1 description at /wp-json/core-bookings/v1/openapi.json, and a small typed JavaScript client in clients/js, included in the plugin, for custom front ends.
Added Booking questions can ask for a signed waiver. Customers read your waiver text and sign on the booking form, or later through a private link in their confirmation email and booking page, by drawing a signature or typing their full name. Each signature is kept privately with the signer's name, the time, and a fingerprint of the exact waiver text, so you can prove which version was signed. Staff see signed or not signed on the appointment, staff portal agenda, calendar and appointment list, can open or download a printable record, and can send a reminder or require the signature before check-in. Customers can download their own copy. Signed waivers are included in personal data exports and deleted on erasure and retention, and webhooks gain booking.waiver_signed.
Added Import services, staff, customers, and upcoming and recent appointments directly from Amelia, Bookly or LatePoint when their tables are in the same database, even if the plugin is deactivated. Preview first, map or skip staff, and run again to continue in batches of 2,000. No email is sent and nothing in the other plugin changes.
Added Staff can choose a CalDAV calendar (iCloud, Fastmail, Nextcloud) that receives their confirmed bookings. Events are added, moved and removed automatically, and customer names appear only if a manager turns that on.
Added Developers: core_bookings/capture_amount sets what approval captures; booking events payment_authorized, payment_captured, capture_failed, payment_released and reapproval_requested, with matching webhooks; capture_amount on the update-appointment ability; deposit_fixed, approval_payment (after, hold, charge), approval_reschedule, approval_rule_notice, approval_rule_new, approval_rule_above and reschedule_limit on the service abilities; POST portal/code signs in with an emailed code; reschedules_left on customer booking payloads; the payment_ledger job and ledger webhook field; a core-bookings:booking DOM event each time the form shows a booking. Embedded payment holds need the payment_intent.amount_capturable_updated Stripe event: Create the webhook for me adds it, also to a webhook it made before.
Improved Services with embedded Stripe payment collect the remaining balance in the same embedded form instead of sending customers to Stripe Checkout.
Improved The appointment CSV export includes payment references, Stripe's fee and the net amount for each booking, and webhooks include the fee and net, for owners who keep their own books.
Fixed The customer dashboard and booking form shrank to almost nothing inside a flex column. They now take the full width, up to their usual maximum.