Thanks for the report; I will copy the information you provided to our internal task tracker so I can give priority to this issue and investigate as soon as possible. I will update this ticket when I find the solution to the issue.
EDIT: Note that the “WP Visual Composer” is a premium plugin, there is not a public repository that I can use to check the source code of that extension so I will have to exclude it from the investigation; we can not guarantee compatibility with premium plugins, you will have to talk with the developer of that extension to investigate and fix the issue.
Thanks for the response.
You can try with free version of Visual Composer.
I desperately need a solution, can you fix that as soon as possible.
Regards
Anuj Sharma
Investigating an issue that affects twelve 3rd-party extensions will take several days if not weeks, I would have to read the code of every single plugin listed in your report, test the compatibility, find a way to replicate the issue, talk with the maintainer of those plugins to see if there is a way to fix the errors in their own codebase, and patch our code too (if necessary); I will work as fast as I can.
Thanks. You can test with few of them.
I did some debugging on it, i found out that if I am commenting do_action( ‘admin_init’ ); in wp-admin/admin.php line 168 then plugin is working fine, but this is wordpress file so we can’t comment code like this.
May be this can help you to get a solution.
Thanks
I see, that does not makes much sense to me, but if you say that deleting the admin_init action fixed the issue then I can add an option in the plugin’ settings to remove all the functions calls that are triggered when the admin_init action is started. Currently the Sucuri plugin executes three functions calls:
- SucuriScanInterface::create_datastore_folder
- SucuriScanInterface::handle_old_plugins
- SucuriScanHook::hook_undefined_actions
The first one is used to automatically create the directory where the plugin will store the security logs, if this directory is not created automatically then the plugin warns the user to do it manually.
The second one is used to delete two old versions of the Sucuri plugin that were deprecated back in July 2014, there is still people using old versions of the Sucuri plugin as you can see in this graph [1].
The third one is used to monitor non-standard actions that WordPress allows to execute from the dashboard but that are not tied to a valid hook, some of them include the installation, update, and deletion of plugins and themes among other things.
I will include the option to stop anything that the plugin does after the “admin_init” action is triggered following your suggestion as you discovered that deleting that code fixes the issue; however, I think that the bug is in one or more of the other plugins listed in your initial comment because many people uses “W3 Total Cache” and this is the first time someone reports incompatibilities between that and the Sucuri plugin, maybe is something in your server.
Anyway, I will write the code for that new option, wait for the release of the new version of the plugin, then I will mark this ticket as resolved.
[1] https://wordpress.org/plugins/sucuri-scanner/stats/
Option added via a PHP constant with commit 423916c [1]; once the pull-request #8 [2] is merged with the rest of the code we will release a new version of the plugin so you can have the fixes too in your website. However, if you want/need the changes sooner you can install the development archive from here [3].
Once the update is installed you can add a PHP constant in your configuration file named “SUCURISCAN_ADMIN_INIT” with a boolean value equal to “False” and the plugin will stop executing any admin_init related code. Thanks for your patience.
define('SUCURISCAN_ADMIN_INIT', false);
[1] https://github.com/cixtor/sucuri-wordpress-plugin/commit/423916c
[2] https://github.com/Sucuri/sucuri-wordpress-plugin/pull/8
[3] https://github.com/Sucuri/sucuri-wordpress-plugin/archive/master.zip
