Bug #88048
closed
PageLayoutController selecting wrong available languages
0%
Description
Error you will get (TYPO3 v8.7.24):
Argument 2 passed to TYPO3\CMS\Core\Imaging\IconFactory::getIconForRecord() must be of the type array, boolean given, called in /vagrant/webapp/htdocs/public/typo3_src/typo3/sysext/backend/Classes/View/PageLayoutView.php on line 900Prerequisite:
- You need Workspaces activated
- Create a page in Live WS
- Translate this page in another WS
- Switch back to Live WS in Page Layout Module, you can see that another language is available to select (which is wrong, as this language change is in WS not in Live)
- Switch from Column Mode in Language Mode and the Page Layout Module gives error message above (as we try to select this translation which do not exists in Live so we get a false instead of the row array).
Regression:
This is a regression from the patch of #77558 "Doctrine: Migrate PageLayoutController", I added a notice in the review https://review.typo3.org/c/Packages/TYPO3.CMS/+/49521
Updated by Alexander Opitz over 5 years ago
In TYPO3 10-dev (where I tested but IMHO this is also valid for v9lts) the whole process changed as we do not have pages_languages_overlay anymore. So 2 pages are created for the workspace thing (NEW_PLACEHOLDER_VERSION and NEW_PLACEHOLDER) and so the process is another one and it won't break. In v8 we only have the NEW_PLACEHOLDER entry.
Updated by Mona Muzaffar over 5 years ago
- Category changed from Backend User Interface to Workspaces
Updated by Georg Ringer over 4 years ago
- Related to Task #77558: Doctrine: Migrate PageLayoutController added
Updated by Georg Ringer over 4 years ago
- Status changed from New to Needs Feedback
we won't fix that for 8 anymore, is it ok to close the issue?
Updated by Georg Ringer over 4 years ago
- Status changed from Needs Feedback to Rejected
we won't handle this issue in 8 anymore as 8 is soon EOL
Updated by Gerrit Hübbers over 2 years ago
Our TYPO3 10 installation also ran into this error message when accessing some pages in the backend while the "language"/"Sprachen" (not "Spalten") presentation was selected.
The error message happened on pages which had been created with the workspace functionality in the past - workspaces being something we don't use/have activated anymore in our installation.
The following SQL update fixed the problem for us - be aware that this solution may or may not destroy data in other circumstances, especially when using workspaces (something that we don't use anymore):
```
update pages set l10n_source = l10n_parent, t3_origuid = 0 where l10n_source != l10n_parent;
```