corebos_updater - fresh install - Printable Version +- CoreBOSBB (https://discussions.corebos.org) +-- Forum: Support (https://discussions.corebos.org/forum-17.html) +--- Forum: Administrator Support (https://discussions.corebos.org/forum-8.html) +--- Thread: corebos_updater - fresh install (/thread-1451.html) |
corebos_updater - fresh install - rslemer - 03-29-2019 I note even in fresh install system shows a error after corebos_updater If i apply all changes again, system solve this issue I think is a change for email templates RE: corebos_updater - fresh install - joebordes - 03-30-2019 sadly this is something we haven't been able to fix, it is due to the fact that the module install and creation of records is made in the same PHP call so there are cache issues. The changesets that try to insert records into the new module cannot find it, for the moment you have to launch the updates twice RE: corebos_updater - fresh install - rslemer - 03-30-2019 one possible solution is to create a temporary file, with the commands for the for the next execution the process terminates, and at the next start, it checks this file, if present it executes As in other processes, such as when you need to upgrade the Linux kernel, or the version update system itself It can not update itself, so it programs itself to update next time RE: corebos_updater - fresh install - joebordes - 03-30-2019 it is an option but we have better things to spend our time on and, really, pressing F5 or the "Refresh" button in the browser is just too easy RE: corebos_updater - fresh install - rslemer - 03-31-2019 But is a problem when system shows error messages, for real problems and problem solve with this easy solution We can ignoring really serious problems I think in this cases, better a warning message and a explanation to refresh de page, for example RE: corebos_updater - fresh install - joebordes - 04-03-2019 the correct thing to do is to fix it eliminating the cache issue, we are working on it RE: corebos_updater - fresh install - joebordes - 05-29-2019 I fixed this |