-
-
Notifications
You must be signed in to change notification settings - Fork 248
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pages:extendToSubpages not recognized #53
Comments
AFAIR What TYPO3 version are you on? Can you please make sure this behavior is not caused by another extension you may have installed. |
I was able to reproduce this now when using the |
I'll now work on this |
I've worked on this issue and implemented a functionality in the GarbageCollector and RecordMonitor to apply recursive deletion or reindexing under certain conditions. I've added the above mentioned "triggers". It would be nice when you can check if this resolved you problem / requirments. PR can be found here: #192 |
I tested your patch, and while I'm thankful for your effort, we're not quite there yet: My test pages:
When I deactivate page A, page B stays in the index. (This is how it should be) 1319116885: exception 'RuntimeException' with message 'Failed to execute Page Indexer Request. See log for details. This also means that even if i set extendToSubpages back to 0 on page A, page B can't be indexed anymore. I'd have to manually delete page B from the index queue table in the database for that to happen again. |
@seirerman Thanks for your Feedback. Which TYPO3 Version are you using? Can you maybe check what is in the log? Here the same use case is working. I'll try to reproduce this. |
We're on 6.2.17. Devlog says it got a 404 from page B which is correct. |
@seirerman I've adjusted the patch and checked it on my installation. Can you maybe check again, if everything is fine now? |
Yes! Looks good to me. |
When I deactivate a page and additionally set the flag extendToSubpages to 1 (quite handy if I want to hide a big part of a website), its subpages will be deactivated, too.
But Solr still lists them in the search results, which leads to 404 errors.
Since the records of the subpages aren't changed, Solr doesn't notice this, and the scheduler task remains at 100%.
Clearing the index and reindexing all pages at least removes the hidden pages from the search results, but also leads to indexing errors for all those subpages:
The text was updated successfully, but these errors were encountered: