Bug #88586

No pseudo-site found in root line for workspaces

Added by Philipp Seiler over 1 year ago. Updated 9 months ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Workspaces
Target version:
-
Start date:
2019-06-18
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
9
PHP Version:
7.3
Tags:
pseudo,site,workspace,edit,rootline
Complexity:
Is Regression:
Sprint Focus:

Description

No pseudo-site found-Exception occurs when trying to edit a page in live-workspace. A different workspace version of the page exists.

Within TYPO3\CMS\Core\Site\PseudoSiteFinder->getSiteByPageId() TYPO3 tries to get the corresponding pseudo site by traversing up the rootline from the currently selected page. The rootline however only contains the page UIDs of the non-workspaced pages, but the method wants to find a pseudo site from the workspaced page UID. The pseudo site is therefore never found and triggers an exception.

Possible solution: If the page has a t3ver_oid field, use that ID to traverse up the rootline.


Related issues

Related to TYPO3 Core - Bug #85985: Error: No pseudo-site found in root line of page 3Closed2018-08-27

Actions
Related to TYPO3 Core - Bug #86186: No pseudo-site found in root line for workspacesClosed2018-09-07

Actions
#1

Updated by Philipp Seiler over 1 year ago

  • Related to Bug #85985: Error: No pseudo-site found in root line of page 3 added
#2

Updated by Philipp Seiler over 1 year ago

  • Related to Bug #86186: No pseudo-site found in root line for workspaces added
#3

Updated by Riccardo De Contardi 9 months ago

  • Status changed from New to Needs Feedback

May I ask if this has been solved with #86186 ? If not, how can I reproduce it? Could you please add a step-by-step guide? Thank you and sorry for the late reply.

#4

Updated by Philipp Seiler 9 months ago

Riccardo De Contardi wrote:

May I ask if this has been solved with #86186 ? If not, how can I reproduce it? Could you please add a step-by-step guide? Thank you and sorry for the late reply.

To be honest, I can't seem to remember anymore, how the error occured. So until I reencounter this error, it'll probably be OK to close this issue.

#5

Updated by Riccardo De Contardi 9 months ago

  • Status changed from Needs Feedback to Closed

@Philipp Seiler thank you for your quick reply; I am closing this issue for now.

If you think that this is the wrong decision or experience the issue again, please reopen it or open a new issue with a reference to this one. Thank you.

Also available in: Atom PDF