Thread Starter
tgchr
(@tgchr)
@alessio91 I’m still getting the same error messages with 2.0.5.2, though at least I can still log-in to deactivate it without restoring a backup.
Thread Starter
tgchr
(@tgchr)
@mtecuk Thanks, I just restored a backup from immediately before the 2.05 update, and was able to log-in and disable the plugin that way. Haven’t had time yet to test the latest updates.
