- This topic has 28 replies, 3 voices, and was last updated 1 year, 5 months ago by
.
-
Posts
-
My post seems to be hosed. Trying again. Do I need to do the following if nothing seems broken with the theme update?
- Allow WP to update both the theme and the plugin to V5.0.2.
- After the theme updates, OPEN the theme in the customizer (or Legacy Settings). Make some small change, then change it back to the original. Now Publish or Save the settings. This should regenerate everything.
And is opening the legacy editor and doing something in custom CSS sufficient as described in #2 above?
Thank you.
And happy new year.
Yes, you should do these steps.
If things are still messed up, you may want to redo it all
- Revert back to 4.4.8
- Update the Xtreme Theme support plugin to its latest 5.0.2 version.
- Redo the v5 update to the latest 5.0.2 version.
- Clear ALL your caches (plugin, cloudflare, browser….)
- Go in Appearance > Xtreme Admin > main Options and click “Save Settings” to refresh everything.
My site is not messed up after the update.
I will do the steps anyway, but wondering if opening the legacy editor and doing something in custom CSS, and then saving is sufficient.
If you are on the latest versions 5.0.2 of both the theme and the theme support plugin and have saved settings, you are fine
Not sure if this is related, but all my plugin updates are timing out. I have running Version 5.0 Weaver plugin and theme. I have tried to update other plugins and get bad errors with plugin deactivation. I contacted hosting site (SiteGround) and they report a huge CPU spike. Does this have anything to do with these versions?
Below is one message from a plugin update attempt
Update failed: <!DOCTYPE html> 504 – Gateway Timeout * { box-sizing: border-box; -moz-box-sizing: border-box; -webkit-tap-highlight-color: transparent; } body { margin: 0; padding: 0; height: 100%; -webkit-text-size-adjust: 100%; } .fit-wide { position: relative; overflow: hidden; max-width: 1240px; margin: 0 auto; padding-top: 60px; padding-bottom: 60px; padding-left: 20px; padding-right: 20px; } .background-wrap { position: relative; } .background-wrap.cloud-blue { background-color: #b0e0e9; } .background-wrap.white { background-color: #fff; } .title { position: relative; text-align: center; margin: 20px auto 10px; } .title–regular { font-family: ‘Roboto’, Arial, sans-serif; } .title–size-large { font-size: 36px; line-height: 46px; } .title–size-semimedium { font-size: 20px; line-height: 28px; } .title–weight-normal { font-weight: 400; } .title–weight-bold { font-weight: 700; } .title–subtitle { padding-bottom: 40px; font-family: ‘Open Sans’, Arial ,sans-serif; text-align: center; } .error h1, .error p { color: #226d7a; } .error–bg__cover { position: absolute; width: 100%; } .error–shape__clouds svg { display: block; } .abstract-half-dot–circle { z-index: 0; position: absolute; left: 15em; right: 0; width: 300px; height: 300px; margin: 0 auto; } .icon-graphic { z-index: 1; position: relative; width: 300px; height: 300px; margin: 0 auto; } @media screen and (max-width: 767px) { .error–bg__cover { display: none; } .abstract-half-dot–circle { left: 0; } } bg_error_lines circle_dots .st0{fill:#fff;} .st1{fill:#226D7A;} .st2{fill:#22B8D1;} 504 – Gateway Timeout This is a temporary error. Please try again later. clouds_shape
Not quite automatically – you’ll be given a prompt from WP if you want to update the existing one with the uploaded one. That is fairly new, and long overdue. Makes rolling back so much easier.
It is very hard to re-create exactly what happens when you use V5 for the first time while logged in as an admin, but I’m now fairly confident that doing almost anything (including editing a post), and then opening the visitor side view while still logged in (in the same browser) will cause V5 to update all the settings and files it needs.
You just rolled out theme version 5.0.3? Is there a same version number for the plugin too?
Is this what is causing all my errors? I am getting so many CPU spikes on the SiteGround end, and trying to update plugins (not just Weaver) is causing 504 – Gateway Timeout errors. I also cannot connect to ManageWP anymore – the connection is timing out.
The 5.0.3 update handles autoupdate of sites when the theme does not acutually generate the required custom css files for the settings – changed so it now knows it needs to use inline CSS if it hasn’t been used from a logged in admin account.
While there are signifidcant changes, there aren’t any changes that should affect conection or anything to cause timeout errors. I think that has to be co-incidence.
I rolled back to 4.4.8 and then installed 5.0.3. Got same error, though site did load. SiteGround is telling me there are huge CPU spikes and blaming the theme plugin.
Below is error after theme update.
Update failed: <!DOCTYPE html> 504 – Gateway Timeout * { box-sizing: border-box; -moz-box-sizing: border-box; -webkit-tap-highlight-color: transparent; } body { margin: 0; padding: 0; height: 100%; -webkit-text-size-adjust: 100%; } .fit-wide { position: relative; overflow: hidden; max-width: 1240px; margin: 0 auto; padding-top: 60px; padding-bottom: 60px; padding-left: 20px; padding-right: 20px; } .background-wrap { position: relative; } .background-wrap.cloud-blue { background-color: #b0e0e9; } .background-wrap.white { background-color: #fff; } .title { position: relative; text-align: center; margin: 20px auto 10px; } .title–regular { font-family: ‘Roboto’, Arial, sans-serif; } .title–size-large { font-size: 36px; line-height: 46px; } .title–size-semimedium { font-size: 20px; line-height: 28px; } .title–weight-normal { font-weight: 400; } .title–weight-bold { font-weight: 700; } .title–subtitle { padding-bottom: 40px; font-family: ‘Open Sans’, Arial ,sans-serif; text-align: center; } .error h1, .error p { color: #226d7a; } .error–bg__cover { position: absolute; width: 100%; } .error–shape__clouds svg { display: block; } .abstract-half-dot–circle { z-index: 0; position: absolute; left: 15em; right: 0; width: 300px; height: 300px; margin: 0 auto; } .icon-graphic { z-index: 1; position: relative; width: 300px; height: 300px; margin: 0 auto; } @media screen and (max-width: 767px) { .error–bg__cover { display: none; } .abstract-half-dot–circle { left: 0; } } bg_error_lines circle_dots .st0{fill:#fff;} .st1{fill:#226D7A;} .st2{fill:#22B8D1;} 504 – Gateway Timeout This is a temporary error. Please try again later. clouds_shape
You may want to do the following:
- Save your settings, and download a copy locally for safe keeping.
- Then switch to a different theme.
- Then deactivate and DELETE ALL weaver theme and Weaver plugins (Xtreme, Xtreme theme support, plus, etc…)
- Then reinstall the Xtreme theme from WordPress , check if any errors.
- Then reinstall each Weaver plugin, and see if there are any errors
Ever since I updated the theme and plugin am having troubles on the SiteGround hosted site.
CPU Spikes
Pages taking forever to load
Timeout errors
Can’t even connect to ManageWP which is my backup/restore app.
I finally as a test disabled all plugins and reverted to the 2014 theme just to see what CPU spikes and timeout issues I was having. Then I slowly added each one back. As soon as I added the Weaver theme (5.0.3) and Weaver plugin (5.0.2.), the timeout errors began again and could no longer connect to ManageWP.
Reinstalling the theme causes errors again. I would like to revert back to 4.4.8 which I have as well as the theme plugin, which I don’t have.
Adding that this issue is only happening on the SiteGround site. I have other sites hosted elsewhere.
Downgrading the theme to 4.4.8 still isn’t working.
I have the following plugins deactivated:
Weaver Show Posts
Weaver Xtreme Plus
Weaver Xtreme Theme SupportSo I am at a loss.
When you switched to 2014 did you DELETE all weaver theme and plugins and not just disable them?
If something became corrupted, only deleting them all will clear the issue
Same issues. So far this has been on a staging site, but every other site is also having problems. SiteGround says it’s not them – and nothing that suggests that there is an issue with the site. The server itself is (and has been) running optimally.
Bottom line for me is it is not working. Continually am getting 504 – Gateway Timeouts.
So far nothing is working with this, but I have to move on with my day.
If you have other ideas, I am open to try them.
- You must be logged in to reply to this topic.