Hi @meetanik,
This error appears to be a bug in the vestige-core plugin, which we looked into last week for another customer experiencing the same error with class-vc-updating-manager.php.
Ideally the plugin author should be contacted to apply a fix, because their plugin is using WordPress hooks and causing an error when other plugins are using parts of WordPress. We are looking into preventing those kinds of errors from interrupting our scans, but we likely still won’t be able to check any plugins causing errors for updates.
Thanks,
Peter.
Thread Starter
Anik
(@meetanik)
Hi Peter,
I am not using any vestige core plugin. The above file is related to wpbakery page builder.
Do you need to see what’s inside that file?
Thanks
Thread Starter
Anik
(@meetanik)
One question, if some plugins can accidentally block worfence from scanning site, the malwares can easily do such things to stop worfence to remove it, isnt it?
Hi all,
I have the same issue and I don’t have any vestige-core plugin installed. Has anyone got to a solution already?
-
This reply was modified 2 years, 9 months ago by
seclo.
Wordfence 7.10.4 is now released with a notable fix in this case:
- Improvement: Detect when a plugin or theme with a custom update handler is broken and blocking update version checks
