Bug #21084: Pages in Workspaces are not editable anymore, course of a "PHP Catchable Fatal Error" - TYPO3 Core - TYPO3 Forge

Actions

Copy link

Bug #21084

closed

Pages in Workspaces are not editable anymore, course of a "PHP Catchable Fatal Error"

Added by Michael Elzer over 13 years ago. Updated over 9 years ago.

Status:

Closed

Priority:

Must have

Assignee:

Susanne Moog

Category:

Workspaces

Target version:

Start date:

2010-08-09

Due date:

% Done:

Estimated time:

TYPO3 Version:

4.5

PHP Version:

Tags:

Complexity:

Is Regression:

Sprint Focus:

Description

If you are working in a workspace and try to click on a page using the left mousekey to open a menu, the following error appeared (similary to Bug-ID 15292):

PHP Catchable Fatal Error: Argument 2 passed to t3lib_iconWorks::getSpriteIconForRecord() must be an array, null given, /typo3_src/typo3_src-4.4.2/typo3/sysext/cms/layout/class.tx_cms_layout.php on line 570 and defined in ~/typo3_src/typo3_src-4.4.2/t3lib/class.t3lib_iconworks.php line 735

Bug happens only in workspaces - Live-Edit works fine. Had to go back to 4.4.0.

Problem appeared since 4.4.1 and stayed in 4.4.2.
(issue imported from #M15401)

Files

15401-ws-lang.patch (790 Bytes) 15401-ws-lang.patch

Administrator Admin, 2010-08-11 18:01

Related issues 2 (0 open — 2 closed)

Actions

Copy link

Updated by Georg Ringer over 13 years ago

sorry I can't reproduce it. can you tell which steps need to be followed to reproduce it.
- Are you working in the page module (templavoila?) or in the workspace module?
- On which icon do you click?

I tested with current trunk

Actions

Copy link

Updated by Michael Elzer over 13 years ago

- Login as administrator or as a user who has access to more than one workspace and the live-environment
- Choose a workspace (problem appears on all of our workspaces)
- Change to view "Web ~~> Page"~~
Click on the title of the page (to get a overview of the content on the right side)

The error-message should appear now.

If a user has only access to one workspace, the problem does not appear.
We don't use templavoila.

Actions

Copy link

Updated by Michael Elzer over 13 years ago

Addition:

If a Page has no translation, the first translation of this page in another workspace works fine and no error message appears. All additional translation of this same page in another workspace ends in the error message.

It looks as if the error appears only when a translation was created in another workspace. Pages who are completed/translated and do not appear in any workspace work fine and no error-message is displayed.

Actions

Copy link

Updated by Georg Ringer over 13 years ago

sorry, still not reproducable.

Actions

Copy link

Updated by Georg Ringer over 13 years ago

To Reproduce:
1) Requirements: 2+ WS, 2+ languages
2) Create a page in Live WS
3) Create one translation in WS #1
4) Switch to WS #2 > Errir

Actions

Copy link

Updated by Susanne Moog about 13 years ago

Assignee deleted (~~Georg Ringer~~)
Target version deleted (0)

Should be fixable by making the function exec_languageQuery in db_layout.php workspaces aware.

Actions

Copy link

Updated by Susanne Moog about 13 years ago

Assignee set to Susanne Moog

Actions

Copy link

Updated by Tolleiv Nietsch over 12 years ago

Status changed from Accepted to Needs Feedback

Anyone able to reproduce it atm (running 4.6beta)?

Actions

Copy link

Updated by Christian Buelter over 12 years ago

I could reproduce this with the TYPO3 introduction package 4.5.5:

1. Switch to a workspace.
2. Create a language page overlay.
3. Create a text element on that page in the new language.
4. Switch back to live workspace.
5. Open the page usinge the "page" module in the backend.

Actions

Copy link

#10