Issue Bug Closed

#107656Backend Indexing not working

Allan Vladimirov 10/10/25, 11:38 updated 09/30/26, 19:26

Description

When Disable indexing in Frontend is activated, indexing via Backend does not work properly. It always says that 0 pages and 0 files are indexed. We’ve tried resolving this with AI, but weren’t successful. Don’t know if everything was right or relevant the AI proposed but indexing is certainly not working via backend, via frontend it works just fine.

After extensive troubleshooting, we’ve confirmed that the crawler in TYPO3 v13 processes pages successfully but does not trigger the Indexed Search indexer, despite correct configuration.
Environment:

TYPO3: v13.4.17
Crawler: v12.0.9
Indexed Search: v13.4.17 (core)
PHP: 8.3.26 and 8.2.29 tried

Configuration:
Database (tx_crawler_configuration):
name: simple-indexing
processing_instruction_filter: tx_indexedsearch_reindex
processing_instruction_parameters_ts: recursive=1\nindexConfigUid = 0
TypoScript (setup.typoscript):
typoscriptpage.config {
index_enable = 1
index_externals = 1
}

plugin.tx_indexedsearch {
settings {
targetPid = 59
rootPidList = 1
}
}
Expected behavior:
Pages should be indexed in index_phash table when crawler processes the queue with tx_indexedsearch_reindex instruction.
Actual behavior:

Crawler processes successfully (Status: OK)
procInstrParams correctly contains indexConfigUid => ’0’
No entries are added to index_phash table
Frontend indexing works correctly (manual page visits do index)

Additional info:

Manual indexing via Backend module works
Hook in ext_localconf.php added but doesn’t help
index_config table is empty (possibly related?)

Workaround:
Currently using frontend indexing with “Disable Indexing in Frontend” unchecked.

When trying to index via console i get this output:
./vendor/bin/typo3 crawler:buildQueue 1 simple-indexing -vvv && ./vendor/bin/typo3 crawler:processQueue -vvv
Putting 1 entries in queue:

[2025-10-10 11:29] https://*******/
Unprocessed Items remaining:0 (b5e564969474da834b240394b3d1d971)
2

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Files 5

History 2

  1. Benni Mack commented and changed status New Needs Feedback <span data-processor="relativetime" data-value="2026-09-23T23:36:16+00:00" > 09/23/26, 23:36 </span>

    Thanks for the detailed report.

    This is not a Core issue as far as I can tell. With “Disable indexing in Frontend” enabled, indexed_search only indexes a frontend request if some listener enables it via EnableIndexingEvent. Before v13 the crawler passed this on via $GLOBALS[‘TSFE’]->applicationData, which was removed in v13 (see Breaking-102600, which also mentions that the crawler needs to use the event instead).

    So EXT:crawler needs to listen to TYPO3\CMS\IndexedSearch\Event\EnableIndexingEvent and call enableIndexing() when processing a tx_indexedsearch_reindex queue item. Could you please check with / open an issue at the crawler project (tomasnorre/crawler)? As a workaround you can register such a listener in your own site package for now.

    I’m closing this one for Core, feel free to re-open if you can reproduce it without the crawler. Is that OK?