Navigation
This is archived content. Visit our new forum.

Tagged: 

  • Author
    Posts
  • #860393

    chrishdunn
    Participant

    After 2 days slogging through the problems on my broken site, and being told it’s not related to the cornerstone update etc etc….

    I have found the problem….

    Add a text type element into cornerstone, and then put an ‘&’ into the text to be displayed using the effect. The ‘&’ causes the cs-body.min.js script to timeout and the page freezes.

    I have had an ‘&’ on the pages I’ve had problems with for months…was definitely OK before the cornerstone update.

    Have also noticed that sections with the column container switched on have had a 5px margin added since the update.

    I must be due some sort of reward!….very glad to have found it, but 2 days work!

    Regards, Chris.

    #860479

    Rue Nel
    Moderator

    Hello Chris,

    We are just glad that you have figured it out a way to correct the said issue.
    Thanks for letting us know!

    Best Regards.

    #860525

    chrishdunn
    Participant

    Are you going to fix it?

    #860648

    Paul R
    Moderator

    Hi Chris,

    We’ll forward this to our web development team for review.

    Please stay tuned for updates.

    Thanks

    #860924

    Alexander
    Keymaster

    Hi Chris,

    This is Alex, lead developer on Cornerstone. Our apologies for not being able to come to a resolution sooner. I start by giving you some information on what happened leading up to this.

    In 1.2.0 we introduced some changes to assist with using HTML characters inside fields that become shortcode attributes. Because a shortcode attribute is wrapped in quotes, the contents need to be encoded. We added encoding when the page is saved in Cornerstone, and the shortcodes now decode those attributes back into working HTML.

    We use a jQuery plugin called “Typed” to animate the text, and although their API claims to support HTML, it does seem to choke on the ampersand character. I’m sorry we didn’t catch this in our testing before the release.

    This has been fixed in the next release by re-encoding the “Strings” field, effectively reverting it to the way it was before without full HTML support. Thank you for letting us know your findings on the issue, when this topic was brought to my attention it helped to have an idea of where to look, as you narrowed it down quite specifically. We’re grateful for this, although we don’t offer any rewards.

    Keep an eye out for the next update with a bug fix.

    #860965

    Tech4Eleven
    Participant

    I can also confirm this behavior with “&” characters in the “typed” section. I had this same problem after updated x and cornerstone today and so glad i saw this thread. removing the “&” fixed the issue, just had to be quick about it before the page crashed. thanks.

    #861089

    Alexander
    Keymaster

    Glad to hear that worked for you as well.