June 5, 2023 at 00:13 UTC - Views: 74 #72995Private ReplyWeaverKeymasterThis reply has been marked as private.June 5, 2023 at 09:04 UTC - Views: 60 #72997
Hi @weaver. Thanks for your hard work on my site. Indeed it works now as it ever had.
So the issue came, as I though from one of weaver updates.
As as said earlier, the issue was there the first time after an update to weaver 6 and disappeared after the next one to come back with the actual.
Perhaps it could be interesting to try what happens with the different versions of 6x (I tried to revert the entire site to 220.127.116.11 and it seemed to work but with loosing all my work since there) but you can only change the weaver versions one by one from 5.1.1 to 18.104.22.168 ?
Of course you can clone my site, you have my permission and confidence.
Another problem is the absence of the option Additional CSS even now with weaver 5. That has no effect on the the site but is strange. As I said on two other sides I created and manage, the option is there and weaver 6.2 works fine.
Many thanks again and I am sure, you will clear up the misteryJune 5, 2023 at 12:10 UTC - Views: 58 #72998
When I tried to edit my message, there was a long time 503 error. What I wanted to add :
Where can I find the extreme 5.1.1 version you installed on my site ? If I try something on my site, I must be sure I can revert to this version. On the archive download page of the weaver site there is only the 5.5.1 version which probably but not surely works too.
The issue with the primary menu color is the only one I noticed. No issue with the primary menu bg color, no issue with the submenu color or bg color. That seems to me the most strange.June 5, 2023 at 12:16 UTC - Views: 56 #72999
Wordfence did’nt find any issue. Yes I already tried deactivating all non weaver plugins. The maintenance was @Weaver working hard to find a solution. He finally reverted the theme to version 5 which resolve for now the problem as you can see. Mais le mystère reste entier ! A suivre. MerciJune 5, 2023 at 16:19 UTC - Views: 53 #73002
You may like to consider using the plugin: WP Rollback when you want to roll back to a previous version of a plugin or theme.
It work very well and is very easy and fast to use, as all past versions are immediately available. I have been using it for years for an instant fix when there is a update conflict. Wouldn’t be without it!
You will find 5.1.1 and all versions there….
Regards!June 5, 2023 at 18:20 UTC - Views: 45 #73008
I used the wp rollback plugin, thank you @user, and the result is that the issue with the primary menu color comes from xtreme 22.214.171.124 When I rollback the theme to 6.2 there is no issue but after that, 126.96.36.199, 6.2.1 188.8.131.52 etc the issue is there. I hope that will help you find out what was going on between 6.2 and 184.108.40.206June 5, 2023 at 18:31 UTC - Views: 43 #73009scramblerModerator
Great data @beethoven, I am sure weaver will appreciate it, it should definitely help pinpoint what is going on.June 6, 2023 at 00:37 UTC - Views: 39 #73015WeaverKeymaster
I loaded two special versions of Weaver Xtreme to our site: “Weaver Xtreme 6.2” and “Weaver Xtreme 220.127.116.11”.
After properly setting the Menu setting for each new version of the theme to “accueil” both versions work as expected when logged in.
However, the not-logged-in version does not reflect the menu being set properly, and instead shows the default version of the menus which was displayed the first time I tried one of the special versions.
What this says is that someone is caching. And the cache seems to be very sticky. At the moment, I’ve left the site using the 6.2 version you got from WP Rollback. But here in the US when not logged in, I’m seeing HTML code generated by the “Weaver Xtreme 6.0” version generated on my very first try before properly updating the Primary menu setting. I can tell this because of line 10 in the html output has /weaver-xtreme-6-2-0/ in it that tells me that. Which in turn tells me that the non-logged in view has been cached.
So, @beethoven , what you need to do is find out where that caching is happening. For example, I’ve discovered that my host, SiteGround, is doing it own caching (without telling me) that can create a similar situation. I can go to my hosting account and force the cache to clear, but it seems to self-clear after some period – maybe an hour? But it does make it look like changes I’ve made aren’t there until I force clear the cache.
I highly suspect that there is no problem with the theme now (there may have been a problem with the > in the theme, but I think that is gone now). It is just that you aren’t seeing the real version on non-logged in views withing a reasonable time frame.
That is the only explanation I can think of that would explain the wrong thing on the non-logged in view.June 6, 2023 at 01:23 UTC - Views: 37 #73016WeaverKeymaster
Duh – it is WP Super Cache.
I turned off Caching and can see updates.
Right now, I’ve left caching off, but you can turn it back on if desired.
I’ve left it with Weaver Xtreme 18.104.22.168 which was a pretty stable version before I released 6.2.1.
The 6.2.1 versions seem to not work again on your site, so that is a new starting point.
I was having trouble with the Customizer not saving – don’t know what that might be – but it may not do that for you. If you try and the the something went wrong message (so unhelpful), you can resort to the Legacy interface.
I’ll try to get back to this a bit tomorrow.June 6, 2023 at 02:07 UTC - Views: 32 #73017
I was going to write this yesterday, but after reading Weaver’s comments… I now write immediately.
Have you re-started/ reboot the server to see if this clears things?
I say this, because over the weekend I had a similar minor issue, but the more I did, the worse it got… even when all setting were correct. After Rebooting the server, the site was back functioning 100% in >4 min.
Just a thought….
Regards!June 6, 2023 at 09:55 UTC - Views: 28 #73020
I am not sure to understand everything because of my bad english
Yesterday the color issue began with xtreme 22.214.171.124 today it begins with 6.2
Yesterday the Customizer saved the settings. Today, in all 6 versions the settings are not saved in the Customizer. In the 5 version they are still saved and working
Super cache is deactivated and I don’t know of another cache. I’ll ask my host but I’m pretty sure there is no cache at that level.
If there were a caching problem would it not concern all changes and not only changing the primary menu color ?
I really do not know what I could do more on my side. I hope, @weaver, you canJune 6, 2023 at 09:59 UTC - Views: 23 #73021
Have you tried to reboot the website server — redémarrer le serveur du site Web ?
Regards!June 6, 2023 at 10:08 UTC - Views: 20 #73022
@user, I am not self hosting the site ! I just asked my host about an eventual caching on server side. Only they could reboot the serverJune 6, 2023 at 18:23 UTC - Views: 11 #73023scramblerModerator
I assume you have tried reinstalling the latest WordPress update to refresh things on that side.June 6, 2023 at 21:39 UTC - Views: 9 #73024June 6, 2023 at 21:42 UTC - Views: 8 #73025
Good new, the customizer now saves the settings again … bad new, but not the primary menu color
- You must be logged in to reply to this topic.