Search results

It seemed to happen upon installing the update but I'm not certain. The other issues referred to above happen on saving the snippet.

I believe I have now patched up all the corrupted code on the live site.

It's also taking out all my escaping. So I write... $echo .= "<a href=\"?page=".($cur_page + 1)."\">></a> "; and it gets saved as $echo .= "<a href="?page=".($cur_page + 1)."">></a> ";

The problem seems to be that on saving, the plug in rewrites some code, turning ?> into > I have previously had problems with older versions of this plug in, for example I can't include code to search for the string "&nbsp;" because it gets turned into a space.

I have sent you a DM.

That file is not present with the older version of the plugin. When I update the plugin (breaking the site), that file appears.

I suspect it's one of the plug ins which process the custom post type data. I use almost identical plug ins which process RSS feeds on another site which was fine after the update. Here's the code... Sorry about the HTML. error_reporting(0); $args = array( 'post_type' =>...

So, should I just never update the plug in again?

Yes I rolled the plug in back to the previous version and the error went away.

The site didn't load at all. It just displayed a message reading "This site is experiencing technical difficulties." I believe that this is a new(-ish) feature of Wordpress so that crashes are handled more gracefully for the end user.

Hi there I am using PHP code in snippets to parse an RSS file and to pull data from custom post types and display it. The upgrade to 2.2.2 broke my site and I got the following email. Hi! Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error...