V 5.0.2. Update Question

[scrambler]

@weaver would probably have to have access to the admin of the staging site

[GR8FL]

That’s fine. I can email it to him. Just let me know where to send it.

[Weaver]

I have about 25 sites running on a single SiteGround account.

That includes this site which is running bbPress, a fairly resource intensive site, and it does not generate any sort of timeouts.

All of my sites use Cloudflare also.

I’v not finished yet, but I’ve autoupdated every one of my sites to Weaver V5.0.3.  Just found one site using an obsolete WordPress setting that is not supported in V5, and will release V5.0.4 to handle that problem, but I’m sure it is a very rare issue, and is a long holdover for the WP background color setting which is not supported by most themes these days.

There has to be some SiteGround issue, especially since reverting to 4.4.8 does not stop the problem. Other than using extra memory and needing a large value for passing settings values (I can’t remember the exact terminology at the moment, but it is well documented), there is nothing special about how Weaver would use resources.

[GR8FL]

@weaver

What would you suggest then?

My staging site is hosed. I lost most of my data, and still would have to reinstall Weaver Show Posts, Weaver Xtreme Plus, Weaver Xtreme Theme Support

My 2nd staging site is running Weaver XtremeVersion: 5.0.2 and
Weaver Xtreme Theme Support 5.0.2. Should I upgrade the theme to 5.0.3?

My live site is running Weaver XtremeVersion: 5.0 and
Weaver Xtreme Theme Support 5.0. Should I upgrade the theme to 5.0.3 and the plugin to 5.0.2?

 

[Weaver]

This reply has been marked as private.

[GR8FL]

This reply has been marked as private.

[Weaver]

I’m sure there are tutorials, but it isn’t overly difficult. If there is an existing site, much of it is automatic.

You create a Cloudflare account.

You add the Cloudflare plugin to each site you want to add.

You go to Cloudflare, add a url, and it will create its own DNS table.

Finally, you have to go to your registrar and change the DNS addresses (usually 2 of them) that point to your hosting site to the addresses Cloudflare provides. Cloudflare figures out your host’s addresses when it creates the new site entry.

When you make changes, you may have to enable development mode on Cloudflare to avoid its caching. That may be the biggest hassle.

[GR8FL]

Update: The culprit for CPU spikes, 504 Gateway Errors and general havoc was due to a plugin: Timely All-in-One Event Calendar.

I have disabled it on my staging sites, but still need to find a good alternative for the live site.

I feel like a jerk in putting @weaver & @scrambler through all this. Yes, there was an initial problem with updating theme to 5.0x with my header and menu bar width, but that was resolved before this thread started.

Thank you so much for your support and patience.

What a crazy way to start off the new year.

And in time, will look into Cloudflare.

 

 

[Weaver]

Just bad timing I guess. It can be hard to track all the little changes.

But this is yet another example of why we often ask users to deactivate other plugins to be sure it isn’t Weaver. But it is not always easy to remember or even detect issues with plugins until you’ve already moved on from adding the plugin.

[GR8FL]

I thought this was resolved by removing the plugin. Everything on the staging sites performed well. So I updated the live site and am having serious issues with what appears to be coming from the theme. SiteGround gave me this report:

baseos | [email protected]:~/www/sussexaa.org/public_html/wp-admin$ tail -f php_errorlog
[02-Jan-2022 23:41:01 UTC] PHP Warning: Cannot modify header information - headers already sent by (output started at /home/customer/www/sussexaa.org/public_html/wp-content/themes/weaver-xtreme/includes/lib-content.php:357) in /home/customer/www/sussexaa.org/public_html/wp-includes/http.php on line 492

What I have running with Weaver is

Weaver XtremeVersion: 5.0.5

Weaver Xtreme Theme Support 5.0.2

And in trying to backup before I restore using Updraft Plus, I see this warning: Warning: Your WordPress installation has a problem with outputting extra whitespace. They recommend looking at this page: https://updraftplus.com/problems-with-extra-white-space/

Is this related?

<hr />

Update: I restored from backup and now am running version 5.0 for the theme, and version 5.0 for the theme support. I checked the Updraft Plus section and the message about extra whitespace is gone. All is good now.

Checking the staging site which is also running fine has version 5.03 for the theme and version 5.0.2 for theme support plugin.

 

[scrambler]

I just crash my test site with 5.0.5 , not sure if related, still trying to figure out a way to gain access back to my site…

[Weaver]

Seems to be a PHP bug for some versions of PHP. Just uploaded 5.0.6 that seems to fix it.

[scrambler]

@weaver, How can I regain access to login ??

[Author]

Posts