PHP Error caused by Wordfence

Hi @savethefrogs, thanks for your query.

It’s interesting to appear in this manner even when Wordfence is disabled, although the call_user_func_array() may well appear regardless if the problem is associated with permissions to run certain PHP functions.

Make sure that permissions on the /wp-content/plugins/ directory is 755 and that the owner on your WordPress root directory (and all contained directories) is www-data. Web servers such as Apache, Nginx, etc will require www-data to be an owner so that WordPress and plugins can update and run functions required to do so.

Further reading on file permissions: https://ww.wp.xz.cn/support/article/changing-file-permissions/

Let me know how you get on!

Thanks,

Peter.

Hi @savethefrogs, thanks for the clarification.

I can’t find, even in Elementor’s documentation, reference to a scheduled cron that might suggest automated creation of a Default Kit on a regular basis like this. You can firstly check if cron jobs are running on your site by checking Wordfence > Tools > Diagnostics > Cron Jobs, you will want to look out for the name of a job triggered around the time you’re seeing the Default Kit being created.

Are your Wordfence scans running and reporting that there are no issues found?

If the creation of the template still continues even when Wordfence is disabled, I may suggest contacting their support channels to see if there’s a known issue.

I would be happy to look over a diagnostic report if you could send one to wftest @ wordfence . com? You can find the link to do so at the top of the Wordfence Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

Note: For the fastest response time, please make sure and add any information or questions directly to this topic and not the email address above unless asked.

Thanks,

Peter.

Hi @savethefrogs, thanks for the additional information.

The notice you’re seeing is an error we suppress under certain circumstances, but custom error handlers can report suppressed errors anyway – which is what’s happening here.

We would only be particularly concerned by a fatal PHP error, as this error is being handled within Wordfence there’s no need to take action.

I’m pleased to hear you’re working with Elementor to deal with the original issue. Let me know if you need anything further at this stage. If not, by all means feel free to start a new topic any time you have Wordfence questions and we’ll be glad to help!

Thanks again,

Peter.