Project

General

Profile

Actions
Copy link

Bug #91570

closed

Pagetree not shown due to error in TYPO3\CMS\Backend\Controller\Page\TreeController

Added by Simon Gilli almost 4 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Pagetree
Target version:
Candidate for Major Version
Start date:
2020-06-03
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
10
PHP Version:
7.4
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Whenever I create a BE-User-Group and a BE-User (gave him the group) and change to the User (normal-user) I get an error:

Page tree error - 500
    Got unexpected response from the server. Please check logs for details.

And the log entry:

Core: Exception handler (WEB): Uncaught TYPO3 Exception: Cannot use object of type __PHP_Incomplete_Class as array | Error thrown in file /var/www/share/xxx.xxx.de/app/releases/13/web/typo3/sysext/backend/Classes/Controller/Page/TreeController.php in line 190. Requested URL: https://xxx.xxx.de/typo3/index.php?route=%2Fajax%2Fpage%2Ftree%2FfetchData&token=--AnonymizedToken--

We have the same error in different installations -> same TYPO3 version

TYPO3 v10.4.3
PHP 7.4
MariaDB 10.3

Have done all tasks in the wizard. After that I cleared all caches after run wizard.

See https://forge.typo3.org/issues/91407#note-14

Related issues 1 (0 open — 1 closed)

Related to TYPO3 Core - Bug #91407: Pagetree not shown due to error in TYPO3\CMS\Backend\Controller\Page\TreeControllerClosed2020-05-14

Actions
Actions
Copy link
 #1

Updated by Simon Gilli almost 4 years ago

  • Related to Bug #91407: Pagetree not shown due to error in TYPO3\CMS\Backend\Controller\Page\TreeController added
Actions
Copy link
 #2

Updated by Simon Gilli almost 4 years ago

  • Target version changed from 9.5.18 & 10.4.3 to 11.0
Actions
Copy link
 #4

Updated by Benni Mack over 3 years ago

  • Target version changed from 11.0 to Candidate for Major Version
Actions
Copy link
 #5

Updated by Torben Hansen over 2 years ago

  • Status changed from New to Needs Feedback

Just just stumbled over this ticket. Clearing the backend user settings resolves the issue as mentioned in the linked Slack discussion.

Since there came no feedback from the reporter, I think we can close the issue.

Actions
Copy link
 #6

Updated by Riccardo De Contardi over 2 years ago

  • Status changed from Needs Feedback to Closed

I think it is safe to close 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 very much for your patience.

Actions
Copy link

Also available in: Atom PDF