Thanks for the report, but you haven’t provided any information that might help… What is the URL to an example post / page / event showing the issue? Are there any errors in the debug.log after enabling the WP_DEBUG constant? See https://wpsso.com/docs/plugins/wpsso/installation/debugging-and-problem-solving/ for more info on WP_DEBUG etc. You can also activate the Query Monitor plugin, which can catch some common errors.
Thank you for your quick reply. Unfortunately, at the time, that was all the information I had. Let me address your points.
URL to an example post – I don’t have one right now. It’s on a live site and my client will blow a gasket if I knowingly break the calendar. I do have a screenshot with the Chrome Developer’s console showing an error. How can I get that to you?
Debug log – When I have time over the next few days, I’ll enable WP_DEBUG and see what the log says. I’ll get back to you on that. Again, it’ll probably be a few days, so please keep this thread open.
Query Monitor – One of my favorite utilities in my toolbox. Unfortunately, WP Engine where the site is hosted will not let me activate this plugin. Wherever you are, you probably heard me cussing last night when I found out about this.
Otherwise, WPSSO has been one of the few reliable plugins that I automatically update for my clients without even seeing if it breaks anything.
Thank you, JS.
Doesn’t WP Engine offer a staging site / service? You can define the WP_DEBUG constant in staging, update the plugin, then check the debug.log for errors. You can also submit the webpage to W3C to check for syntax errors, along with saving the HTML of the webpage before / after and diff’ing the two. 😉
It does. We’re currently using the Staging environment for a site refresh and makeover. I’ll install WPSSO there and let you know what happens.