-
Notifications
You must be signed in to change notification settings - Fork 52
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
TYPO3 9.5: Still error when accessing page properties #417
Comments
Looks like did it not find it's way into the master and latest release yet...
|
These changes help me to edit the page properties again,
as is said, what helped with this issue was to edit:
changing
to
i can edit page contents again, but still run into template issues if i check pages in frontend view |
Have the same issue after update form If parent page has No one code changes form above didn't help. Just got a little different message
Now
|
The same error with copy -> paste pages. Add new page possible just with drag and drop |
I have the same error on two instances. |
@olegkarun Flux 9.3.2 have fluidpages inside so you should remove fluidpages to avoid conflicts. |
Thanks @rupasix in that case this issue can be closed. I got everything running now by only installing flux instead of fluidpages. |
Hi FluidTYPO3 team,
i still have issues with accessing page properties or working with pagecontent.
I made a clean new install of Typo3 9.5 () with vhs ("fluidtypo3/vhs": "^6.0") and fluidpages ("fluidtypo3/fluidpages": "^5.0") via composer.
As soon as I add a page I run into
trying to edit page properties and
if I want to add/edit pagecontents.
The page properties problem I did solve via mentioned changes (#409 ) in ext/fluidpages/Classes/Backend/BackendLayoutDataProvider.php
The main problem was that I am not able to add/edit page contents. After some debugging I stumbled across resolveTemplateFileForControllerAndActionAndFormat() in vendor/typo3fluid/src/View/TemplatePaths.php. In that method
$this->templatePathAndFilename !== null
condition does return an empty stringvalue because $this->templatePathAndFilename is after a clean install just an empty string value and not null.
That leads straight into the 'InvalidTemplateResourceException' from Line 598.
After changing that '$this->templatePathAndFilename !== null' condition into !empty($this->templatePathAndFilename) I can edit the page content like before.
Now I run into the issue, that I am not able to get my Backend Layouts of my extension working. I am not sure if that is because of the Changes in TemplatePaths or if I have problems with my extension. Maybe someone is able to have a look at that condition (Line 254) in TemplatePaths.php and can verify that this is a cause for that
issue.
cheers
Bernhard
The text was updated successfully, but these errors were encountered: