We are moving to Git Issues for bug tracking in future releases. During transition, content will be in both tools. If you'd like to file a new bug, please create an issue.

Bug 4849 - Upgrade via GUI
Upgrade via GUI
Status: NEW
Product: OJS
Classification: Unclassified
Component: User Interface
PC Mac OS X 10.3
: P5 enhancement
Assigned To: PKP Support
Depends on:
  Show dependency treegraph
Reported: 2009-10-29 12:33 PDT by James MacGregor
Modified: 2012-09-21 15:54 PDT (History)
2 users (show)

See Also:
Version Reported In:
Also Affects: OCS 2.3.4, OMP 1.0


Note You need to log in before you can comment on or make changes to this bug.
Description James MacGregor 2009-10-29 12:33:02 PDT
Allow upgrades to be done via GUI. This would hopefully alleviate the permissions-based issues we've been seeing, and make upgrading easier in general, where people don't have to ssh/CLI things. The GUI upgrade path should work somewhat like the following: 

1. On the Site Administrator's System Information page, the Site Admin has the option to check for updates. If there is an update, they should also have the option of a) downloading the new package for a manual upgrade; or b) upgrading automatically via the GUI. 

2. Clicking the Automatic Upgrade button will prompt the user to back up their entire system using the backup plugin (see Bug 4846). 

3. After backup has been completed (or skipped!?), the system should download the new files and extract them, or maybe patch is the way to go. I'm a little fuzzy here. 

4. After files have been updated, the DB should be updated. 

Users should see visual confirmation of which steps have been accomplished.

We should take a look at what's happening in Wordpress under the hood when they do this, as it's very quick and painless*. Here's the automatic upgrade plugin that I believe was the foundation for what is now core functionality: http://wordpress.org/extend/plugins/wordpress-automatic-upgrade/. 

* I say quick and painless: it's always worked perfectly for me, in under 2 seconds. I've seen threads online while looking for more WP upgrade info that suggests this isn't always the case. For that reason, I'd suggest considering creating this as a plugin available from the plugin gallery first, allowing users to install and test at their own risk before moving into CVS.