generic Posted December 25, 2006 Share Posted December 25, 2006 dont overwrite your configuration.php file like i did when i upgraded my beta version, had to have my noc recover the file for me. just in case in the future, for example if I could not recover the file, can we just back up the database and reinstall it, then reup the database, or will that just mess everything up. 0 Quote Link to comment Share on other sites More sharing options...
WHMCS CEO Matt Posted December 25, 2006 WHMCS CEO Share Posted December 25, 2006 There'll only be a problem if you overwrite it, you store clients credit card information in your database and you don't have a copy of the cc encryption hash. Otherwise it's easy to just recreate the file should it be overwritten. Matt 0 Quote Link to comment Share on other sites More sharing options...
MACscr Posted December 26, 2006 Share Posted December 26, 2006 As already mentioned as well, you should have daily backup of all your files and databases and even another one when your doing upgrades. It even states this in the whmcs README. 0 Quote Link to comment Share on other sites More sharing options...
Sohan Posted December 26, 2006 Share Posted December 26, 2006 Happend to me, but I had a local copy on a seperate hard drive. 0 Quote Link to comment Share on other sites More sharing options...
Host4cheap Posted December 26, 2006 Share Posted December 26, 2006 Ya, happened to me aswell. I think the basic Package should come with configuration.php.new and when someone is trying to upgrade he wont have problems of configuration.php being overwritten and new Installation can show an ERROR to rename configuration.php.new to configuration.php, pretty much like all PHP scripts work 0 Quote Link to comment Share on other sites More sharing options...
mstorman Posted December 29, 2006 Share Posted December 29, 2006 Ya, happened to me aswell. I think the basic Package should come with configuration.php.new and when someone is trying to upgrade he wont have problems of configuration.php being overwritten and new Installation can show an ERROR to rename configuration.php.new to configuration.php, pretty much like all PHP scripts work Might be a simple minded thing, but it sounds great to me. Good suggestion. 0 Quote Link to comment Share on other sites More sharing options...
MACscr Posted December 29, 2006 Share Posted December 29, 2006 Ya, happened to me aswell. I think the basic Package should come with configuration.php.new and when someone is trying to upgrade he wont have problems of configuration.php being overwritten and new Installation can show an ERROR to rename configuration.php.new to configuration.php, pretty much like all PHP scripts work Might be a simple minded thing, but it sounds great to me. Good suggestion. I agree as well. But since the file has to be writable anyway, why not give the script the ability to automatically rename it if the original isnt there. Basically, have it be configuration.php.default. If configuration.php isnt there, it would rename configuration.php.default to configuration.php and write to it. Less work for the installer. =P 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.