Conversation
Moving: Extra_WebUI_Modifications apply to after "$TEMP_MENU_TREE" has been created and after _CreateMenuAddOnsSection_ / Sitemap injection has finalized the menu state.
Yeah, the order of execution is critical to make sure the check is done at the right point in the sequence. |
Martinski4GitHub
left a comment
There was a problem hiding this comment.
Approved the changes!!!
|
After a closer code review, I found a couple of things that should be changed as well. |
I wont lie, I initially took a bit of a guess where it should go in the Mount_WebUI function, and clearly, I guessed wrong LOL |
Right now we do this in this order:
That means on a fresh boot, Extra_WebUI_Modifications apply can run before menu_Addons exists in "$TEMP_MENU_TREE",
So .menu_Addons never gets added to /tmp/index_style.css.
Later in the same startup, CreateMenuAddOnsSection adds the Addons menu, but
the CSS decision was already made.
Quick fix is moving: Extra_WebUI_Modifications apply to after "$TEMP_MENU_TREE" has been created and after
CreateMenuAddOnsSection / Sitemap injection has finalized the menu state.