2.7.7 breaks PGP syntax

[user5ab22cd517e418.1 (Karl Emil Nikka)]

With the release of 2.7.7, the way Gravity Forms handles five hyphens in a row changed. Text in text areas is now affected by wptexturize (or a similar function), transforming five hyphens into two dashes. This is an issue for fields dedicated for PGP keys, since it breaks the syntax.

Is there a filter to revert the behavior back to the 2.7.6 way of handling text?

[chrishajer (Chris (Gravity Forms))]

Hi Karl. I recommend opening a support ticket for this issue, since it’s the first I’ve heard of it:

https://www.gravityforms.com/open-support-ticket/technical/

Thank you.

[user5ab22cd517e418.1 (Karl Emil Nikka)]

@user5ab22cd517e418.1

With the release of 2.7.7, the way Gravity Forms handles five hyphens in a row changed. Text in text areas is now affected by wptexturize (or a similar function), transforming five hyphens into two dashes. This is an issue for fields dedicated for PGP keys, since it breaks the syntax.

Is there a filter to revert the behavior back to the 2.7.6 way of handling text?

Thanks. I’ve created a support ticket and provided both a video recording and access to a fresh WordPress install with only Gravity Forms running to demonstrate the issue.

[user5ab22cd517e418.1 (Karl Emil Nikka)]

Here’s a quick update of what we know so far.

• The bug only affects sites that were installed with an older version of Gravity Forms and updated to Gravity Forms 2.7.7.
• The bug only affects forms embedded through the Gutenberg block. Forms embedded through the shortcode are unaffeced.

I’ve provided Gravity Forms support department with another video along with two freshly installed WordPress sites (one running the bug-free 2.7.6 version and one running the bug-affected 2.7.9 version).