Sites without the module's expected content-section field could see /llms.txt return an unexpected-error page. A targeted maintenance release closes that edge case.
...more
Sites using token-driven configuration or upgrading from ECA 2.1 have the clearest reasons to review the latest maintenance fixes in the 3.1 branch.
...more
For Drupal sites with logged-in experiences, the integration can use existing user attributes to segment journeys and activity, extending Rybbit beyond anonymous traffic reporting.
...more
For editorial teams troubleshooting changed or missing Layout Builder blocks, the module exposes a more granular history than node revisions alone.
...more
Because Link Remediator can write approved replacements back to stored content, its testing history is part of the operational risk. The core workflow has development and staging experience behind it, but not production validation.
...more
Component authors can replace icon identifiers entered as text with a visual picker while continuing to use icon packs discovered through Drupal core.
...more
For site builders deciding where location belongs, Canvas Map draws a narrow line between a map placed in a page layout and geographic data managed as structured content.
...more
The latest beta gives Drupal teams finer control over what context reaches AI agents while addressing upgrade problems found in the previous release.
...more
Site builders weighing Custom Field against Paragraphs or entity-reference approaches will get a maintainer-led look at its data model and workflow.
...more
For multilingual Drupal teams, the key safeguard is control over what AI may refresh. Human-authored or human-edited translations stay untouched unless an overwrite is explicitly requested.
...more
For teams using Drupal Views as the listing layer behind a decoupled frontend, the release removes several routing and integration problems without adding a new feature layer.
...more