Hi Kory,
I have experienced this on each of the betas at some point, plus css failures on initially loading the theme (that required clearing styling cache to resolve)
Thanks, @scotbaston. I’ve noted this down to be investigated. Any chance you could get us access to this site? Even better would be setting up the “old” version of the site somewhere that we could login to and run the upgrade ourselves to see what is happening in that process. Thanks!
here you go,
I have restored to this morning’s backup which was at Beta 2, to give you the chance to update to beta 3 as requested
a couple of things to note, there is Object Cache Pro, and WP Rocket cache. neither of which does anything on refresh until the clear styling cache is cleared
@scotbaston Are you using Firefox?
I’m getting this even in some Pro 5.1.5 sites when using Firefox. Seems hit and miss though.
I was experiencing these problems with Chrome. I do use Firefox developer on occasion but I’m back to using Chrome as my daily driver
Thanks, guys. We’ve got this noted and are looking into it.
@scotbaston, is the site you provided login credentials to having some other issues at this time. When I login and then go to the frontend of the site, it would seem that the whole WP Adminbar has lost its styling and is not outputting properly?
it looks fine to me,
I have plenty of other pro sites on this server that don’t have issues, but have found with this beta that when I first install a new beta I need to clear the object cache pro, the wp rocket cache and the styling cache, sometimes multiple times
@scotbaston, the admin bar seems to be fixed on the frontend now (it was fine in the backend), but now when I try and go to the Cornerstone app, I get this:
I’m getting lots of errors like this one in the console:
Access to CSS stylesheet at '{{website}}/wp-content/themes/pro/cornerstone/assets/css/app/app.84cd168.css' (redirected from 'https://cdn.shortpixel.ai/spai/q_orig+ret_img+to_webp+v_1/{{website}}/wp-content/themes/pro/cornerstone/assets/css/app/app.84cd168.css') from origin '{{website}}' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Wondering if some of your caching setup needs to be cleared out or is holding onto some things, and perhaps that’s why you had the styling error you referenced earlier?
That looks like the short pixel cdn. I’d forgotten that site was using it. I’ll disable it and see if that fixes things.
shortpixel is disabled now… does that change things for you?
@scotbaston, yes…now that that is disabled, I’m not seeing any issues in the builder and I can’t replicate that observer style error. Probably all related to the various caching / CDN settings used here.
I normally exclude the cornerstone and pro folders from the cdn. Is there anything else pro related that I may have missed?
@scotbaston, nothing I can think of at this time. I just realize that this isn’t an issue we’ve seen any widespread reporting of, and due to the presence of various caching / CDN services you’ve had running and some of the issues I was experiencing upon logging in, at this time it feels like it points to something relating to that. We will certainly keep an eye on it, but that is my hunch at this time…you’re no longer experiencing the original issue mentioned in this thread, correct?