500 error after upgrade

I had assumed users would upgrade the WPSSO Pro Update Manager at the same time as they upgraded WPSSO — I’ll have to be more careful in the future about these kinds of version dependencies.

If you re-install the WPSSO Free version, then update to the Pro version, you should be fine now. ??

Thanks for letting me know about this issue. If you need additional support, please open a ticket on the Pro support website — the forums on www.remarpro.com are reserved to Free plugins versions only and don’t get the same response time as Pro support tickets (replies to forum posts can take several days).

js.

I would like to comment that I have the same issue and deleting the plugin did work. I would also like to report that my WordPress dashboard does not indicate that there is an update available for the UM (currently says 1.2.1), even though the link to the plugin site says 1.2.2 is available.

Furthermore, I noticed that my WPSSO plugin was updated last night, an update I did not initiate. I then looked at my Jetpack settings and noticed that autoupdates were enabled for WPSSO, but the UM can’t be autoupdated by Jetpack, and this is an absolute recipe for disaster. I would not be surprised if more people come up with this issue.

I did not see the upgrade notice about UM either.
I had tried to re-install WPSSO Free, but blog remains non-functional, generating 500-errors. The only solution I found was to delete both plugins —?WPSSO and UM, then install WPSSO and it required the UM installation — and it worked then. Though I am not fully getting the idea of having separate plugin that has to be upgraded in order to upgrade another plugin, but anyway the situation was very clear —?I saw a notice about new version of WPSSO only, clicked “Upgrade” and got my blog crashed.

This was definitely a backwards compatibility issue I should have anticipated — and certainly will in the future. The current code is back to using the old method name until I can find a graceful way to deprecate it in the future.

I didn’t know JetPack users could have autoupdate enabled for WPSSO. I’ll look at enabling autoupdate for WPSSO UM as well if autoupdate for WPSSO is enabled (so both can be enabled / disabled together).

The Update Manager used to be part of the Free WPSSO code base, but www.remarpro.com asked me to remove it. They do not want any code in Free plugins that can download / install code from other locations than www.remarpro.com. I could have kept the Update Manager bundled with the Pro version of WPSSO, but then to upgrade from the Free version would have meant installing the Pro version from a ZIP file. In the end, since the Update Manager has to be installed from a ZIP file anyway, it probably comes out to about the same thing. :p

js.