Skip hidden content/records on indexing #155
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mbrodala
force-pushed
the
index-command-skip-hidden-content
branch
from
76e2352 to
b20137a
Compare
The "visibility" aspect set up by the TYPO3 CommandApplication includes hidden content (and thus records) by default. This can be seen especially when using the Extbase persistence during the indexing process. Related objects ignore any enable fields and are loaded unconditionally. This whole topic very likely needs further investigation and additional restrictions (e.g. skip hidden pages and scheduled records) but left for another change.
mbrodala
force-pushed
the
index-command-skip-hidden-content
branch
from
b20137a to
9dd2cfd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The "visibility" aspect set up by the TYPO3 CommandApplication includes hidden content (and thus records) by default. This can be seen especially when using the Extbase persistence during the indexing process. Related objects ignore any enable fields and are loaded unconditionally.
This whole topic very likely needs further investigation and additional restrictions (e.g. skip hidden pages and scheduled records) but left for another change.