Good morning gorrit,
Based on the nature of the updates in version 2.5 (i.e., none of them are database-related; you can see the diffs here and here), my hunch is that there might be something non-Clef-related that is causing the error.
Do you mean that immediately after you updated the Clef 2FA plugin from version 2.4 to 2.5, you received a database error message? If so, can you send an email to support@getclef.com with the following info:
1. What is the URL in question?
2. What is the error message you are seeing? (Include a screenshot if possible.)
3. Were you making any other changes at the same time such as updating WP core, plugins, or themes?
4. What is the hosting setup for this site? Are you on a shared hosting plan, VPS, etc.? Have you experienced any issues with maxing out server resources on this site under load (e.g., running out of RAM or CPU)?
Hi!
We’ve identified the issue here — it was caused by a change in interface on a dependency that could be shared with other plugins and affects users that have certain combinations of plugins installed.
We’ve pulled the 2.5.0 update from WordPress.org and are working on a fix, shipping Monday as v2.5.1. In the meantime, if you are affected, you should delete v2.5.0 of the plugin manually and install v2.4.1 from the plugin repository. If you have any issues, please email support@getclef.com and we will help you resolve them.
You can follow our progress on this issue at status.getclef.com, thank you for your patience and sorry for the issues.
Hi! We have a beta release of v2.5.1 that we’d appreciate you testing. If you have a moment, would you go here and download the wpclef.zip plugin, install it, and let us know if there are any issues?
Thank you for your help!
Cheers,
Jesse
Thread Starter
gorrit
(@gorrit)
I installed it on my testsite
Seems to be working fine. I will not do any testing on live websites, hope you understand 🙂
