B9: Upgraded to B9 on existing site - content editor seems to have lost editing / utility styles

Beta
#1

Just upgraded to B9 on an existing site to test the upgrade process out. Fairly simple site, using a few plugins but nothing too crazy I don’t think. After upgrade, everything seemed to look fine on the front-end, no issues there.

Going in to the content editor, some strange things happening. The hover outlines on elements (along with the little tab to indicate element name, and column width markers in row / column layouts) look like they’ve lost some styling and are showing up as shown below:

image
image1517×680 253 KB

Can give access if required

#2

Looks like the whole preview.css file is missing. Could you open your browser’s developer tools and see if you’re getting a 404 error for that file? I’m wondering if something went wrong with the theme update. Did you update via FTP or the WordPress theme uploader?

#3

I think this issue actually solved itself - or it was a caching issue (I had purged the cache immediately post upgrade, but have since done a deeper cache flush from the cPanel interface for the SiteGround Optimizer plugin) which sorted out the preview.css issue.

However, there then popped up a new issue to do with js files. The builder was loading only the header and footer, and the main content area was not showing up at all. In the chrome console, this was the error showing up:

cornerstone-site-body.min.js:1 Uncaught SyntaxError: Malformed arrow function parameter list
x-site.min.js:1 Uncaught SyntaxError: Malformed arrow function parameter list
react-dom.min.js:103 TypeError: Cannot read property 'everinit' of undefined
react-dom.min.js:53 Uncaught TypeError: Cannot read property 'everinit' of undefined

Which was then resolved by turning off just the JS Minification in the cache plugin being used (SiteGround Optimizer). I was able to turn back on JS Minification, with specific file exclusion for /themes/pro/cornerstone/assets/dist/js/site/cs.847fab8.js and /themes/pro/framework/dist/js/site/x.js, and everything worked as expected.

I guess this is not a massive issue, as JS Minification is often something that requires a bit of care when turning on, however it was never a problem with previous version of Pro (currently all sites I’ve built have the SG Optimizer, and most have JS Minification on with no issue—front-end of back-end) so I wonder if it is something that can be sorted out?

#4

Thanks! Glad it’s working now. Unfortunately we can’t really do much to support external minification of JS. Our assets are actually already minified so it’s ok to exclude them. When it comes to minifiers, it’s really the responsibility of that system to make sure whatever comes in comes back out as valid javascript. There really isn’t a good way for us to troubleshoot that on our end.

1 Like
#5

Fair enough, I thought that might be the case.
Thanks for looking into it though!

#6

No problem. Appreciate your understanding with this one.

1 Like