Hello @jmeyer2485,
I trust you’re doing well!
I’m afraid the above lines are not showing what is the error on your site. It is showing a directory path to one of the plugin’s file. Not sure if this is related to the vales added inside a php.ini file.
Please enable WordPress debugging by putting the following to the wp-config.php file:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
Make sure that you insert these lines above /* That's all, stop editing! Happy blogging. */ in the wp-config.php file.
Visit your site’s dashboard to replicate the issue. This way all errors will be saved in the debug.log file inside the /wp-content/ directory. Share these warnings/notices with us.
These errors can be coming from a conflict with another plugin, please check if any of active plugins on your site is causing this
– Deactivate all plugins, leave only the Defender plugin active,
– If the warnings/notices are not showing up anymore, start activating one plugin at the time, till these will be back on a dashboard page.
This way you will find which plugin causing this.
Before running this test, please have a site backup, so if something will go wrong, you can always restore your site.
Please advise,
Cheers,
Nastia
@wpmudev-support9 I have done the error log already and it shows the same code that I have shared above.
I have also tried turning off the plugins with no success.
The only thing in the php.ini file is also shared above.
max_input_vars = 1600;
max_execution_time = 180;
My theme Avada requires these be set to what they are.
Hi @jmeyer2485
I hope you’re well today!
I’m sorry for “pushing” but could you please check the debug.log again? These lines (that you shared in your first post)
wp-content/plugins/defender-security/app/module/scan/behavior/core-result.php on line 30
wp-content/plugins/defender-security/app/module/scan/behavior/core-result.php on line 31
are definitely “cut off” at the beginning and there must be something more logged in the log – between the date at the beginning of the rror line and between the path (as shared above). That missing part is actually crucial.
As for PHP settings mentioned in your earlier post – they wouldn’t cause this. However, PHP itself might in some cases – what are the PHP and WordPress versions that you are currently using for your site?
Kind regards,
Adam
Hello @jmeyer2485,
I hope you are doing well!
We haven’t heard back from you for a while now so we’re going to mark this ticket as resolved, if you do have any followup questions or require further assistance feel free to reopen it and let us know here.
Kind regards,
Nastia
