After updating to version 11.4, Megamenu was corrupted.

Hi,

All pages, sub-pages and articles on our site work with templates that we download from “Cloud Templates” which maked changes according to our wishes. Header and Footer work the same way. The “Header 2 Overlay” title we use on the homepage is also used for other article templates.

It was working fine until I updated it to 11.4 which is the latest version of Newspaper theme. After the update the Mega menu structure was broken as seen here. Although the same menu is defined for this template, there is no corruption here.

When I open the homepage with tagDiv composer, there is no corruption in the menu, as can be seen here.

When I open the homepage in a browser where we are logged in with the admin user, there is still no corruption as seen here.

I tried many ways. First, I opened the homepage with tagDiv composer and saved it again. I did the same for Header. I cleared all cache on server and browsers; the problem is not solved.

What do you recommend?
Our Web address: Arthenos.com

Thanks in advance for your interest and help.
Best regards!

• This topic was modified 4 years by Demir.
• This topic was modified 4 years by Demir.
• This topic was modified 4 years by Demir.

Hi,

Before opening this support ticket, we tried the method you suggested first. Now we tried once again.
– As can be seen here, all CSS files generated by tagDiv CSS Analyzer have been removed.
– All cashe cleaning done.
The result has not changed.

Regards

Hi again,
Could it be that the “Remove generated CSS” option doesn’t remove all?
Regards.

Hi,

Our site is used intensively at all hours of the day. Trying to disable all plugins except tagDiv as you suggested means the site will not work.

If we do this with the “Troubleshooting” mode, this will not work as we will connect with the admin user, because when we log in with the admin, this problem does not appear.

Therefore, I open a support request and send the information you requested to the support address.

Regards!

Hi,

As a result of the support team’s control, it was determined that this problem was caused by the LiteSpeed Cache settings we used. Correct settings were made and the problem was solved.

Thank you very much for your support.
Best Regards!

• This reply was modified 4 years by Demir.