@ozfiddler - we've opened a case with the Wordpress Toolkit development team to get this resolved. You can follow along with that here for updates: WordPress Toolkit Incorrectly Detects ClassicPress as a WordPress Instance
Last edited:
Great. Thanks for the prompt response @cPRex . I also see there is this article now... WordPress Toolkit Incorrectly Detects ClassicPress as a WordPress Instance
WordPress Toolkit
WordPress Toolkit is a single management interface that enables you to easily install, configure, and manage WordPres...
docs.plesk.com
Just my two cents, whoever thought it was a smart idea to force WP Toolkit on the latest 92.* update, or worse if it was an oversight, needs to step into the real world of how we run our businesses. With 400+ websites under management and a staging server with hundreds of WP installs and projects in development, having to remove WP Toolkit and all of the associated files and folders in WP Uploads directories is still ongoing after a week.
Might just be us thinking this, but WP Toolkit have blown their chances of us ever using their software. Trust and partnerships are the cornerstone of business and they always will be - something WP Toolkit's team need to step into the real world and learn. It's simply unacceptable and arrogant to think you can force your software onto businesses who have run successfully and profitably without it.
Might just be us thinking this, but WP Toolkit have blown their chances of us ever using their software. Trust and partnerships are the cornerstone of business and they always will be - something WP Toolkit's team need to step into the real world and learn. It's simply unacceptable and arrogant to think you can force your software onto businesses who have run successfully and profitably without it.
We want to completely remove WPT from servers that have been upgraded. Is there an option within WHM to be able to completely remove WPT from the server? If so, where is it? Thank you
@Josh Cobb - thanks for that clarification. The wp-toolkit-scheduled-tasks service executes tasks from a ScheduledTasks table inside the WPT sqlite database.
@atlanticadigita - the best way to remove the software is to uninstall the RPM from the server.
@atlanticadigita - the best way to remove the software is to uninstall the RPM from the server.
I see wp-toolkit is now part of a yum mirror check. Run 'yum clean all', then 'yum update' and just under the kernelcare mirror check it lists:
Its just itching to re-install itself isn't it? !!
Code:
wp-toolkit-cpanel
wp-toolkit-cpanel/primary_db
wp-toolkit-thirdparties
wp-toolkit-thirdparties/primary_db
Duplika
Well-Known Member
Just found about the changes made to wp-config with this new plugin.
There is no way to uninstall WordPress Toolkit and undo the changes made at the wp-config.php?
Couldn't find anything at your documentation.
There is no way to uninstall WordPress Toolkit and undo the changes made at the wp-config.php?
Couldn't find anything at your documentation.
Duplika
Well-Known Member
So to remove it, at least not everything, we should run the following command and nothing else?
Code:
rpm -e wp-toolkit-cpanelIt's definitely not just you. Oakley have certainly changed the ethos of cPanel.
I just received the 92.0.6 WHM/cPanel update and WOW .... I now have WORDPRESS ....... how do I get this crap off my VPS server?
All it does is open up security vulnerabilities across ALL my user accounts and my main VPS server as well ...
Who decided to FORCE this crap on WHM/cPanel server owners??? .... they should be FIRED !!!
All it does is open up security vulnerabilities across ALL my user accounts and my main VPS server as well ...
Who decided to FORCE this crap on WHM/cPanel server owners??? .... they should be FIRED !!!
@Forrest Ward - your server did not get any Wordpress installations as part of the update. If your server had Wordpress Manager, which has been a cPanel tool for some time, or if you clicked the option to install Wordpress Toolkit during the Feature Showcase, your machine would get Wordpress Toolkit installed. It just gives you the option to install and manage all Wordpress installations more easily.
As mentioned earlier in this thread, you can remove the RPM if you don't want the tool on the machine at all.
As mentioned earlier in this thread, you can remove the RPM if you don't want the tool on the machine at all.
Here's an update applied in version 5.2.4 of WPT that I'm sure many of you will appreciate:
WordPress Toolkit no longer adds WP_AUTO_UPDATE_CORE constant to wp-config.php file right after scanning process adds a WordPress installation. This constant will be added only after site admin has explicitly modified WordPress autoupdate settings.
WordPress Toolkit no longer adds WP_AUTO_UPDATE_CORE constant to wp-config.php file right after scanning process adds a WordPress installation. This constant will be added only after site admin has explicitly modified WordPress autoupdate settings.