Hello again @bundfegadmin and @tigermediamao!
I’m really sorry that the previous suggestion didn’t resolve the issue for you, Chris.
On a positive note, we’ve worked on a fix that I’m confident will address the problem. This is a patched build of the latest 5.3.0 version.
If the plugin is currently disabled via WP CLI or naturally, without renaming it’s folder name:
1?? Download the patched build from this link:
2?? Upload and replace the current version with the patched build above.
3?? Reactivate the plugin—everything should work as expected.
If the plugin folder was renamed in order to disable the plugin:
1?? Upload the patched build as you would with a new plugin installation and activate it.
2?? Confirm the issue is now fixed by trying to access the /wp-admin page when our plugin is active.
3?? In case you are seeing two instances of our plugin now (reference example) here,, you might want to remove the duplicate WP Activity Log (the one which was previously disabled by renaming the folder)
That should resolve the issue, and nothing should be affected! Let me know how it goes, and I appreciate your patience and cooperation.