Issue Bug Rejected

#23957nested XMENU_LAYERS and the typo3temp *.js caching bug

Janos 11/05/10, 18:06 updated 04/01/13, 11:52

Description

The bug occured when i tried to fix the typo3temp bug (0012376).

I’ve created an nested XMENU_LAERS navigation. With an GMENU_LAYERS on level 1 an TMENU_LAYERS on level 2 and level 3 an TMENU.

For each solution i tried i had the result that the level 3 TMENU didn’t disapear.

First i tried to avoid this bug like in description of Bug (0012376) by setting an layer_menu_id for level 1 and 2.
Result: Serverside looks fine, only on *.js file for varius requests. But level 3 didn’t disapear.:-(

After that i set the layer_menu_id only for level 1.
Result: Frontend looks fine (level 3 disapear) but for each request i had 2 new *.js files.

After that i checked out the solution 4_4 rev 9037 described in the last notice of bug (0012376). Without set an layer_menu_id for each level.
Result: The sam e as in the first test, only on *.js file for varius requests. But level 3 didn’t disapear.

Those are only a short excerpt of my try.
Task 0012376 seemed to me the best approach. Cause it is marked as resolved and commited to trunk.
I also tried a lot with the TMANU_LAYER parameters and configuration.

To retrace i’ll attache the ts-code in text file.

I am grateful for any help
(issue imported from #M16268)

Reviews 0

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