Peter Wooster

Thanks Cais, I thought you might know about it, but wasn’t sure as it’s a relatively new Yoast deprecation. I run with debug=true on all my test and QA systems and these messages break some other plugins like wp-migrate-db which produces corrupted backups when a message is written at the top of the admin.
/peter

The client updated his account and I updated the add-ons. The system is now working properly.

Thanks Mike,

I will let the client know, and get them to do the update.

I’m marking this topic resolved.

/peter

Please, just tell me what the current version numbers are. With that I can probably motivate this client.

The versions are
WP Job Manager: 1.23.4
WooCommerce Paid Listings: 2.4.0

As I said in my initial post, I’m quite aware this is not where I should post problem reports for add-ons. However it was late Friday afternoon, and the client won’t be available until Monday. And the WSOD is in WP Job Manager.

Is there a way I can find the current version of the add-on so I can get the client to update it?

This problem appears to be related to the use of custom CSS to restyle the form. Reverting to the standard Formidable CSS makes it work. The question remains, what would a Wp update break that. I’ll let you know when I find the answer.

I just posted this on your forum.

I did more than that. I tested it offline against WP 3.8 and 4.1.1, which both worked fine. WP 4.2 breaks FP. My test site has very few plugins, a simple theme an no caching.

I’ve reported it here as a heads up that there are issues with this. FP support has replied on their forum.

I using 2.0.0.3, I just ran a test on a development system using 2.0..0.3 and WP3.8 and 4.1.1. Those all worked.

This is fixed in version 5.4.2, now available.

Thanks to Yoast for the quick turnaround on this.

Thank you,

I just tried it and it is fixed.

Thank you,

I just tried it and it is fixed.

It’s a well known fact that you cannot parse HTML with a regular expression. You need a finite state machine to do it, since tags can stack recursively. That’s why there are XML/HTML parsers for most languages. I’ve turned the plugin off on the affected site since they never look at their GA stats anyway.

I am seeing damaged links to images with GA by Yoast 5.4.1 enabled. Disabling the plugin fixes the problem. Everything was fine before I upgraded the plugin. The tracking code is being inserted into the src= attribute.

I’ve posted a new topic on this with details

I have a client who was getting this 503 error after a recent WP upgrade, probably to 4.1.1 Upgrading PHP to 5.4 cleared up the error.