[ad_1]
*FIXED* with 4.5.1; only downside was that I had to get support involved because you cannot access the plugins config from the web due to the error. WordPress mentions you can disable via phpmyadmin or FTP which is not a quick thing for me. Good luck!
Funny thing is that 4.5.1 was in my plugin list (after autoupdating) but it was not activated so the error did not resolve until 4.5.0 was deactivated and 4.5.1 was reactivated
DEVS, TEST TEST TEST BEFORE RELEASE!
- This reply was modified 13 hours, 57 minutes ago by .
Hi @plcexchange
Glad to know that you have managed to resolve the issue, and thanks for the suggestion.
Have a nice day!