Bee

Fixed

• After you change a source's Element type, the new scope options no longer look faded with a not-allowed cursor (#5). The 5.1.2 fix removed the disabled class from the wrong element.

Added

• GraphQL queries for headless front ends: beeRecommend, beeRelated and beeSearch return Craft elements in Recombee's order, with the recommId and the matching item IDs. Grant Bee → Query recommendations and search on a schema to use them. Pro.
• The visitor is taken from the request's session and Bee's guest cookie. There is no userId argument and no ReQL filter, so a shared token cannot read someone else's recommendations or page through the catalog.
• Results are limited to what the schema can read: an element in a section, group, volume or product type the schema has no access to is left out, and so is its item ID. beeRelated only accepts an element that is live and already in the catalog, so it cannot create empty items in Recombee.
• Queries that use Bee skip Craft's GraphQL result cache. That cache is keyed on the query and not the visitor, so it would otherwise hand one visitor's recommendations to the next person who sent the same query.

Fixed

• After you change a source's Element type, the new scope options (for example a user source's User groups) no longer look faded and disabled while still being clickable (#5).

Fixed

• A Twig mapping for a set or image list can now output a JSON array ({{ values|json_encode }}) as well as one value per line. A JSON array used to arrive as a single value, and printing an array directly failed so the property was left out (#3). Commas are still not separators, because a value can contain one. The source screen and the docs show both formats.
• The Bee navigation item now stays selected on the Log and Diagnostics screens (#4). Someone who can see the log but not the catalog is taken to the log.
• Changing a source's Element type now switches the scope options (sections, groups, volumes, entry types) straight away instead of after a save (#5). Saving keeps only scope choices that belong to the chosen type, so a switched source can no longer keep a scope that matches nothing.

Added

• Users can now be a catalog source, scoped by user group — a user in any of the checked groups is included (#2). Only active users are synced, a user's photo maps to imageUrl, and activation, suspension, unlocking and group changes resync the user even though Craft makes them without saving the element. Users are never returned by the public JSON recommendation endpoint; recommend them with craft.bee.recommend() in your own templates.

Fixed

• Fixed the Test connection button in the plugin settings, which did nothing: Craft namespaces plugin settings, so the button's id no longer matched the script (#1). Its instructions now say that it tests the saved credentials.
• Recommended elements are now filtered by live status as well as by the element type's default query status, which for users still includes suspended accounts.

Security

• Catalog sources can now only be added, changed, reordered or deleted by admins, and only where allowAdminChanges is on. A user with the Manage the catalog permission could previously add a Twig property that read secrets such as the security key and returned them through the payload preview. That permission still runs syncs, re-sends and purges, and the sync buttons now show on production too. On Craft 5.9+ with enableTwigSandbox on, Twig properties are also rendered in the sandbox.
• The payload preview now checks that the user can view the element, so it can no longer read entries from sections they have no access to.
• The public tracking endpoint no longer accepts purchases. Purchases are recorded on the server by the Commerce integration or craft.bee.trackPurchase(), so a script can no longer fake them to push an item up everyone's recommendations.
• The tracking endpoint's rate limit is now per IP address rather than per IP and User-Agent, which a client could rotate, and it can no longer be bypassed by sending requests in parallel.
• Recommended elements are resolved with their default status, so a disabled or future entry that Recombee still recommends is no longer returned by the public recommend endpoint.

Changed

• The control panel's inline styles and hard-coded colours were replaced with Craft's CP tokens and classes, so Bee's screens follow the CP theme.

Initial release.

Added

• Catalog sync for entries, categories, assets, Commerce products and Commerce variants, driven by catalog sources stored in project config. Property mappings read from custom fields, element attributes, built-in mappers or inline Twig, coerced to the declared Recombee type.
• Automatic sync on save, on the queue or inline, with a content fingerprint so an unchanged element costs nothing, and removal when an element is unpublished or deleted.
• Bulk sync from the console or the control panel, batched and resumable.
• Interaction tracking — detail views with real dwell time, purchases, cart additions, bookmarks, ratings and view portions — through one funnel with consent gating, de-duplication and a fail-open guarantee.
• A dependency-free front-end runtime that records views, measures dwell time, and carries a recommendation's recommId across the navigation to the interaction it produced.
• Recommendations and search — to a user, to an item, to an item segment, and Recombee's personalised search — returning Craft elements in Recombee's order.
• An attribution ledger, so Recombee can report on and learn from its own recommendations.
• The Commerce order funnel: purchases on order completion, cart additions on genuinely new line items, guest-to-account merging at checkout, and a historic order backfill that is safe to run twice.
• Diagnostics — twelve checks, each with a fix — in the control panel and as a console command that exits non-zero, so it can gate a deploy.
• A connection log with both payloads and no credentials, and a dry-run mode that builds and logs every request without sending it.
• Two editions: Lite (free) and Pro.