theappwhisperer

I am in London, England, so if you’re in the US, do you know if ‘drop’ would mean ‘delete’ – it’s just a different way of saying the same thing?

oh gosh, isn’t it annoying? I’m a novice like you but I do know that the PHPAdmin that they referred to is your database. It’s possible to see the woo commerce files within that – I can see mine – but it says to ‘drop’ them – I have no idea if this means delete and the consequences for the website thereafter, so am too scared to press it.

I have ActNow Domains, for the DNS but why would this be related firstly to GoDaddy and secondly, to the Woocommerce plugins?

hi, it’s awful isn’t it? I’m sorry you’re dealing with this too, I wouldn’t wish it on anyone. Did you rename your woo commerce plugins? There are two main ones and then lots of sub directories, or did you rename all of the sub directories too?

I can get onto the database of the site and could ‘drop’ the woo commerce files – except I have no idea of the definition of ‘drop’ – if that means ‘delete’ and also what affect it will have on my site thereafter.

With regards the chap who commented about GoDaddy, I have no idea, I do not have a GoDaddy account so I don’t know, I’m sorry…

well my site has gone now, this plugin destroyed it, so that’s the end of that

nope because it’s nothing to do with it

yes it was, it was downloaded from the plugins section of WordPress

so, I did what you said above and it didn’t work at all
this is what your plugin does – I’d advise anyone to avoid using it

Fatal error: Uncaught Error: Class 'WC_Payment_Gateway' not found in /var/www/wp-content/mu-plugins/gd-system-plugin/plugins/mwc-core/src/WooCommerce/Payments/AbstractPaymentGateway.php:46 Stack trace: #0 /var/www/wp-content/mu-plugins/gd-system-plugin/plugins/mwc-core/vendor/composer/ClassLoader.php(478): include() #1 /var/www/wp-content/mu-plugins/gd-system-plugin/plugins/mwc-core/vendor/composer/ClassLoader.php(346): Composer\Autoload\includeFile('/var/www/wp-con...') #2 [internal function]: Composer\Autoload\ClassLoader->loadClass('GoDaddy\\WordPre...') #3 /var/www/wp-content/mu-plugins/gd-system-plugin/plugins/mwc-core/src/WooCommerce/Payments/GoDaddyPaymentsGateway.php(39): spl_autoload_call('GoDaddy\\WordPre...') #4 /var/www/wp-content/mu-plugins/gd-system-plugin/plugins/mwc-core/vendor/composer/ClassLoader.php(478): include('/var/www/wp-con...') #5 /var/www/wp-content/mu-plugins/gd-system-plugin/plugins/mwc-core/vendor/composer/ClassLoader.php(346): Composer\Autoload\includeFile('/var/www/wp-con...') #6 [internal function]: Composer\Autoload\ClassLoader->loadClass('GoDaddy\\WordPre...') #7 /var/www/wp-content/mu-plugins/gd-system-plugin/plugins/mwc-core/src/WooCommerce/Payments/CorePaymentGateways.php(153): spl_autoload_call('GoDaddy\\WordPre...') #8 /var/www/wp-content/mu-plugins/gd-system-plugin/plugins/mwc-core/src/WooCommerce/Payments/CorePaymentGateways.php(63): GoDaddy\WordPress\MWC\Core\WooCommerce\Payments\CorePaymentGateways::getPaymentGateways() #9 /var/www/wp-includes/class-wp-hook.php(292): GoDaddy\WordPress\MWC\Core\WooCommerce\Payments\CorePaymentGateways->loadHandlers('') #10 /var/www/wp-includes/class-wp-hook.php(316): WP_Hook->apply_filters(NULL, Array) #11 /var/www/wp-includes/plugin.php(484): WP_Hook->do_action(Array) #12 /var/www/wp-settings.php(560): do_action('init') #13 /var/www/wp-config.php(82): require_once('/var/www/wp-set...') #14 /var/www/wp-load.php(37): require_once('/var/www/wp-con...') #15 /var/www/wp-admin/admin.php(34): require_once('/var/www/wp-loa...') #16 /var/www/wp-admin/index.php(10): require_once('/var/www/wp-adm...') #17 {main} thrown in /var/www/wp-content/mu-plugins/gd-system-plugin/plugins/mwc-core/src/WooCommerce/Payments/AbstractPaymentGateway.php on line 46
There has been a critical error on this website. Please check your site admin email inbox for instructions.

Learn more about troubleshooting WordPress.

there are two main woo commerce plug ins – so I rename each one with one of these names?

No it went wrong before this and wrecked the site – so I tried rename the files to disable the plug in but it hasn’t disabled it and I still cannot access my site or dashboard

so the ‘Sharing Queue’ will not build a list and I cannot publish anything

I did all that you asked and that worked but when I went to view the ‘Sharing Queue’ I received this message – It seems there is an issue with your WordPress configuration and the core REST API functionality is not available. This is crucial as Revive Old Posts relies on this functionality in order to work.
The root cause might be either a security plugin which blocks this feature or some faulty server configuration which constrain this WordPress feature.
You can try to disable any of the security plugins that you use in order to see if the issue persists or ask the hosting company to further investigate.

I have changed nothing else

Yes I do! At least I’ll remember that next time – gosh what an ordeal – thank god it’s over and back up. Thank you for all your help. x

oh god, I’ve done it – I followed this post but followed the advice from the first chaps comments about renaming the plugin folder (as I couldn’t delete it) – then that deactivated all of my plugins and gave me access to my WP dashboard – I then went to the plug in folder and deleted that damned BBPress forum and reactivated all my other plugins – and then went back and renamed the plugin folder to what it was originally in the FTP – gosh I’m a computer whizz now! Really needed that stress on a Sunday night! Thank you all sooooooooo much for your help and patience. Joanne xxx

https://wpdude.com/case-study-disabling-plugin-dashboard-fubar

I’ve tried everything, I can’t see a simple delete button anywhere ;(