Cornerstone not usable anymore (2.1.3)

Support
#10

Hello Guys,

Thanks for writing in! Most users rush to the updates and then if it does not work, tend to get frustrated which of course we always understand it especially if you are on a deadline. Before you update, we highly recommend that you always set up a staging area. This is very useful because you can test drive any X updates in the staging area, do the customizations and troubleshooting without disrupting your live site. Once everything is perfect, you can easily and flawlessly proceed the update in the live site. To know how to create a staging area, please check out these articles:
http://www.wpbeginner.com/wp-tutorials/how-to-create-staging-environment-for-a-wordpress-site/, https://maintainn.com/2015/02/how-to-create-a-staging-site-for-wordpress/

Now, after doing the updates, you also experienced issue like Cornerstone no longer working. It has worked before the updated and after doing so, it does not work anymore. One of the major cause of this issue is caching:

  • You have have installed WP Super cache, W3 Total Cache or any other caching plugin. You must always clear your plugin cache right after the updates or slight site changes.

  • Other users are using minify plugins or applied minification for the JS and CSS. Well you will need to regenerate the minified JS/CSS files first after doing the updates.

  • If you are using CloudFlare, you must purge your site cache too.

  • If you are using WPEngine or Site Ground, there is a caching feature in the server which you will have to clear the site cache too.

  • If you are on BlueHost, they have Endurance Cache which could also pose a problem if the cache is not clear.

  • Other servers has Varnish. The Varnish cache must be cleared too.

Hope this helps.

#11

Hello RueNel,

I think you are totally right by saying we need to check the updates in our staging areas but I guess you missed the point where there is a lack of quality in your software and we are having troubles now.

So as i cleared all caches and stuff please tell me what to do next as this error is continuing on my side. Is there a way to roll that update back until you have a decent fix for that bug?

On a second thoughtI find it also quite disappointing that it takes you more than 5 days to respond to an urgent topic, is there another way to get help in urgent topics faster?

Are you interested in looking into that topic? I can provide you with login credentials and access to my siteground hosting.

Thanks and best regards
Johannes

1 Like
#12

I can open the editor now but I am now unable to save any changes which is really annoying.

Anything I can fix that or is that just another bug?

All the best
Johannes

#13

Hi There,

Would you mind doing a plugin test? The error that we are seeing on the browser console from your site is not common and we cant replicate it on our end, so we can not say that this is a bug, but more likely with your site setup. If it’s not possible to deactivate all the plugins try purging the SG Optimizer cache and deactivate it for a while until we resolve the issue, also if the site is under an internal caching please deactivate it as well. This is to make sure that the site is serving us the updated resources and not a cached version.

Also, I advise to re-install the Cornerstone to make sure that there is no corrupted file due to fail update. The easiest way is to deactivate and delete the Cornerstone, then visit the X > Overview page so it reinstalls automatically.

If this does not resolve the issue, please provide us FTP credentials in “secure note” so we can investigate further.

Let us know how it goes,
Cheers!

#14

Well I deactivated pretty much all my plugins and still I am not able to save. Maybe you could assist in reinstalling cornerstone because in “x<overview” I do not find any option to do that.

Would it also be an option to install the last version? I can provide you the FTP credentials in the secure note but for me this is currently really blocking my work :frowning:

You can also try to deactivate the plugins again maybe I did something wrong but I tried to flush all caches.

Best regards
Johannes

#15

Hello Johannes,

It’s quite unusual, but have you changed the default login page URL? I tried accessing admin page using https://fitness-fuer-mamas.de/wp-admin/ and http://prasantrai.com/wp-login.php but it’s redirecting to https://fitness-fuer-mamas.de/login/ page which seems to be the course login page and the credentials don’t work there too. Here is the screencast https://screencast.com/t/WdAkCPPs

I can login to the FTP using the details you have shared but I need to see the WordPress admin page for any changes that we make using FTP. Can you please confirm WordPress login page URL? If it’s something I am missing, kindly let me know.

Thanks.

#16

Hey :slight_smile:

you can use this URL for the login:

And you can use the credentials in the first secure note

As far as I can confirm, it is an error in one of the cornerstone JS files.

Best regards
Johannes

#17

Hey @Johannes,

I can confirmed that there is a JS error in one of the Cornerstone files. And it is weird because it only happened in your site. We have tested X and Cornerstone in our local testing servers over and over but we cannot replicate the issue. Could you please give us access to your SiteGround and FTP so that we can manually update the files and check all other aspects why you are experiencing this issue. Could we also ask permission to update X and Cornerstone to the latest version?

Thank you in advance.

#18

Hello RueNel,

you can update Cornerstone and X and you should already have my FTP and Website Credentials but I will give it to you again

Hopefully you can fix this issue as I am running behind my schedule already.

Thanks for your help
Johannes

#19

Hi There,

Maybe you could assist in reinstalling cornerstone because in “x<overview” I do not find any option to do that

