Releases 14.0 

TYPO3 14 LTS Compatibility 

EXT:solr has been fully adapted for TYPO3 14 LTS, including Fluid v5 ViewHelper compatibility, TCA changes, deprecation removals, and testing framework updates.

XLIFF 2.0 Migration 

All language files have been migrated from XLIFF 1.2 to XLIFF 2.0 format.

Parallel Solr Worker Cores for Integration Tests 

Integration tests now use parallel Solr worker cores via paratest, significantly improving test execution speed.

Event Listener Migration to PHP Attributes 

Event listeners have been refactored to use the #[AsEventListener] PHP attribute instead of Services.yaml tag registration, following TYPO3 14 best practices.

Unified Sub-Request Indexing Pipeline 

The page indexing system has been completely rewritten. The legacy HTTP-based PageIndexer (which made real HTTP round-trips via X-Tx-Solr-Iq headers) has been replaced by a unified in-process sub-request pipeline using TYPO3's Application::handle().

Key changes:

• IndexingService orchestrates all indexing via Application::handle() sub-requests — no more HTTP round-trips
• SolrIndexingMiddleware handles page rendering, document creation, and Solr submission within the standard TYPO3 middleware stack
• UserGroupDetectionMiddleware + UserGroupDetector detect frontend user groups during page rendering without Singleton state or TCA manipulation
• CliEnvironment and forcedWebRoot scheduler option removed — sub-requests use chdir(Environment::getPublicPath()) to ensure correct working directory
• 12.7% faster indexing (493.9s → 431.3s for 59 pages) with  3,200 lines removed

See #4559 and #4598 for details.

Bugfix: No c:0 Variant on fe_group-restricted Pages 

Two interrelated bugs in the new sub-request indexing pipeline caused access-protected pages to be indexed with incorrect Solr documents.

Bug 1 — Spurious ``c:0`` variant from global template content: During the findUserGroups sub-request, TYPO3 renders the full page including global template content (footer, navigation) from other pages. Content elements without fe_group restriction in these template areas caused UserGroupDetector to collect group 0, which then triggered a c:0 Solr variant even for pages where all actual page content is access-restricted. With fe_group=1 on the page, the c:0 variant was never meaningfully accessible (its access rootline already required group 1), but it polluted the index with empty or incorrect documents.

Fix: When pageUserGroup > 0, group 0 is removed from the detected access groups. The page's own group is added as a fallback so that users holding only the page group can still find the page in search results.

Bug 2 — Protected content leaking into the ``c:0`` variant: When indexing the c:0 variant (anonymous rendering), FrontendGroupsModifier unconditionally added pageUserGroup to the faked frontend groups. This granted access to fe_group-restricted content elements during the anonymous rendering sub-request, causing protected content to appear in the public Solr document — a potential content disclosure issue.

Fix: pageUserGroup is now only added to the faked groups when userGroup > 0 (i.e. not during the anonymous c:0 rendering).

As a result, pages with fe_group restriction no longer produce a c:0 Solr document. Instead, the page's own group (e.g. c:1) is used as the base content access variant.

Unified Site Hash Strategy 

Introduced in solr v13.1, and now implemented as default, the site hash strategy is now based on the site identifier and not on the domain anymore, making the site hash calculation more robust across sites with multiple domains.

The extension configuration setting: siteHashStrategy has been removed without substitution.

The PSR-14 event AfterDomainHasBeenDeterminedForSiteEvent has been removed, as it has been superseded by AfterSiteHashHasBeenDeterminedForSiteEvent.

If you upgrade from < 13.1, it is recommended to re-index all solr cores completely.

!!! QueueInitializationServiceAwareInterface and related Queue methods removed 

The interface \ApacheSolrForTypo3\Solr\IndexQueue\QueueInitializationServiceAwareInterface and its implementation in \ApacheSolrForTypo3\Solr\IndexQueue\Queue have been removed entirely. The following public API is gone:

• Queue::setQueueInitializationService(QueueInitializationService $service): void
• Queue::getQueueInitializationService(): QueueInitializationService
• Queue::getInitializationService(): QueueInitializationService (was already deprecated since v12)

The QueueInitializationService itself is not affected and continues to exist.

!!! DataUpdateHandler::removeFromIndexAndQueueWhenItemInQueue() removed 

The deprecated method DataUpdateHandler::removeFromIndexAndQueueWhenItemInQueue(string $recordTable, int $recordUid): void has been removed. Use DataUpdateHandler::removeFromIndexAndQueue() directly instead.

!!! PageIndexer::isPageIndexable() removed 

The deprecated method PageIndexer::isPageIndexable(Item $item): bool has been removed. Use PageIndexer::isPageEnabled(array $record): bool instead.

!!! RecordUpdatedEvent no longer covers record insertions – use RecordInsertedEvent 

A dedicated RecordInsertedEvent has been introduced for record creations. The RecordUpdatedEvent now only fires for updates; the deprecated $isNewRecord property, its constructor parameter, and the isNewRecord() method have been removed from RecordUpdatedEvent.

Previously RecordUpdatedEvent was dispatched for both new records and updates, with isNewRecord() acting as a flag to distinguish the two cases. In v14 these are two distinct events.

# Before – one listener covering both cases
tags:
  - name: event.listener
    event: ApacheSolrForTypo3\Solr\Domain\Index\Queue\UpdateHandler\Events\RecordUpdatedEvent

# After – separate registrations
tags:
  - name: event.listener
    event: ApacheSolrForTypo3\Solr\Domain\Index\Queue\UpdateHandler\Events\RecordInsertedEvent
  - name: event.listener
    event: ApacheSolrForTypo3\Solr\Domain\Index\Queue\UpdateHandler\Events\RecordUpdatedEvent

!!! Item properties are now non-nullable with strict validation 

Item constructor properties (item_uid, indexing_configuration, changed) are now non-nullable and validated strictly. CSV fixtures for integration tests must include all required columns.

!!! Legacy PageIndexer system removed 

The HTTP-based page indexing system has been completely removed and replaced by the unified sub-request pipeline. The following classes no longer exist:

• \IndexQueue\PageIndexer — replaced by \IndexQueue\IndexingService
• \IndexQueue\PageIndexerRequest — replaced by \IndexQueue\IndexingInstructions
• \IndexQueue\PageIndexerResponse — replaced by JsonResponse
• \IndexQueue\PageIndexerRequestHandler
• \IndexQueue\PageIndexerDataUrlModifier (interface)
• \IndexQueue\FrontendHelper\Manager
• \IndexQueue\FrontendHelper\FrontendHelper (interface)
• \IndexQueue\FrontendHelper\PageIndexer (event listener)
• \Middleware\PageIndexerInitialization
• \System\Environment\CliEnvironment
• \System\Environment\WebRootAllReadyDefinedException

The UserGroupDetector and AuthorizationService have been moved from \IndexQueue\FrontendHelper to the Middleware namespace.

The forcedWebRoot scheduler task option has been removed from IndexQueueWorkerTask and IndexQueueWorkerTaskAdditionalFieldProvider.