CiviCRM Community Forums (archive)

Hi

I used to be quite trigger happy when it came to nulling the config backend in civicrm, thinking it wasn't a problem.

But (correct me if i am wrong but) this field contains two types of info: server and domain info and  civicrm config info, like what countries are available, what components you are using, etc.

So you can potentially lose a lot of information when nulling that field.  Just wanted to

*check this was true before adding a health warning to:
http://wiki.civicrm.org/confluence/display/CRMDOC/Moving+an+Existing+Installation+to+a+New+Server+or+Location warning people of this.

*check that NULLing config_backend is actually a sensible thing to suggest.  Is civicrm/admin/setting/updateConfigBackend&reset=1 any gentler?

*suggest that (though you've probably thought of this) you could seperate out the server and domain and config if that is trivial and that would make it less dangerous.

ok - thanks - have made this more explicit in the documentation with a warning tag

Just to say big thanks for creating that upgrade script.  Not sure when you added it but in 3.1.3 I was asked if I wanted to run it and it worked like a dream!  No having to null config_backend makes a big difference when switching sql dumps between servers - saves the precious brain cells and helps me keep cool - must be the same for lots of others, so thank you

you'll come across it when you upgrade to 3.1.3 and move servers.  It's a URL so I am presuming yes...