tx_fed_fcefile can be empty for new elements
leonlaser opened this issue · 2 comments
We configured our provider extension to use a subfolder Resource/Private/Provider for the three template directories (Layouts, Templates, Partials).
When adding a new content element to a column using the third or second or any other button between other content elements it can happen that the dropdown fortx_fed_fcefile will be empty.
It seems to be unable to find the individual typoscript configuration and falling back on the default template paths.
My current solution is to not use custom paths for templates in provider extensions.
You may need to help debug this one on your particular setup. I've tried and failed to reproduce the problem - in my tests, Flux's BackendConfigurationManager does resolve the correct PID, but does so via the standard ConfigurationManager from Extbase.
It's possible you are affected by one or more of the following:
- BackendConfigurationManager reads the wrong page UID because it is unable to resolve a TS template which 1) exists on a page marked as root and 2) is itself marked as root template. The configuration manager will use the first such created template.
- Your TYPO3 version may be outdated: for example, TYPO3 8.7.x has added a couple of bug fixes related to resolving of templates.
- The problem may have been solved with recent commits to fluidcontent which uses TYPO3 API to resolve templates (which means concerning TS config and template resolving: if it works in Extbase/Fluid, it works the same in Flux/Fluidcontent).
I'd advise you to try with dev-development branches of Flux and Fluidcontent and the most recent bugfix release of your TYPO3 version. As far as I've been able to debug, this problem is either solved or caused by incorrect setup.
But despite all the above: I would definitely suggest that you always use the default template locations.
Thank you for looking into this. I am going to check the possibilities you listed and give you feedback.