Bug #87475

Filelist error - RootllineUtility tries to fetch deleted page by sys_file_storage UID

Added by Reinhard Schneidewind 3 months ago. Updated 2 months ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2019-01-18
Due date:
% Done:

0%

TYPO3 Version:
9
PHP Version:
7.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

When accessing the filelist an error is thrown:

#1343589451 TYPO3\CMS\Core\Exception\Page\PageNotFoundException
Could not fetch page data for uid 2.

typo3_src-9.5.3/typo3/sysext/core/Classes/Utility/RootlineUtility.php line 262

As far as I can see the RootlineUtility tries to fetch the page data by the sys_file_storage uid.
In my case the uid is 2. Furthermore a page with uid 2 exists, but is deleted. This causes the error to be thrown.

The problem is caused by the GET parameter id:
example.com/typo3/index.php?route=%2Ffile%2FFilelistList%2F&token=TOKEN&id=2%3A%2Fapplikationen%2F

The RootlineUtility seems to interpret the id always as pid, even it's the sys_file_storage in that case.

History

#1 Updated by David Backes 2 months ago

Reinhard Schneidewind wrote:

When accessing the filelist an error is thrown:

[...]

As far as I can see the RootlineUtility tries to fetch the page data by the sys_file_storage uid.
In my case the uid is 2. Furthermore a page with uid 2 exists, but is deleted. This causes the error to be thrown.

The problem is caused by the GET parameter id:
example.com/typo3/index.php?route=%2Ffile%2FFilelistList%2F&token=TOKEN&id=2%3A%2Fapplikationen%2F

The RootlineUtility seems to interpret the id always as pid, even it's the sys_file_storage in that case.

Same Issue here, couldn't open any directory in Filelist, same Errormessage as shown above.

Backround: During an update from older Typo3 to the new 9 Version I did copy the whole Pagetree and deleted the old one and cleard the database. So the page with Uid 1 was completly gone.

Workaround: I created a new page, and set the UID manually via database to 1, now everythings works fine, even when I set the Page with uid to deleted=1, and why ever, even after I deleted the page from database again.

It also works after I removed the t3boostrap-Extension, because the Error Trace shows a Problem in an User Condition used in the t3bootstrap part of Typoscript Rendering. This User Condition uses the function from RootlineUtility from core and this produce the error as Reinhard Schneidewind wrote above.

I am not sure if the error is from t3boostrap, or core or if ther just was some strange cache behaviour tricks me.

I cannot reproduce the error, t3boostrap is active like before and the page with Uid 1 doesn't exists. I know it sounds weird, but if the error returns I will post the trace here.

#2 Updated by David Backes 2 months ago

UPDATE:

We need a page with the same Uid as the Filestorage, otherwise the error occures again after a couple of hours.

Also available in: Atom PDF