Issue Bug Closed

#88204Page Caching with restricted pages in page tree breaks menu

Walter Sparding 04/25/19, 10:52 updated 07/03/20, 21:47

Description

Using TYPO3 9.5.5 PHP 7.2.17

I have a multi-level-menu, which contains restricted pages for frontend-users.

The menu is always fine, until nobody is logged in.

If i logout as fe_user the menu breaks.

At the part of the menu, where the restricted page exists, it does a ul for the submenu, but the /ul is missing, and the restricted page is not in the menu. It seems, as TYPO3 somehow knows, there is a submenu, but then realizes, that the user (session?) is not logged in, and therefor may not see this page.

This gets more weird if i open 2 browsers with the same page one logged in, the other not. If i then clear all caches and reload in browser1 the menu is ok, but when reloading browser2 the menu is broken for browser2.

After struggling deeper and deeper, i found out that setting cache_hash of the cacheConfiguration to TYPO3\CMS\Core\Cache\Backend\NullBackend all is working right the way it should.

Setting back to default Cache TYPO3\CMS\Core\Cache\Backend\Typo3DatabaseBackend breaks the menu again.

IMHO that is not a error in TS of the menu, cause the menu is always right, when all caches are cleared.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.