Double menu

I still see LiteSpeed Cache activated:
https://www.screencast.com/t/cX1caZJG

Please clear then disable.

Done

Are there any server cache that you are aware of?

Right now it's calling for a file in GP Premium 1.7.2 which doesn't exist if you are using the alpha version:
https://www.screencast.com/t/ZKGBxcsA

No, as far as I know, there is nothing

Any chance you can check with your host?

Really can't think of another reason why this would happen...

Let me know :)

I'm still thinking there's some sort of caching going on. Server caching? Cloudflare?

Your site is still requesting this file:

<link rel='stylesheet' id='generate-mobile-header-css' href='https://yourwebsite.com/wp-content/plugins/gp-premium/menu-plus/functions/css/mobile-header.min.css?ver=1.7.2' type='text/css' media='all' />

mobile-header.min.css no longer exists in GPP 1.8.0, and you'll see the version is still set to 1.7.2. When you try to open that URL, the file doesn't exist on the server (as it shouldn't if you're using 1.8.0).

So something is caching the output of your page.

Yes, it makes very good sense. Allthough, I've asked my host, and there is no server caching from their part.

Are you using a service like Cloudflare?

No Tom, I'm at a loss here

Can you clear your caching plugin and then deactivate it and keep it off so I can look?

Thanks!

Done Tom, thanks

Any chance you can send me temporary admin login details so I can take a closer look?: https://generatepress.com/contact

Let me know :)

Sent

I just took a closer look. The frontend of your website is cached to when you were using GP Premium 1.7.2. We can confirm this by looking at the source of your website and searching for "1.7.2". You'll see all of the resources have the 1.7.2 query string, meaning the frontend of your website still thinks it's using 1.7.2.
​
The only explanation for this is caching. It's not browser caching, so it must be either plugin caching or server caching.
​
I trust you cleared the cache using your LiteSpeed caching plugin? If so, the only explanation is server caching.
​
You can, of course, switch back to 1.7.8, but you'll likely run into this issue again when you update if you don't figure out where the cache is coming from.

Okay Tom, thank you very much for your effort. For now, I will switch back to 1.7.8. How do I do that? :-)