You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Im using TYPO3 8.7.32 with flux 9.5.0 on two different projects for page layouts and content elements. Both pages have multiple languages and on both sites I got the problem, that the settings (page settings) for the translated page are empty.
For the default language the settings are fine.
I haven't enabled the setting to show the page configuration field on translated pages.
Also I checked the database. In pages_languages_overlay the field for the settings is empty.
I updated both projects to the latest flux and TYPO3 version. Before this the error does not happened.
Anyone else here who can confirm this problem?
Or someone here who has a workaround to fix this problem?
Best
The text was updated successfully, but these errors were encountered:
On my TYPO3 8.7.30 instance and using flux 9.5.0, when configuration translation is not enabled, the configuration used by flux seems to be the on set or inherited from the subpage configuration.
This is - apparently - the default behavior of TYPO3, but only when it concerns the "pages" table. I have no idea why, though. It simply will not copy almost every field of this specific table when doing a "localize" command.
Hi there.
Im using TYPO3 8.7.32 with flux 9.5.0 on two different projects for page layouts and content elements. Both pages have multiple languages and on both sites I got the problem, that the settings (page settings) for the translated page are empty.
For the default language the settings are fine.
I haven't enabled the setting to show the page configuration field on translated pages.
Also I checked the database. In pages_languages_overlay the field for the settings is empty.
I updated both projects to the latest flux and TYPO3 version. Before this the error does not happened.
Anyone else here who can confirm this problem?
Or someone here who has a workaround to fix this problem?
Best
The text was updated successfully, but these errors were encountered: