Understood.@rivermobster - I did my testing and couldn't reproduce that on my end. I had a WordPress site and I manually selected the "Discourage search engines from indexing this site" option in WordPress, then clicked the refresh button in WPT (which causes it to re-scan the site) and that was displayed properly. The same thing happens with the "Search engine indexing" option.
Is it possible you just need to do the re-scan to let WPT pick up those changes? It doesn't grab that data in real-time, so that's likely where the confusion is.
lol...I'm kind of afraid to go down that road. If I do it once here, I can just picture someone going "but you tested a custom plugin for rivermobster!" Well, yeah, because I don't want to get thrown in a river!
I'm just going to give a more general "we don't test plugins" answer here :D
I agree - We should have had an option to install WPT with the update and not being forced on our servers - I hate this !!@custer thank you for your reply.
Full update, minor update, plugin update etc are all available options of course from within 'Softaculous' which thousands of us already have installed.
And please in future, do not alter or edit our clients files without our express permission! It doesn't look good when we have to explain to our clients that although we host their websites, some third party software called "cPanel" has edited them without asking us !!!
The script can process all sites on a server if you specify the directory that contains all your vhosts instead of specifying the directory of each vhost individually. Let us know if you still have issues with the script.There is nothing automatic about that tool. It requires you edit the command line to include the path to the wp-config.php file and then run it, one at a time, for each and every Wordpress installation on the server. Your installation script apparently found and edited every one of them without our intervention. Why are you making it so difficult to uninstall?
Will there be an easier way to uninstall in the future? Or at least opt not to have it installed in the first place?The script can process all sites on a server if you specify the directory that contains all your vhosts instead of specifying the directory of each vhost individually. Let us know if you still have issues with the script.
Wrong. I manage 9 WHM servers, and did not get asked about this during automatic updates. Most of which are in the "stable" branch until the next LTS is available, though this problem contradicts the meaning of stability. Having not known these plug-ins exist let alone what they are and do I've never opted in to WordPress Manager or WordPress Toolkit.@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.
While WordPress Toolkit does get automatically installed for users that had WordPress Manager, it doesn't take over any installations without you specifically telling it to. For example, if you have WordPress already installed, and then install WordPress Toolkit, it won't try and manage the installs unless you perform a scan for them.First of all, I reckon something that meddles with the existing Wordress installs on my servers in this fashion is akin to malware.
I agree - and at this point I believe that is how it behaves. While WPT may see your installation, it won't adjust any configuration files unless you have it manage the WordPress install.Number two - If you are going to so rudely interrupt the long standing open-source party over at Wordpress perhaps you would like to first make the installation options very, very clear in advance. And also while you're at it you should probably write a very comprehensive instruction manual.... something like the depth of the beautiful Wordpress codex site.
This point doesn't make sense to me since EasyApache is proprietary software and WordPress is distributed freely. WordPress doesn't run at a high enough level to make any adjustments to the EasyApache tools as those are handled by the root user. I do understand the point you're trying to make though, which is why we don't force users to use WPT. The reason we install the software at all is because we are trying to get users off the older WordPress Manager tool.Number three - How would your company and clients feel if Matt Mullenweg and all the good people over at Wordpress wrote a new update that decided it was OK to screw with the EasyApache cPanel files without asking?
Unfortunately experience shared in this thread shows that this is just not accurate.While WordPress Toolkit does get automatically installed for users that had WordPress Manager, it doesn't take over any installations without you specifically telling it to. For example, if you have WordPress already installed, and then install WordPress Toolkit, it won't try and manage the installs unless you perform a scan for them.