Enable working with SysFolders in CONTENT
When using the pages table in CONTENT, only pages with doktype below 200 will be queried, but it should be possible also to fetch SysFolders.
The patch adds a new TS property CONTENT.select.dontCheckDoktype to enable all pages no matter what doktype.
(issue imported from #M11797)
#12 Updated by Sybille Peters over 1 year ago
Thank you for your report.
Even though it has been some time, would you consider checking if your patch idea is still up to date and upload it to our Gerrit review server?
Someone could do this for you, but I am thinking you might like the opportunity to contribute to TYPO3 yourself.
You can find a description of the TYPO3 contribution workflow here: https://docs.typo3.org/typo3cms/ContributionWorkflowGuide/
Hint: If you get stuck anywhere, ask on Slack in the #typo3-cms-coredev channel. You can register in the TYPO3 slack workspace here: https://forger.typo3.com/slack
Thank you in advance!
#14 Updated by Benni Mack 6 months ago
following up on the twitter discussion here....
Can you explain what your use case is?
Fetching stuff from sys folders in general is no issue, and should work already.
When do you actually want to show a sys folder in the frontend? Adding an option is doable, but adding an option for the sake of it and a special use-case seems weird to me.
For a more generic approach, I tried to actually "not care" about any doktypes except 255 (recycler), thus including all the other magic fields, so this could e.g. work for mount points, which would make sense IMHO. But this would lead that people can actually link to a storage folder (because PageRepository is used for linking as well and validating valid pages in FE).
So, if we get more input on what (all of you) try to achieve, we can find a better solution with a cleaner architecture in general, and avoid (even more) magic.