Urgent "New Cornerstone" display not working for translated pages, new update broken button styling and spacing

Support
#1

Hey guys,

I’ve just put in the new update for Pro (version 1.2) and it’s damaged some button and spacing styling.

Additionally I’m having difficulty with the “new page builder” viewing page which isn’t showing up on WPML manual translated pages and only about 50% of the time in the original pages. I can see this is a major update. At the moment I can’t edit the pages I could edit yesterday. Sometimes if I refresh 5 times the viewer will show up, but I’m having a lot of difficulty trying to edit the pages right now and make the corrections that the theme update has damaged.

I’m sure it will be great and it could be something to do with WPML plugin compatability, but now I’m stuck.

Is there a workaround for this? Or would it be better to roll back to the previous version of X until a future release. And if so, where can I access this?

Warm regards,

#2

Hey there,

Is this happening in your live site? If so, I recommend your roll back to the previous version and test on a staging server and give us access so we could investigate the issue without interrupting your live site.

Thanks.

#3

Hi Christian,

I’ve just updated to the latest maintenance update version 1.2.1, which appears to have resolved most issues and the page builder viewer is now working correctly. Thank you for your message and all the fantastic support from the Themeco team.

I’ll see how I go and come back to you if I come across any major issues.

Thanks again,

#4

Glad it’s working now. Are there any other issues that we need to check? We’ll be more happy to help. Thanks!

#5

Hey Rad,

Sorry false alarm. Page builder is not working in Pro (and also not working in X theme) I updated X theme and X Pro on to the latest versions as below:

Oct 6. UPDATE: Pro 1.2.3, and Cornerstone 2.1.3 are now available on automatic updates.

Oct 5. UPDATE: Pro 1.2.2, X 5.2.2 and Cornerstone 2.1.2 are now available on automatic updates.

Both Pro and X theme are having problems loading. Not getting past the loading circle. I’ve tried disabling all plugins, updating PHP to 7.2, removed any additional Javascript and increased WP memory limit. It appears none of these have made any difference and now the Page Builder won’t work at all. If it gets passed the preloader it gets stuck on the display screen. In either case loading is 5-10 minutes +.

Login credentials are still posted here. I would really appreciate if you could investigate further. I’ve exhausted all forum responses I could find so far.

Regards,

#6

Hi, there,

Could you confirm you’re still facing the issue?

I just logged and tried to launch some (up to 10) pages using the Edit with Pro button. The first and a random one accused error while loading, but both worked fine on a second attempt.

It seems you have some memory issues. You could check https://docs.woocommerce.com/document/increasing-the-wordpress-memory-limit/ about PHP memory seetings, but would be useful to check your Nginx error log and see if there are any PHP Fatal Errors.

If you find any errors, please copy and paste here so we can help to diagnose the problem.

Thanks!

#7

Hi Rafaelgou,

I honestly hope that other people aren’t having as much trouble with Pro as I am right now, because it seems like from all angles that 1.2+ is a causing so many issues and has damaged our ability to produce a high quality product for our clients. After your last message I spent an hour with host troubleshooting and all signs pointed back to Pro. Finally made the decision to give up on 1.2+ all together, and roll everything back to 1.1. Now when I go into page builder all the content from my pages is showing as “Element Missing”

Now this is also my fault/unlucky when my softaculous backup (which I made shortly after the update) was corrupt. And in trying to find a solution every forum post I read that are having similar problems you’re just putting it back onto the web developers. Yet with 1.1 it was running perfectly fine, now it seems that I can’t even roll it back to that time either.

Unfortunately for anyone reading these posts, they’ve probably already updated and if they’re in the same kind of situation as me, I’m incredulous as to how you could take a brilliant theme package and essentially destroy it by making it amateur. We started using X and PRO for it’s flexibility and ability to empower businesses to build and take control of their websites. And for now it seems like all that quality has disappeared through on page conflicts, slow or never-loading page loaders, strange spacing errors and styling changes, and no way to roll back to the previous stable version.

#8

#9

Hi there,

I checked and it’s working fine, could you try another browser? Or Chrome’s incognito.

Tried in both Windows 10 and Mac.

Thanks!

#10

Hey Rad,

Thanks for your response. I spent 3 days rolling it back to 1.1 manually uploading page templates I was lucky enough to have saved, so what you’re seeing there is Pro 1.1 and not 1.2.

I cloned copies of the site and removed all plugins and custom javascript and was still faced with a page builder that didn’t work. These are still live and you’re welcome to investigate further - please see secure note with login credentials.

At this stage i’ve given up on 1.2+ and hoping that a more stable release comes out in the future.

Please note that if you update to 1.2 and open the page builder and then roll back to 1.1 all content in the page builder is corrupted and lost. I’m not sure if this was just me, but it appears there is no way to roll back to 1.1 once started on 1.2 unless you have all templates saved for pages.

I’m a bit disappointed in the approach from Themeco with this update and wish there was more communication as to warn prior to updating of the significant effect it could have on full developed and developing websites. Especially given that rolling back appears to be a site killer if one was unlucky enough to not save all templates.

#11

Hi there,

The update could always ruin any existing setup even if the update is good and it varies from each site’s setup. It always happens on any software development stage, especially if there are structures that are changed. And I would love to see what’s causing that on your end.

And with any updates, we strongly recommend to test it first on a staging like you just did and thanks for cloning it. It’s a bad practice to directly apply updates or maintenance to a live site, it could go wrong. Now, we can continue the investigation, please provide the staging’s credentials in a secure note and we’ll check.

Thanks!