Bug #88048

PageLayoutController selecting wrong available languages

Added by Alexander Opitz about 1 year ago. Updated 6 days ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
Workspaces
Start date:
2019-04-01
Due date:
% Done:

0%

TYPO3 Version:
8
PHP Version:
Tags:
Complexity:
Is Regression:
Yes
Sprint Focus:

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 900
Prerequisite:
  • You need Workspaces activated
HowTo Reproduce:
  • 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


Related issues

Related to TYPO3 Core - Task #77558: Doctrine: Migrate PageLayoutController Closed 2016-08-21

History

#1 Updated by Alexander Opitz about 1 year 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.

#2 Updated by Mona Muzaffar 12 months ago

  • Category changed from Backend User Interface to Workspaces

#3 Updated by Georg Ringer 28 days ago

  • Related to Task #77558: Doctrine: Migrate PageLayoutController added

#4 Updated by Georg Ringer 28 days ago

  • Status changed from New to Needs Feedback

we won't fix that for 8 anymore, is it ok to close the issue?

#5 Updated by Georg Ringer 6 days ago

  • Status changed from Needs Feedback to Rejected

we won't handle this issue in 8 anymore as 8 is soon EOL

Also available in: Atom PDF