Page 1 of 1

Why not to create config.php during new installation?

Posted: Tue Nov 17, 2009 3:07 pm
by Sonya
I do not know if the question has been already discussed. When installing CMS Made Simple an empty file called config.php should be created manually and placed in the installation directory.

Is there any reason for not creating the file automatically for new installations?
1. You can assure, that the file is created automatically only if no file config.php is found in the root, so that any production config.php will not be replaced accidentally.
2. If the file cannot be created due to the permissions on the server, then you can still give a warning on the installation check screen, so that it has to be created manually.

I think this will enrich usability for new installation a bit. For me I always forget to create the file before the installation. My FTP browser cannot create files, only folders. So I have to create a file on the local disk and upload it with FTP. I know that there is only half a minute, but I wonder why CMS Made Simple doesn't create the file itself if it cannot be found. :)

Re: Why not to create config.php during new installation?

Posted: Tue Nov 17, 2009 7:30 pm
by JeremyBASS
I second this...  detail makes diamonds bright

Re: Why not to create config.php during new installation?

Posted: Tue Jan 12, 2010 10:10 pm
by tyman00
While I can't answer your question, I do have to agree. Simple as it is to create one manually and upload it... it just seems more logical to automatically create it.

If you haven't please add it to the Feature Request tracker in the Force for the CMSMS Core.

Re: Why not to create config.php during new installation?

Posted: Tue Jan 12, 2010 10:54 pm
by Wishbone
I thought it was because it can take awhile to upload, you don't want others installing it until you were ready.. Nothing like going to lunch while uploading and coming back and someone installed it for you. :) That was my guess. I always forget too.