Dropdown Menu Stuck Open on Blog Post Pages After CMS 2.0 Update

[Pegasus]

I’m currently testing something on one of my test blogs.

While doing that, I noticed the following issue:

I’m using the Dropdown component in my header menu with several links inside it.

Now I’ve discovered that only on my individual blog post pages, the dropdown menu is already open when the page loads, and I also can’t close it anymore by clicking.

Examples:

• Keto, Vegan & Co: Was steckt hinter den verschiedenen Ernährungsweisen
• Kochen Leichtgemacht - Hauptsache es schmeckt!

It should actually behave like this:

• Kochblog

Before switching to CMS 2.0, everything worked without any problems. Other than the CMS update, I haven’t changed anything else.

@dan @ben
Any idea what could be causing this?

PS: Uploaded to Support

[dan]

It appears the required javascript isn’t loading, I’m wondering if it has something to do with the way you have things setup in the blog

For example it’s looking for js files, but can’t find them. See the safari console error report below:

Ah-ha! After further investigation, I think it’s broken because you’re added a base href to the blog page

To fix the issue, stop doing this

[Pegasus]

OK, but where would then be the best place for <base href="/blog/">?

If I want to use pretty URLs, I need to use that, right!?

If not there, then where is the correct place for it? Because without it, my layout completely breaks and becomes unusable…

Pretty URL's | CMS | RapidWeaver Elements Docs

[differentdan (Daniel)]

Hey @Pegasus

If I move your base tag up in the head section like so:

Then your menu works on those pages, like so:

[Pegasus]

works!

Thank you very much!

In fact, during the first days of ECMS 2.0, I originally had the <base href="/blog/"> tag exactly in that place.

I can’t fully remember anymore what the issue was, but it caused some kind of problem on the websites, which is why I later moved it into the “headers” area instead.

Most likely, one of the bug fixes from the past few days resolved that issue, and now everything works correctly again.

In any case, thank you very much — it’s really a great feature that is slowly but surely turning the entire Elements app into a true WordPress alternative. Keep pushing until the summer break