Facebook
Twitter
RationalPolymer
Basic Pleskian
Plesk-12 Linux: removing a WordPress installation leaves behind a "<site>/httpdocs/wordpress" directory and two subdirectories ("wp-content" which is empty and "wp-includes" which is NOT empty). Something similar has been seen for installed Joomla applications.
1) this might lead to multiple instances of an Application being located in different directories, one which may be nothing more than the leftover "stub" as noted above, and another a full application installation - this can lead to site/domain backup/restore corruption as we have witnessed
2) users/customers/admins are allowed to choose any directory within a site/domain directory structure to install a given application (if they don't choose the "automated install option"), so leaving "application stub directories" can cause complications later on except, of course, where the installing person makes the same installation target each time (which might make things easier for Plesk, but is really not the best choice)
3) users/customers/admins may choose/need to relocated an installed application because the default/initially selected target location isn't what they really wanted/needed (I know - I have "been there - done that"), in which case the application installation remnants are a "bad idea"
4) if a user/customer/admin is selecting a Plesk Panel installed application for removal, then "by golly" ALL of the associated directories for that application installation SHOULD BE REMOVED - do not leave any application remnants!
1) this might lead to multiple instances of an Application being located in different directories, one which may be nothing more than the leftover "stub" as noted above, and another a full application installation - this can lead to site/domain backup/restore corruption as we have witnessed
2) users/customers/admins are allowed to choose any directory within a site/domain directory structure to install a given application (if they don't choose the "automated install option"), so leaving "application stub directories" can cause complications later on except, of course, where the installing person makes the same installation target each time (which might make things easier for Plesk, but is really not the best choice)
3) users/customers/admins may choose/need to relocated an installed application because the default/initially selected target location isn't what they really wanted/needed (I know - I have "been there - done that"), in which case the application installation remnants are a "bad idea"
4) if a user/customer/admin is selecting a Plesk Panel installed application for removal, then "by golly" ALL of the associated directories for that application installation SHOULD BE REMOVED - do not leave any application remnants!