Hello Michacy,
Thank you for showing interest in our plugin.
What you’re reporting is very odd behaviour, especially when you consider that we haven’t done any changes to the database component in the last few versions.
Also, if WordPress is able to connect to the database when WP Security Audit Log plugin is installed, technically speaking all other plugins should be able to connect as well, since at the end of the day they all use the same database connector.
Though we are more than happy to help you troubleshoot this. But it might be easier to get some logs from the Migrate DB Plugin? Or contact the developer of that plugin and get more information on why it is failing to connect to the database?
Looking forward to hearing from you.
I have run into the same problem with the free version of WP Migrate DB. It seems to break when trying to run queries in the process_chunk() function inside wpmdb.php. The specific query that my install seems to have problems with is SET sql_mode='NO_AUTO_VALUE_ON_ZERO';, however there are no WP errors thrown and I don’t see anything relevant in the apache logs.
WordPress 4.4.2
WP Migrate DB v0.7.2
WP Security Audit Log v2.3.3
Hello Marc,
I will contact the developer of WP Migrate DB myself and will get back to you as soon as I have any updates.
I forgot to mention that the original error message I received from the plugin was “A problem occurred when attempting to connect to the local server, please check the details and try again. (#112)”, when I look at the console I see simply “error”, and the network activity that is timing out is an ajax call to ‘ajax_initiate_migration’.
Hello MarcGuay,
We got in touch with WP Migrate DB and can confirm that the issue is from our end. We will be looking into this and should be releasing a fix in the upcoming release.
Thank you very much for reporting this. Should you need to use WP Migrate DB before we issue a fix you can run it in compatibility mode.
Should you have any further queries do not hesitate to get in touch.
Good stuff, thanks a bunch.
Hello all,
This issue has been resolved in version 2.4 of WP Security Audit Log, which we just announced. Thank you for your support and please do not forget to rate the plugin.
