TYPO3 Core

got the same problem with a lot of sys_category records

in my clients Website there are 3000+

Had problem here too after editing and saving a page, directly after close, but it is not always reproducible or I rather I am still figuring out how to reproduce.

This is in an installation after update to v11 from v10 with several pages and extensions.

It might be helpful, if this is possible to reproduce with a standard installation.

The error message seems to be displayed by JavaScript for the PageTree, or more specifically in the SvgTree, but I do not know where the problem occurs.

Searched for "Navigation loading error". Is language label tree_networkError . This language label is used in SvgTree.ts, see

• https://github.com/TYPO3/typo3/blob/11.5/Build/Sources/TypeScript/backend/Resources/Public/TypeScript/SvgTree.ts#L132
• https://github.com/TYPO3/typo3/blob/61493346f8e8793b3619fe04816dcc3f24ff59b7/Build/Sources/TypeScript/backend/Resources/Public/TypeScript/SvgTree.ts#L640

A stacktrace might help to see where the errorNotification() was called. Unfortunately, the function is called in the JavaScript part so there is no message in the logs.

Got the same problem on 11.5.13. There are ~ 300 Categories, which take ~ 1.5s to fetch and a few more ms to render. If the backend form is closed before the categories are loaded, the error message "Navigation loading error" occurs.

Same here. After an update from the latest v10 to v11.5.14:

When saving a page after a edit, the big red

"Navigation loading error - Got unexpected response from the server. Please check logs for details."

Message pops up. Not everytime but rather random and very often. Can't find any hint in the logs...

Also editing and then saving a page became very slow. Wit TYPO3 v10 everything was fast and instant, with TYPO3 v11 this is not the case anymore.

It is a large site with more than 100 editors and over 4000 pages. But as I wrote, with version 10 we never had any performance issues.

Regards
Mike

I have the same problem with an update from v10 to v11.5.15 with PHP 7.4.
The project has many sys_categories.
If i edit a content-element and close or safe the element again, the error occurs (SvgTree error in browser console).
If i go to the category tab and wait till the categories are loaded and then safe/close, the error does not pop up.

My workaround to fix this error is to disable the categories tab for all tt_content elements. This is only a sutable solution, because i do not use the sys_categories for tt_content Elements:

TCEFORM.tt_content.categories.disabled = 1

Patch set 3 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/76443

Patch set 4 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/76443

Patch set 5 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/76443

Patch set 6 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/76443

Patch set 7 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/76443

Patch set 1 for branch 11.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/76473

I am still having this problem in TYPO3 11.5.24, more than 4k categories and 18k pages.

We also have such problems with big TYPO3 websites (TYPO3 11.5.24)

Can anyone who still has the problem post a log message from the logs (written by logging framework, e.g. in var/log / typo3temp/varlog)? This would help to figure out where the problem is and also check if sites are affected.

(I have not seen the problem for a while but I don't do too much editing).

Thanks Alexander. I can't reproduce it that way (with TYPO3 version 11.5.24) and 32127 pages (sys_language_uid=0) and 466 sys_category (sys_language_uid=0). Maybe not enough categories, but used to regularly get the message too. I agree it is probably canceled ajax request and did not have any log messages pertaining to this error either.

I would categorize the scenario described as non-error though (Clicking on page tree while loading edit form should probably cancel the request - though the flash message is maybe superfluous).

I have found an issue in my tca configuration:

Before:

'config' => [
    'type' => 'select',
    'renderType' => 'selectTree',
    'foreign_table' => 'sys_category',
    'treeConfig' ...
]

After:

'config' => [
    'type' => 'category',
    'relationship' => 'oneToOne'
]

Backend editing is faster with tca type "category" and the flash message appears not that often anymore.

A coworker notified me about this issue in a project when using the fileadmin with many images. The customer is very annoyed by those flash messages when they edit their content.

By the way: the same error Message is triggered for the page tree and the file tree as they both use the SvgTree class.

The problem is, that the editors select the image in the modal faster than the tree is built. When the image is selected the request is canceled, and the JS triggers the flash message. Error still exists in TYPO3 11.5.26-dev and 12.3.0-dev.

This can be easily tested with a plain TYPO3 11/12 and one image by slowing down the response of the controller with sleep(10) here: https://github.com/TYPO3/typo3/blob/11.5/typo3/sysext/backend/Classes/Controller/FileStorage/TreeController.php#L57

Dear watchers please see follow up ticket. This one is closed.

https://forge.typo3.org/issues/100219