[AlexanderKeymaster]

Hi everyone,

Update (January 11, 2015 – 12:09pm): We are planning for a Cornerstone release within the next week. It will be addressing the jetpack issues, and featuring refined drag and drop interactions. Repositioning elements will be far more accurate, and contain inline previews.

Update (December 11, 2015 – 5:05pm): If you are using Jetpack and having issues loading Cornerstone, we’ve identified conflicts with the “Sharing” and “Publicize” modules. Disabling these modules has been confirmed to restore editing ability. We’re still investigating the cause of this. It is likely that you will continue to see threads related to these updates for a little while. Our support team is continuing to followup with existing topics to ensure satisfactory solutions are provided, and we’re seeing new threads come in from those who have not yet been made aware of the information provided below. We’re also encountering isolated issues related to customizations that are now conflicting with Cornerstone, and compatibility issues with other 3rd party plugins that are being looked into individually (not global Cornerstone issues, rather specific to individual installs, customizations, or certain 3rd party solutions).

---

Update (December 10, 2015 – 3:55pm): Version 1.0.11 is now available via automatic updates.

At this time, I’d like to thank everyone who has been affected by these issues for your patience and understanding thus far. What we faced in these past updates was a myriad of compounding issues related to Cornerstone framework updates, WordPress core changes, and conflicts with updates in 3rd party plugins. It was somewhat of a perfect storm, but we’re coming out the other side.

If you’re still having issues, please keep these things in mind:

• Update to the latest version (1.0.11)
• Clear the cache of any performance plugins
• Disable script minification, at least as a troubleshooting measure. Sometimes plugins like Autoptimize will cache your scripts, and although you are updated, the scripts are stale.
• Watch for unclosed HTML tags, and special characters in your Raw Content elements

If you’re interested in reading more in-depth about some of the technical issues we’ve seen, feel free to read on. Otherwise, again we thank you for patience, and offer our best wishes to you!

Beginning with 1.0.7, Cornerstone has undergone a much needed framework rewrite. This was needed to support some of the new features that have been requested, and to provide an API extensive enough for new rich, complex, and tailored elements. Our framework changes introduced bugs that we didn’t catch in our testing due to server environment differences, and creative ways we didn’t anticipate people using Cornerstone. By expanding a beta group, we hope to stay out in front of these types of issues.

Additionally, we faced some issues where older versions of Cornerstone were incorrectly serving “Raw Content”. It was being pre-proccessed (wpautop) by WordPress in ways that corrupts certain custom code. This pre-processing was also removing harmful javascript errors. By correcting this, any sites with HTML or script errors immediately began to cause problems on the front end, and with Cornerstone loading. We now have safeguards in place to protect sites containing errors from becoming unusable. You should also be able to edit existing pages that were affected.

Finally, there were challenges faced with breaking changes WordPress introduced in the shortcode API. We rely heavily on shortcodes in Cornerstone, and we’ve had to workaround a few different bugs in WordPress core.

It is our desire that X and Cornerstone be reliable and enjoyable products, and we don’t take these issues lightly. While we can not control third party changes that can and will have an effect on any piece of software, we hope that some upcoming countermeasures will be effective to mitigate and eliminate these events moving forward. At the same time we can not stress enough the very unique nature of this particular update given the upcoming changes after the first of the year. Everyone should be very excited at the bright future ahead with Cornerstone the the ecosystem around it. We sure are!

---

Update (December 9, 2015 – 3:30pm): A new version of Cornerstone will be available tomorrow with the following updates:

• Prevention of unclosed HTML tags breaking the live preview
• Notification when unclosed HTML tags are detected
• Fixed icon selection control
• Fix missing ID attributes on elements
• Fix incompatibilities with WordPress 4.2 and older

We may also have an exciting new feature in X ready – not sure just as it’s still being worked on so if it’s not quite ready it will definitely be in the next X update. In next X update.

---

Update (December 4, 2015 – 6:30pm): Cornerstone 1.0.10 is now available via automatic updates, and will be included in the version of X downloadable on ThemeForest.

---

Update (December 4, 2015 – 4:30pm): Cornerstone 1.0.10 Release candidate is being tested. We’re updating affected installs to isolate the issues with Cornerstone loading, and improperly displaying some HTML. We plan to do another release this evening.

---

Update (December 1, 2015 – 3:30pm): Cornerstone 1.0.9 is live.You should see it under automatic updates if you click “Check Again”.

This is a quick status update on the recent issues with this past Cornerstone update. Having rewritten the majority of the backend, we’ve had a handful of issues slip through that we’re working to resolve quickly.

If you’re experiencing PHP errors or issues with column widths, please update to the latest version.

The following is a list of the primary concerns to be imminently addressed in the 1.0.9 release.

• [cs_undefined] appearing in content.
• Page builder stuck on preloader due to permalink conflicts.
• Menu item duplication. (Identified as conflicts with WPML and Polylang)
• <br> tags not working in some element text fields.
• Some elements like embedded video can’t be previewed with “no container”
• Missing margin or padding on sections and rows

If you’ve experience any issues where the front end is not identical to what is previewed in the page builder, try re-saving that page.

If you’re having issues with the page builder not loading, going to Settings > Permalinks in your dashboard and clicking “save” has been known to get this working again. This should no longer be required.

We’ll follow up here with any more updates and information as things progress.

[Author]

Posts