This issue does not seem to be related to either CSS or HTTPS. To me it looks like a logic problem in Dokuwiki. When you see the blue bar, the <li> element has the CSS class active while it lacks this class when its inactive.
So whatever PHP code in Dokuwiki that determines the active state of menu items is broken.
@tmomas - I figured it out. The actual problem was that https://lede-project.org/sidebar lacked a ~~NOCACHE~~ tag.
Without that, the sidebar state is rendered once and then cached forever, so the blue menu highlight stayed at what happened to be the active menu item when the sidebar menu was first rendered after clearing the cache (or updating the config).
Perhaps the includeSubDomains attribute should be removed from HSTS setting Strict-Transport-Securitymax-age=31536000; includeSubDomains to prevent this affecting some new subdomain/subsite in future.
Yeah, that makes sense. I'll remove it.
Edit: removed now
Thanks.
The change seems to work as expected. E.g. it is now possible to visit buildbot with http after visiting wiki/www (with https).
Jow, big thanks to you. This drove me nearly mad yesterday.
Interesting to see that the caching was the issue. Caching might also be the root cause for the double dataentry issue in the ToH, but that's yet to be confirmed.
I there a reason why the issue q https://bugs.lede-project.org/ is not added to the left sidebar as this forum is? I find it kinda hidden as it is know.
We're working hard to keep the sidebar to a minimal state, so that the site (and the navbar) remains "discoverable". The items at the top are pretty much orthogonal, so that people can quickly home in on what's interesting to them:
The "Development" link goes to the top-level Developer Documentation page that has links to all the resources, including the Bug Tracker, since developers are the major users of the bug tracker.
I would have no qualms about adding a link to the main User Guide page at: https://lede-project.org/docs/user-guide/start
Sorry about the slow reply. Took a long holiday off the grid.
I completely understand the need to keep the amount of menu links down. Too many links are just confusing. What about creating a ... lets say, a root menu entry called "Support" and under/in that page include both the forum and the bug tracker, etc.? I still think the bug tracker should be easier for the end user to locate. Especially since LEDE "soon" goes from dev and into a more stable state, inviting more non technical users to install it.