Navigate to the X > Overview page, and X will automatically re-install the Cornerstone for you. I did reinstall the Cornerstone, Purge the SG Cache and deactivate, and that enable me to save page in Cornerstone (I added 2 empty section at the bottom of this page), if you still see the error on your end, please do a hard page refresh (ctrl + f5 / cmd + f5), or use your browser’s incognito/private mode.

Though that did not resolve the persistent error, we like to do a plugin test and try switching to your parent theme (maybe something on your child theme customization is causing the issue), but we can not really do that on a user production site since you have a lot of essential plugins there. Please setup a Staging Environment so we can further investigate the site.

How to Create Staging Environment for a WordPress Site

Thank you,

#20

I solved one of the problemes by changing the template of the blog entry back to “Default Template” from “Fullwidth Layout”. I am still getting the initial error but I am able to save now.

So does that help to find the JS error on your side?

Best regards
Johannes

#21

Hi there,

I checked and I can’t find what’s causing it either. Is it okay if I disable all the plugins? It’s best to do that by staging server. That way, we can do full-scale testing without damaging your live site.

Thanks.

#22

I created a staging site using wp-staging, you can find it here:

You should be able to access it with the support credentials I send to you earlier.

Best regards
Johannes

#23

Hey @yoggelino,

When I logged in to your staging, I tested opening your page in Cornerstone and I get the error message. I deactivate all your plugins except Cornerstone and now it works. To prove that it works, I added an exclamation mark at the end of your text. See Secure Note.

Please enable your plugins one by one while checking Cornerstone each time you do that. You have 51 plugins activated when I checked… See Secure Note.

Thanks.

#24

Hey,

so I took the time and investigated further and the whole thing seems to be very strange:

  1. This error within your cs-vendor.js is caused by the follow-up plugin from woocommerce (https://woocommerce.com/products/follow-up-emails/)

Uncaught TypeError: this.indexOf is not a function
at HTMLDocument._emberMetalMixin.Mixin.create._Mixin$create.contains (cs-vendor.js?ver=2.1.7:34174)
at i (jquery.js?ver=1.12.4:2)
at Object.fireWith [as resolveWith] (jquery.js?ver=1.12.4:2)
at Function.ready (jquery.js?ver=1.12.4:2)
at HTMLDocument.K (jquery.js?ver=1.12.4:2)

  1. I think there is a general problem in your new cornerstone version because even when i deactivate the “follow-up” plugin i still get the error overlay with the error message “The preview was unresponsive after loading. This is most often related to a plugin conflict or aggressive page cacheing.”

  2. Now comes the strange part, if I open up the developer console and remove the error overlay I can just work perfectly fine

So from my side I think you should change the behavior when you throw the “unresponsiv” error message maybe the time and delay is to short because the site takes forever to load on my end. Also you generate more than 200 ember warnings in your js file maybe this is causing the terrible performance ending up in taking so long that it tells me that it is unresponsive.

So what are our next steps here? You check why your plugin has a problem with an official Woocommerace plugin? Also the performance and warning part needs to be adressed from my point of view I am really unpleased with the new conerstone version i wish i could go back 2-3 version where everything worked just fine and was super fast.

Thanks and best regards
Johannes

#25

I have exactly the same huge problem as @yoggelino since the last cornerstone update !!!

#26

Hey Johannes,

Thanks for the additional info. I’ll post the conflict between the WooCommerce Follow Up plugin and Cornerstone in our issue tracker. This might need a deep thorough investigation though so it might take some time. Right now, the only solution that I can think of is for you to revert from the previous working state of your site.

Regarding the other issue even when you deactivate the follow up plugin. It looks like an issue with cache. Please try deleting your browser cache and also check in incognito mode or other browsers.

@lilarosa,

Thanks for writing in. There are many factors that could affect any page builder especially after updating. With that said, please try the following general solutions suggested in our troubleshooting builder preview warnings article.

If nothing helps, please open a separate thread and post a link to this thread for reference and give us WP Admin access in a Secure Note there.

Thanks.

#27

I do not think it is related to caching or at least it does not seem to be, because the cornerstone plugin loads super long after I upgraded and there are tons of warnings and stuff in the console.

I guess you guys are firing this error message depending on a timeframe or something because when I get the error I can just remove the overlay using the developertools and just work with the plugin without any problems, so the only problem right now is the error message itself.

#28

Hey @yoggelino,

I’ve investigated further and this time, in your live site. I discovered that SiteGround’s caching is causing this. The builder is included in the dynamic cache.

To prove that the caching is the cause, I’ve purged the cache, disabled dynamic caching and opened in incognito mode. After that, Cornerstone worked.

I placed a period at the end of your headline so you could see that it works.

Given my first screenshot, please contact SiteGround to learn how to exclude the builder’s URL from the dynamic cache.

Thanks.

#30

Hey everyone. I’ve been reviewing some aging issues and I believe this should be resolved with the next version of the theme. The javascript error above was coming from an older version of Ember that we were using. I would recommend that anyone who experienced this problem enable “pre release” downloads from “Edit Account Info” on the dashboard page. This will let you try a beta version when it comes out (likely within the next few weeks). If the issue is still a problem we can take a closer look during the beta testing period. Thanks!