Because I can take advantage of the plesk software updates that the server provider verifies rather than ad hoc plesk updates from a plesk vendor that ruins customer control panels for them ending up in the server move that's in progress. It's a simple thing, updating plesk based on whenever plesk releases updates would include phpmyadmin and php updates along with database updates. This way round, I can backup databases and should be able to restore databases just the same....well with less difficulty. As well as that, I get a better updated server and a faster one, depending on what's released. The previous server had CentOS 6 to which I updated to 6.7 (final) and plesk was on V12.0.0 to which had periodical updates but would not update to V12.5.30 and then some inherent configuration file issue from an earlier update which corrupted the web files base meaning that users couldn't see their sites from their locations (whereas I could all the time). Which leads me to the conclusion that the stock image from the server provider is the good and trusted one; any CentOS updates are also good and trusted but Plesk isn't which seems to be down to which repository it is picking up it's updates. So on that note, that requires research that I haven't the time for right now. But will later. It will be kept alive whilst I find out where to make the changes, then subsequently deleted (why have a CentOS 6.7 when there's a fully working CentOS 7.......lol)
