FilterOptionHook::processDatamap_afterDatabaseOperations is processed on updates / changes on sys_category in non-live workspacees.
If a sys_category record is edited in the non-live workspace, a copy of the original record is created. A new tx_kesearch_filter entry is created for this new sys_category record. As a result, there are several filter entries for a category in the system. This is a problem because the search filters are created in the live workspace and are therefore immediately visible in the frontend.
Perhaps the creation of the search filter should only be executed when the change is in the live workspace, or during the workspace publishing process.
FilterOptionHook::processDatamap_afterDatabaseOperations is processed on updates / changes on sys_category in non-live workspacees.
If a sys_category record is edited in the non-live workspace, a copy of the original record is created. A new tx_kesearch_filter entry is created for this new sys_category record. As a result, there are several filter entries for a category in the system. This is a problem because the search filters are created in the live workspace and are therefore immediately visible in the frontend.
Perhaps the creation of the search filter should only be executed when the change is in the live workspace, or during the workspace publishing process.
TYPO3 12.4.17 ke_search: 5.2.1 composer: yes