Hi dear people at akeeba,
I have the one Wordpress website among a lot of Joomla websites where I have both Akeeba Backup and Admintools installed. After an update of Admintools I got this error when doing a php scan via cron:
********** ERROR! **********
Class 'FOF30\Container\Container' not found
Technical information:
Code: 0
File: /home/<dir>/domains/<dir>/public_html/wp-content/plugins/admintoolswp/app/model/scanner/email.php
Line: 77
I have looked up the Class etc on support on this site and find support tickets on Joomla on this, not on WP, but saw that a reinstall of Admintools could help: (export settings, deactivate admintools defend, deactivate plugin, delete plugin, install admintools, import settings). But it is not helping, I still get this error with a php cron scan. When I do a manual scan everything is fine, no errors about the Class, but maybe because no email has to be sent.
Could someone please put me in the right direction to solve this, and above all, how can I prevent this from happening the next update of AdminTools? I must be doing something wrong, but at this point I don't see what this could be.
Cheers,
Gahan Zwart
I have the one Wordpress website among a lot of Joomla websites where I have both Akeeba Backup and Admintools installed. After an update of Admintools I got this error when doing a php scan via cron:
********** ERROR! **********
Class 'FOF30\Container\Container' not found
Technical information:
Code: 0
File: /home/<dir>/domains/<dir>/public_html/wp-content/plugins/admintoolswp/app/model/scanner/email.php
Line: 77
I have looked up the Class etc on support on this site and find support tickets on Joomla on this, not on WP, but saw that a reinstall of Admintools could help: (export settings, deactivate admintools defend, deactivate plugin, delete plugin, install admintools, import settings). But it is not helping, I still get this error with a php cron scan. When I do a manual scan everything is fine, no errors about the Class, but maybe because no email has to be sent.
Could someone please put me in the right direction to solve this, and above all, how can I prevent this from happening the next update of AdminTools? I must be doing something wrong, but at this point I don't see what this could be.
Cheers,
Gahan Zwart