Upgrading
From The Lyceum Wiki
- Make sure you were last logged in as admin. This avoids problems later when running upgrade.php.
- Restrict access to your Lyceum installation so that there are no changes to the database while it is being upgraded.
- Then, install the new code over the old code.
- Create a new wp-config.php file from the new wp-config-sample.php file, and reapply any changes.
- If you have installed Lyceum using flattened directories you will have changed /src/lyceum/private.php. Do not overwrite you changes, or if you do remember to re-apply your changes.
- Do any version-specific instructions listed below.
- Visit /wp-admin/upgrade.php while logged in as the Lyceum system admin.
- For enhanced security you may wish to delete src/lyceum/wp-admin/install.php.
- If you are using a language pack other than english remember to keep or re-upload the language pack in src/lib/wp-includes/languages
[edit]
Version-specific upgrade instructions
- 0.34→1.0.1
- The upgrade seems to take care of the DB schema, so nothing special needed.
- 0.33→0.34
- There were no changes to wp-config.php
- There were no changes in the DB schema, so /wp-admin/upgrade.php reports "Your database is already up to date".
- 0.31→0.32
- Make sure that none of the blogs in your system have the same slug, regardless of case differences. For example, myblog and MyBlog are the same slug. One of them must be changed, for example to myblog2.
- Run this query:
UPDATE options SET option_value='1' WHERE option_name='db_version'; - Note that WEBROOT in wp-config.php must now NOT have a trailing slash. If your WEBROOT was previously '/', it should now be .
