How does the update process work?
Permalink
Hi,
this one goes to very involved developers and originators of concrete5: I'd like to know exactly the process chain that happens when i push the update button in the dashboard. How does it differ from a manually update (backup db & files dir, copy new concrete dir, etc.). Could someone please tell me that?
this question comes upon the fact that I did an update and recieved errors (e.g. mail.php in helpers dir reports a path down into /updates/5.4.1.1/concrete...) so it seems that the cms would like to operate down into the updates dir? is that correct?
thanks in advance
Marv...still love C5 :)
this one goes to very involved developers and originators of concrete5: I'd like to know exactly the process chain that happens when i push the update button in the dashboard. How does it differ from a manually update (backup db & files dir, copy new concrete dir, etc.). Could someone please tell me that?
this question comes upon the fact that I did an update and recieved errors (e.g. mail.php in helpers dir reports a path down into /updates/5.4.1.1/concrete...) so it seems that the cms would like to operate down into the updates dir? is that correct?
thanks in advance
Marv...still love C5 :)
OK, got it! So it makes sense to me, that updating the concrete folder itself as usual when updating manually, would result in an error because files are "in use" by concrete5. so after an update trough the update-function concrete uses the concrete version out of the updates folder. But why does Franz from the developer team keep saying that references on files in that dir ist not correct?http://www.concrete5.org/community/forums/usage/trouble-upgrading-t...
Later from costa rica!!
Mike