Forums | Mahara Community
Support
/
Problems upgrading to v1.2.3
29 March 2010, 18:36
Greetings all. I'm having some problems upgrading my test instance to v1.2.3 and am looking for some guidance.
Gorey Details:
- Upgrading from v1.1.6 straight to v1.2.3 (more about this later), downloaded from mahara.org
- Running underLinux and mySQL. Don't have the version numbers at my fingertips, but can look them up if necessary.
- I'm running the upgrade in a test environment, on a copy of my live data
Upgrade process itself seems to go fine and upgraded Test Mahara site is running but there are bits missing.
- Both my testing accounts are missing several views
- In one case, the URLs for a couple of the missing views now point at a user profiles
- I notice that profile images/avatars are also missing
- No errors in php.log (just a number of messages about the upgrade "Migrating group...", "Resync of filetype list", etc)
- Nothing in the httpd error logs
- On the "Performing upgrades..." browser page, Mahara reports that its updating core from version 1.0.9 (not 1.1.6) to 1.2.3. Is this significant?
An experienced Admin in my office suggested that maybe I should be upgrading with the interim steps: v1.1.6 to v1.1.7 to v1.2.0 etc.I attempted an upgrade to v1.1.7 and it failed badly*. So I attempted a v1.1.6 to v1.2.0 upgrade which gave me the same results (missing views) as the attempted v1.2.3. upgrade.(I refreshed the database and data directory from production each time.)
*v1.1.7 upgrade: On the "Performing Upgrades" page, the twirly never got past the "core" line and there were error messages in the httpdserror_log of the form "File does not exist: /opt/httpd/htdocs/tmaharatheme, referer: https://tcranberry.kwantlen.ca/tmahara/admin/upgrade.php"
I've run out of ideas and would appreciate input.
Donna Hrynkiw
Kwantlen Polytechnic
29 March 2010, 21:11
Hi Donna,
I can answer a couple of your questions:
There's no need to do incremental upgrades; as long as you're starting from 1.0.0 or higher, you should be able to go straight to 1.2.3 in one step. However, doing the upgrades incrementally (and testing after each one) might be useful for finding out which upgrade is the one that destroys your data.
R.