Facebook
Twitter
Chad Reitsma
New Pleskian
Hi guys,
It looks like you have coded the Wordpress toolkit to look for files in the installation directory and fail if any files are found - from an Admin level this is simply not good practice. We have several files in our skeleton directory that need to be present when a domain is created which are copied into the root folder. Then if we try to install Wordpress with the toolkit it fails because those files are present - but they have nothing to do with Wordpress.
I understand you are trying to help the user by making sure that they cannot install Wordpress overtop of an already existing installation - so why not search for the wp-content folder? Or some file that you know belongs to wordpress - and not just IF any file exists in this folder /fail ...
I hope this will be remedied in the future so we can use our skeleton directories properly
Cheers,
C.
It looks like you have coded the Wordpress toolkit to look for files in the installation directory and fail if any files are found - from an Admin level this is simply not good practice. We have several files in our skeleton directory that need to be present when a domain is created which are copied into the root folder. Then if we try to install Wordpress with the toolkit it fails because those files are present - but they have nothing to do with Wordpress.
I understand you are trying to help the user by making sure that they cannot install Wordpress overtop of an already existing installation - so why not search for the wp-content folder? Or some file that you know belongs to wordpress - and not just IF any file exists in this folder /fail ...
I hope this will be remedied in the future so we can use our skeleton directories properly
Cheers,
C.
