Pro broken after 2.1.2 update

Hi,

OK so I’ve set up a subdomain and copied everything over, and…frustratingly, everything now works! Aaarrgh!

The site is exactly the same except for one thing. As I am using a sub-domain, my PRO license is not valid and so I could not automatically update it. So I had to delete and install manually. That’s the only difference. All plugins are still running.

Clearly a the original site is operating in a parallel dimension where the laws of physics are not the same!

Thanks
S.

EDIT: This may be a red-herring but, if I inspect both the working page and the broken page I see an error in the broken one. See secure note.

Hi there,

How about moving your staging live? Maybe it will overwrite any internal cache and since it’s the same copy.

The error is related to Ember used in the builder, and it should only appear where it’s loaded (builder). And could be due to internal cache too.

Please note the CF uses cache, there is no point in using it if all requests are just going to pass-through, which means it still served by your site. And all CDN like CF served the cached files for the purpose of dividing the traffic (hence, not served from the original site). It will serve the cache working or not, and the main problem with that is CF has no way of telling if your site is updated for it to generate a new copy of cache.

Thanks!

I’m using CF because it provides SSL, not because it provides cache.

Hi there,

Sorry for the confusion, I’m not saying you use CF because of cache. But CF uses cache(or similar) regardless of setup you use. Even if you turn off it, it will still work as CDN, and CDN creates a mirror of files across cloud servers. And since they are duplicate files, it’s also similar to cache since it’s not the original copy. Purging is needed too.

I have similar experience and turning off caches and purging doesn’t take effect, only when I remove CF nameservers on my domain.

Have you moved your staging to live site?

Thanks!

Hi,

As I’m sure you know, it is no trivial matter to move a site from a subdomain to the main domain so I’m disinclined to do that unless there is a specific logical reason for doing so. (I copied all the files from the main site to the subdomain so I don’t see the point of copying them back again).

However, I’m going to investigate CF some more, as you say, and see if I can uncover anything. As CF provides my SSL I will have to turn all that off on my site temporarily.

I’ll report back shortly.

Thanks
S.

Hi,

OK, some progress (and at the same time, more confusion).

I turned off CloudFlare caching. It has a Dev mode whereby it routes all traffic direct to the site, so I put this on. It made no difference.

Then I switched off CF altogether…in other words, I just used CF nameservers (DNS only). In doing this, I had to switch my site over to HTTP. This WORKED!

So…finally…

I switched caching back on, and changed the setting in CF so that HTTP was NOT redirected to HTTPS.

Now

  • if I access Wordpress via HTTP, the link Pro->Content works.
  • if I access Wordpress via HTTPS, the link Pro->Content does NOT work.

Not sure where that leaves us.

Thanks
S.

Hi S.,

I’ve accessed https://skyhawkpictures.co.uk with https:// which I can tell is using Pro theme version 2.1.3 with SSL certificate issued by cloudflaressl.com, however I can get the builder working fine as you can see:

That’s really weird that this issue happens only at your end, I can see you have tried using many browsers, would you mind to just try another PC? Just wanted to narrow this issue down to either a caching issue or not.

Thanks.

Only my PC and only from 2.1.2 onwards. 2.0.4 was fine. Bizarre.
I’ll try on different machines and report back.

ok get this…

Remember my PC fine with Pro 2.0.4 but with Pro 2.1.3 it works over HTTP, but not over HTTPS.

So…

  1. Tried Macbook. Worked.
  2. Tried a beat up old laptop on my Windows domain, logged in with my domain account: Worked.

Then
3) A different domain account on the MY PC: Worked!!.
4) Me again on MY PC (to check I’m not going insane): Failed.

WTF? haha

What could it be on my PC that is failing (across browsers and even incognito)?

Thx S.

Hi There,

How did you introduce the SSL on your site? that seems to have failed. The Content Builder on your site works on our end (I tested it on 2 PC Win 7 & 10), (https://prnt.sc/jsa9vi) (https://prnt.sc/jsab59)

However, when we exit the builder your site is giving this notice



Notice the address, it redirect back to the non-secure protocol (http)

Please redo, how did you do introduce the SSL on your site, and make sure the WordPress Address (URL) and Site Address (URL) under Settings > General are change to (https)

You can follow the guide here to change all the entry of http://skyhawkpictures.co.uk/ on your database to https://skyhawkpictures.co.uk/ or use a plugin like Force SSL.

Let us know how it goes,
Cheers!

Yeh, I set that to http temporarily so that I could test HTTP and HTTPS, that’s all. It actually makes no difference to whether it works for me or not. It’s back at https now

Hello There,

Could you please update to the latest versions first?

  • Pro theme 2.1.5

This latest release contains fixes for several issues so be sure to check out the changelog (http://theme.co/changelog/).

_After doing the updates, always remember to clear all caches (if you are using WP Rocket, WP SuperCache or W3 Total Cache) when updating so that the code from the latest release is always in use. This will help you to avoid any potential errors.-

Please let us know how it goes.

That’s done.
No change.

Some good news. Not “great” news, but sanity news.
I went back to 2.0.4 again, the one that I thought was always working. It isn’t.

My check for this is to go to Pro->Content. If that page loads we’re good. If it doesn’t we’re not so good.
In 2.0.4 that page loads and I’ve been assuming we were happy.

But I’ve just noticed that Pro->Headers does not work. Pro->Footers does not work. And even though Pro->Content works, I cannot edit a page from there or jump to headers or footers.

So whilst I still have the problem…at least I have a n almost consistent problem across the board.

I’m going to update to 2.1.5 again.

Thanks
S.

I’m sure you’ll be glad to know that I’ve fixed it.

It was getting all too weird and unusual, so I decided to do a full site restore.
I restored to 16 May after my last major set of site changes. Checked that the Pro theme was working (it was) and then I have updated to 2.1.5. It is still working.

I have a bunch of out of date plugins, which I will update one at a time. If anything crops up that breaks Pro, I will report back.

Thanks
S.

Hey There,

It’s good to know that you have finally updated to 2.1.5 and it is not working back to normal.
Just make sure that every thing is up to date. In most cases, out dated WP, theme or plugins may caused conflict and other issues in your site.

If you need anything else we can help you with, don’t hesitate to open another thread.

Think you meant to say it IS working back to normal :smiley:

Just one final update. I have now updated all plugins to their latest version, cloudflare back on, everything back to the way it was…and it is now working.

So…don’t ask me what was going on there.

Maybe there was some theme or plugin update that failed part way or perhaps PHP memory limit hit. I don’t know. But it is all back up and running.

Thanks
Steve

There could have been some corruption. Glad it’s working now.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.