Hello @sngm
Thank you for using our plugin.
I am sorry to read about your issue. This usually happens when you try to upgrade to version 4.4 from a build that is older than version 4.3.6.
Therefore can you please do the following:
1) Download version 4.3.6
2) Upgrade the current install to version 4.3.6
3) Once that is complete, then upgrade to 4.4.0
Can you please keep us posted about this issue? Thanks.
Thread Starter
sngm
(@sngm)
Hello Robert,
sorry for my late response here. I am back at work since today.
First of all, thank you for your feedback and yes I had version 4.3.4 installed. I did the update with the zip you shared with me, today. This works. After updated to 4.4.1 (with the backend update process) I got the following error:
Fatal error: Class WSAL_Adapters_MySQL_ActiveRecord contains 5 abstract methods and must therefore be declared abstract or implement the remaining methods (WSAL_Adapters_ActiveRecordInterface::IsInstalled, WSAL_Adapters_ActiveRecordInterface::LoadMulti, WSAL_Adapters_ActiveRecordInterface::LoadAndCallForEach, ...) in /kunden/317706_37073/webseiten/wp-hosting/wp-content/plugins/wp-security-audit-log/classes/Adapters/MySQL/ActiveRecordAdapter.php on line 25
You wrote I should update to 4.4.0 but I update directly to 4.4.1. Could this be the problem?
Greetings
Magnus
Hello Magnus,
Thank you for the update. Can you please confirm if this was a one-off error and the plugin is still working?
We’ve only managed to reproduce this once in one specific test environment and it was caused by some old PHP files, and in our case it was reported only once (during the update process) yet everything worked as it should.
Let me now.
Thread Starter
sngm
(@sngm)
Hello Robert.
Ok I think at least that this is a one-time error. The error from yesterday also refers to another class and is not the same as at the beginning. The error from the beginning did not come again yesterday.
After the update the system and also the plugin runs correctly.
I would currently say that the actual request here is fixed. So I just wait for the next update and see if any new errors are reported. If so, then I create a new ticket. This is probably the best thing I can do right now, right?
I am glad to hear that the errors where a one-off and everything is “sorted” now.
Indeed, the best thing to do is to keep an eye on the log files and wait for the next update. The next update will be way smoother since there are no database table schema changes.
Should you have any more questions, please do not hesitate to ask. I am marking this thread as solved for now.
Have a great dat and thank you for using our plugin.
