- This topic has 9 replies, 3 voices, and was last updated 2 weeks ago by
.
-
Posts
-
We’ve discovered yet another issue when updating to Weaver Xtreme 6.2.1.2 – auto theme updates.
The problem fixed in the latest version of Weave Xtreme requires clearing a CSS cache the theme generates. Clearing the old cache is required to fix some sites using some Custom CSS options. And because the theme will only touch the database while logged as an admin, one must be logged in to clear the issue.
For most users, this will happen when logged in to update the theme. But if the theme is auto-updated by WP or a plugin, the theme will indeed be updated, but the cache will not be cleared because it never opens the site as an admin.
Sorry about that. This has been one of the trickiest bugs in the history of the theme, and really needed an admin login to fix automatically.
So, if your site has been updated to Weaver Xtreme 6.2.1.2 and you are still seeing stray CSS or some of your Custom CSS is not working, then you will need to login as an admin and actually open the site to clear the problem.
Best way to assure theme fixes applied:
- Login to site as admin
- Be sure theme updated to 6.2.1.2
- While still logged in as admin, open site visitor view in new window to confirm fix applied
Everything is almost certainly OK. The popup should be a one-time thing.
And it seems that there are several ways the theme can be updated – all the way from updating from the main dashboard, to an auto update, to opening the themes list. And sometimes the popup message will show, and sometimes it generates the headers already sent message. Seems to depend on the method used to actually do the update. Maybe it would have been better to not show the notice, but it will be a one time thing.
But either way, it does seem the theme gets updated and the cache reset.
Looking at the site with the link, it does confirm the theme has been updated because the version does display as the latest in some of the link and style html code.
I have continued to test the website. The messages I’m getting are definitely not a one time thing.
This popup seems to occur just about every single time I update anything using the legacy interface or the if I update anything from the CSS custom rule box using the “Fonts & Custom” section.
I’ve also noticed a couple of times that after making a change, I unexpectedly saw the “headers sent” warning message as a white screen of death message (not just a dashboard message), but I was able to hit the back arrow to get back to the site.
I notice so far, I can avoid the warning message more often if I click on “Visit Site” instead of clicking “Dashboard” after a change, but I may still get the popup instead, but I shouldn’t be getting a white screen with the headers sent message.
There should be a way to turn off these messages. They are frequent and unpredictable.
Can this occur if a user logs in an creates a new blog post, or does this just effect updating the theme setting?
@larua –
Thank you for your persistence.
Sigh. As soon as you clarified the issue was associated with the Legacy interface, I knew what the problem was.
I missed a tiny update to the Legacy library that is part of the theme (vs. the Theme Support plugin).
So, I would appreciate it if you would verify the fix before I upload to the WP repository.
Weaver Xtreme 6.2.1.3 is available for direct download here, just below the link to the WP repository:
The message with all the header sent stuff will be gone, and the css cache will still be updated (which in fact it is every time you save settings).
Now as for the Customizer vs Legacy….
I understand that you are very familiar with the Legacy Interface, and it in some ways is easier to navigate.
BUT, and this is my own experience, the Customizer interface is in the end is (for me at least) way faster to tweak your site design.
The main (and I find it huge) advantage is the instant (or near instant) refresh of the actual site in the site layout to the right of the Customizer.
The WHERE Customizer interface follows fairly closely the organization of the Legacy Interface. And in fact, the Customizer has become very fast. New settings will update instantly for most settings, while the minority that do require a page refresh happen very quickly these days.
And, there are quite a few new Weaver Xtreme options that are supported by the Customizer interface that have not been retro-fitted into the Legacy Interface. These include, among others, font styling options, outlined fonts, menu options (including the new grid layout), and options for replacing the header and footer with totally custom designs.
But in the end, it is the instant update of what your changes really are without having to flip back and forth (and manually page refresh) from the Legacy interface to the view of the site that for me makes the whole process easier.
As for the new Block Themes… with them, WP has seemed finally embrace the concept of a way to add options for nearly every part of page design. I suppose one would learn the new workflow and the ability to tweak so many parts of the design, but I find the need to switch back and forth, and figure out just which option panel to open on the right hand side of the editor to be somewhat difficult. But for now, I don’t think there is any other theme that gives the totally flexibility of Weaver.
Sorry about the sales pitch…
Please let us know if the 6.2.1.3 version cures the issue with the CSS cache update messages / header already sent problems.
I upgraded two websites with version 6.2.1.3 and they both seem to be behaving normally again.
I’m no longer getting either the pop up message or the “headers already sent” messages.
Question:
When I apply 6.2.1.3 to my other Weaver installations, should I expect a one time pop up or will this version suppress that?
I understand why you are encouraging me to learn the customizer. I guess I am used to the legacy interface because that is the way that I taught myself how to design a website with the Weaver theme when I first learning. I go back a long way with the Weaver learning curve with the Legacy interface. I think the reason I haven’t bothered with the customizer so much is because I’ve never had any caching issues with any of my Weaver sites and they update pretty fast as it is and I am not really doing much new website production.
If I start learning with the customizer, can I flip back to the Legacy interface until I feel comfortable with it?
Thank you so much for all your help.
As part of 6.2.1.3, I did remove the popup message. Figures it probably doesn’t give that much info, and is certainly annoying when it is triggered in such a way to generate those header already sent messages. And the critical update the popup notified about was done, but the fact it was was not saved by the Legacy version.
You certainly can switch back and forth between Customizer and Legacy – all Customizer settings are saved by Legacy, even if not supported with options. (That was actually the cause of the problem you experienced – I failed to add the code that had the Customizer save the CSS cache status value).
The Weaver Xtreme Plus fonts are also not listed in the Legacy Interface. I might fix that, but not high priority. Adding options to the Legacy is kind of a pain which is why it is not keeping up with the Customizer options.
- You must be logged in to reply to this topic.