New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto upgrader issues #716
Comments
working on the upgrader when I wake up so should address the problems. On Thu, Jul 19, 2012 at 1:08 AM, Robbie MacKay <
Too brief? Here's why! http://emailcharter.org |
* Fix empty query error due to new line after last ; in sql script * Don't run ALL upgrade scripts, just the relevant one * Support both old and new settings table * Special case support for db version < 11
OK - this commit might get some of it: rjmackay@4ffad6d |
@kamaulynder you're on this already right? |
ok, could you push to the repo. that way we test it out. |
Pushed all my stuff on Monday. Assuming your testing and fixing the rest.. |
perfect, thanks. On Tue, Jul 24, 2012 at 10:50 AM, Robbie MacKay <
Too brief? Here's why! http://emailcharter.org |
ah ok.. might be only on develop branch.. cherry-pick 4ffad6d onto v2.5b if you need it |
* Fix empty query error due to new line after last ; in sql script * Don't run ALL upgrade scripts, just the relevant one * Support both old and new settings table * Special case support for db version < 11
cherry-picking done! |
Reopening this to cover further upgrader issues |
Previous updates haven't had this subdir in the zip file but the upgrader seems to think they should.
During upgrade we need to be able to bootstrap Ushahidi and hit the upgrade controller without any errors even though the DB is out of date. To do this we're checking for the 'key' field in the setting helper functions and running old/new queries as appropriate. Signed-off-by: Robbie Mackay <rm@robbiemackay.com>
This is to handle upgrading from 2.4 where settings in cache was an object
No need to copy the source zip file over
The gen_updates.sh script has now been updated to package files inside an ushahidi/ subdirectory. This means we can still work with older versions This reverts commit c82de39.
* Run SQL upgrades from docroot rather than than upgrade dir * Fix botched change to get_setting() * Bump up execution time for sql upgrades, just in case * Avoid infinite loop when version not returned * Revert to manually getting db_version from settings table
Prevent Kohana saving its caches on shutdown ushahidi#716
Upgrader repeat asking for update on commit d30c5b8 [V2.5b], have to fixed by manual set db_version to 96. |
Screenshot? |
@gcameron89777 Make sure you're using the auto-upgrader plugin and if the plugin ask for your ftp details, make sure you provide the correct |
Ah. Installed updater plugin and now updated. The confusion was that the On Fri, May 3, 2013 at 4:09 PM, Henry Addo notifications@github.com wrote:
best |
This is fixed, the auto-upgrader -> https://github.com/eyedol/Ushahidi-plugin-auto-upgrader plugin works. |
A couple of issues in the auto upgrader:
https://github.com/ushahidi/Ushahidi_Web/blob/v2.5b/application/controllers/admin/upgrade.php#L358
The text was updated successfully, but these errors were encountered: