• On attempting to delete the Jetpack plugin, I received this: “Deletion failed: There has been a critical error on this website.” Might someone suggest how to achieve this?

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • You can also remove the plugin via FTP. Log in via FTP and delete the plugin directory under wp-content/plugins/jetpack/. Of course, this is not a real uninstall. There would remain remnants of the plugin in the database.

    You could also check what the error is. The message displayed is very general. Details can be found in the error log of your hosting. Contact the support of your hoster if you need assistance.

    Alternatively to the latter tip you can also enable debugging in WordPress as described here: https://www.ads-software.com/documentation/article/debugging-in-wordpress/ – this way you would also get the specific cause of the problem displayed in the debug.log.

    If you see the specific cause and can’t handle it further, you can contact Jetpack support here: https://www.ads-software.com/support/plugin/jetpack/

    Thread Starter lotuspete

    (@lotuspete)

    Hello Threadi, thank you for putting your attention to this. I had seen the page “… debugging in WordPress as described here:?https://www.ads-software.com/documentation/article/debugging-in-wordpress/?–?” however, since I am not a real webmaster or developer, but just a person trying to run a small business, I was concerned that I might make some, big error. Here are the errors that the site seems to attribute to the Jetpack plug-in. Maybe you will find them interesting:

    Fatal error: Uncaught Error: Function name must be a string in /home/oldcarguy/public_html/wp-content/plugins/jetpack/vendor/composer/jetpack_autoload_filemap.php:1 Stack trace: #0 /home/oldcarguy/public_html/wp-content/plugins/vaultpress/vendor/jetpack-autoloader/class-manifest-reader.php(68): require() #1 /home/oldcarguy/public_html/wp-content/plugins/vaultpress/vendor/jetpack-autoloader/class-manifest-reader.php(51): Automattic\Jetpack\Autoloader\jp9559eef123208b7d1b9c15b978567267_vaultpress?2_2_4\Manifest_Reader->register_manifest(‘/home/oldcarguy…’, Array) #2 /home/oldcarguy/public_html/wp-content/plugins/vaultpress/vendor/jetpack-autoloader/class-autoloader-handler.php(112): Automattic\Jetpack\Autoloader\jp9559eef123208b7d1b9c15b978567267_vaultpress?2_2_4\Manifest_Reader->read_manifests(Array, ‘vendor/composer…’, Array) #3 /home/oldcarguy/public_html/wp-content/plugins/vaultpress/vendor/jetpack-autoloader/class-autoloader.php(80): Automattic\Jetpack\Autoloader\jp9559eef123208b7d1b9c15b978567267_vaultpress? in /home/oldcarguy/public_html/wp-content/plugins/jetpack/vendor/composer/jetpack_autoload_filemap.php on line 1

    Notice: Function is_embed was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /home/oldcarguy/public_html/wp-includes/functions.php on line 5865

    Notice: Function is_search was called?incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see?Debugging in WordPress?for more information. (This message was added in version 3.1.0.) in?/home/oldcarguy/public_html/wp-includes/functions.php?on line?5865

    The error is caused by the vaultpress plugin. If there is an update available, install it – it may solve the problem. Otherwise try to deactivate it. If you have questions about the error caused by this plugin, please contact their support forum: https://www.ads-software.com/plugins/vaultpress/ – if this does not work, you can also delete the plugin directory via FTP as described.

    • This reply was modified 1 year, 4 months ago by threadi.
Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Plugin won’t delete’ is closed to new replies.