By Danny Malouin on Tuesday, 05 February 2019
Posted in Technical Issues
Replies 3
Likes 0
Views 873
Votes 0
Any thoughts on what STRING in the following post keeps crashing my post ?


<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body>
<div class="storycontent">
<p>WordPress 5.1 Beta 2 is now available!</p>
<p>This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version.</p>
<p>There are two ways to test the WordPress 5.1 beta: try the <a href="https://wordpress.org/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin (you’ll want to select the “bleeding edge nightlies” option), or you can <a href="https://wordpress.org/wordpress-5.1-beta2.zip">download the beta here</a> (zip).</p>
<p>WordPress 5.1 is slated for release on <a href="https://make.wordpress.org/core/5-1/">February 21</a>, and we need your help to get there!</p>
<p>Over <a href="https://core.trac.wordpress.org/query?status=closed&changetime=01%2F11%2F2019..&milestone=5.1&group=component&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&order=priority">110 tickets have been closed</a> since <a href="https://wordpress.org/news/2019/01/wordpress-5-1-beta-1/">beta 1</a>, many of which are documentation and testing suite improvements. Here are the major changes and bug fixes:</p><a href="https://core.trac.wordpress.org/query?status=closed&changetime=01%2F11%2F2019..01%2F22%2F2019&focuses=!~docs&keywords=~servehappy&milestone=5.1&group=component&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&order=priority">Several refinements and bug fixes</a> related to the Site Health project have been made.The pre_render_block and render_block_data filters have been introduced allowing plugins to override block attribute values (<a href="https://core.trac.wordpress.org/ticket/45451">#45451</a>, dev note coming soon).get_template_part() will now return a value indicating whether a template file was found and loaded (<a href="https://core.trac.wordpress.org/ticket/40969">#40969</a>).A notice will now be triggered when developers incorrectly register REST API endpoints (related <a href="https://make.wordpress.org/core/2019/01/11/new-rest-api-notice-in-5-1/">dev note</a>).Bulk editing posts will no longer unintentionally change a post’s post format (<a href="https://core.trac.wordpress.org/ticket/44914">#44914</a>)Twemoji has been updated to the latest version, 11.2.0 (<a href="https://core.trac.wordpress.org/ticket/45133">#45133</a>).A bug preventing the Custom Fields meta box from being enabled has been fixed (#<a href="https://core.trac.wordpress.org/ticket/46028">46028</a>).The treatment of orderby values for post__in, post_parent__in, and post_name__in has been standardized (<a href="https://core.trac.wordpress.org/ticket/38034">#38034</a>).When updating language packs, old language packs are now correctly deleted to avoid filling up disk space (<a href="https://core.trac.wordpress.org/ticket/45468">#45468</a>).
<h2>Developer Notes</h2>
<p>WordPress 5.1 has many changes aimed at polishing the developer experience. To keep you informed, we publish <a href="https://make.wordpress.org/core/tag/5-1+dev-notes/">developers notes</a> on the <a href="https://make.wordpress.org/core/">Make WordPress Core blog</a> throughout the release cycle. Subscribe to the Make WordPress Core blog for updates over the coming weeks, detailing other changes in 5.1 that you should be aware of.</p>
<h2>How to Help</h2>
<p>Do you speak a language other than English? <a href="https://translate.wordpress.org/projects/wp/dev">Help us translate WordPress into more than 100 languages!</a> The beta 2 release als marks the <a href="https://make.wordpress.org/polyglots/handbook/glossary/#soft-freeze">soft string freeze</a> point of the 5.1 release schedule.</p>
<p>If you think you’ve found a bug, you can post to the <a href="https://wordpress.org/support/forum/alphabeta">Alpha/Beta area</a> in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, <a href="https://make.wordpress.org/core/reports/">file one on WordPress Trac</a>, where you can also find <a href="https://core.trac.wordpress.org/tickets/major">a list of known bugs</a>.</p>
<p>Do you enjoy bugs?<br>
I don’t. So, we fixed them all.<br>
Well, not all. But close.</p>
</div>
<div>
<a href="https://wordpress.org/news/2019/01/wordpress-5-1-beta-2/" rel="noopener noreferrer" target="_blank">Original link</a>
</div>
<div>
Original author: Gary Pendergast
</div>
</body>
</html>
Hey Danny,

I am really sorry for the delay of this reply as it is actually a public day off for us here. Hm, what do you mean by crashing? Do you mean you hit Internal server error when trying to save this block of text?

If that is the case, very often the culprit would be mod_security that reports a false positive on certain text that is in the content. The only way is for you to remove them paragraph by paragraph to test them out.
·
Tuesday, 05 February 2019 22:26
·
0 Likes
·
0 Votes
·
0 Comments
·
You mean mod_security from the server's PHP settings ?
If so, OK
Thanks
Danny
·
Tuesday, 05 February 2019 22:37
·
0 Likes
·
0 Votes
·
0 Comments
·
Yes, that is correct Danny.
·
Wednesday, 06 February 2019 16:24
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post