Scolta 1.2.0 Adds Incremental Indexing and Removes Deleted Content From Search

Discover Drupal graphic with the Tag1 logo and a browser search illustration. Text reads "DISCOVER DRUPAL". "Scolta 1.2.0 Brings Incremental Indexing to Drupal Search". "Deleted content now leaves the index immediately while routine edits can avoid a full rebuild". "TAG1". "https www thedroptimes.com". "THE DROP TIMES".

Version 1.2.0 of Scolta adds incremental indexing, allowing ordinary content edits to update only changed items instead of rebuilding the full search corpus. Drupal.org release notes published on 7 August 2026 say deleted nodes and removed translations now leave the index immediately. Changes that cannot be applied exactly through the incremental path fall back to a full build, with the reason recorded in logs. The release supports Drupal 10.3 and 11.

For sites with frequent publishing activity, the incremental path narrows the amount of search work triggered by routine changes when it can be applied. Immediate deletion handling also prevents removed content from remaining searchable and sending visitors to 404 pages until another rebuild occurs. Facet counts after AI query expansion are now calculated from the same collapsed result set shown to users, correcting counts and filter values that could previously disagree with visible results.

The release also changes build execution and recovery. drush scolta:build now runs in the foreground, exits with a non-zero status on failure, and reports success only after the index verifies. Resume logic now uses an entity ID boundary rather than a page offset, while the build lock renews for each chunk. The Scolta release notes report that a warm full build was about 2.3 times faster in project testing.

Fresh installations no longer select an AI provider automatically, leaving query expansion and summaries disabled until a provider is configured. Existing sites with saved provider settings are unchanged. Most sites require no additional upgrade step beyond updating, but custom PHP that subclasses ScoltaContentGatherer or decorates scolta.content_gatherer must update its gather() override because the resume parameter changed. Sites that call directly into the Tag1\Scolta\ namespace should also review the Scolta PHP 1.2.0 upgrade notes for two package-level compatibility changes. Scolta 1.2.0 requires tag1/scolta-php 1.2.0.

Disclosure: This content is produced with the assistance of AI.

Note: The vision of this web portal is to help promote news and stories around the Drupal community and promote and celebrate the people and organizations in the community. We strive to create and distribute our content based on these content policy. If you see any omission/variation on this please reach out to us at #thedroptimes channel on Drupal Slack and we will try to address the issue as best we can.

Related People

Upcoming Events