This is the story of upgrading change.bbvx.org from WordPress 2.0.7 to 2.1.3.
- Replaced deprecated wp_get_linksbyname('Blogroll') with wp_list_bookmarks('category_name=Blogroll&categorize=0&title_li=0')
Miscellaneous plugin upgrades and additions
- Replaced c2c_get_recent_posts with post processing of data returned by query_posts
- Upgraded category access - check configuration
- Upgraded event calendar - check configuration
- Upgraded role manager - check configuration
- Upgraded search everything - redo configuration
- Added feedlist 2.2. Replace wp-includes/class-snoopy.php; Move feedlist.php to plugins directory
- Added Category Order 2.0.1
- Added MyLinkOrder 2.3; Note that old link order was not preserved over the upgrade
- Added Post Template 1.2.1 (weirdness with Server Error here. Not reproducible)
- Added InlineTagThing 1
- Added Advanced TinyMCE. Configured. Note requires install of plugins in wp-includes/js/tinymce/plugins. But this didn't work -- maybe WP 2.3, maybe something else -- and the author doesn't seem to have an interest in keeping it up to date.
- Deleted Advanced TinyMCE and added TinyMCE advanced -- explicitly supports WP 2.3. Newer version also supports a style picker -- which was the missing feature that caused me to use Advanced TinyMCE earlier.
Category Access/Theme problems
Support issue filed
See support issue.
If Category Access is the only plugin activated, and error_reporting(E_ALL) is set, then the following error message appears:
- Notice: Trying to get property of non-object in
- <server directory>/wp-content/plugins/category-access/category-access.php on line 325
Reported to plugin developer.
Attempts to resolve this by changing the theme
- Added function_exists wrapper for the event calendar, feedlist
How to install the upgrade
So now I've got a running version and I want to install it in the production server. There's a discussion of "moving wordpress" that seems roundabout to me. Here's what I did -- assuming shell access on a site like Dreamhost.
- Old Web files are in xxx.yyy.com, URL is http://xxx.yyy.com
- Old Database is db1 in db.mydb.com
- Test web files are test.yyy.com, URL is http://test.yyy.com
- mv xxx.yyy.com xxx.yyy.com.old
- mkdir xxx.yyy.com
- Create a "this site is down" index.html in xxx.yyy.com
- extract WordPress files into xxx.yyy.com
- Export the database from db1 to a SQL file
- Create db2
- Edit the SQL file to replace test.yyy.com with xxx.yyy.com
- Upload the modified SQL file to db2
- Edit wp-config.php to insert the authentication info for db2
Plugins, Themes, etc.
- Copy the wp-content/plugins and wp-content/themes/ directories from test.yyy.com to xxx.yyy.com
- Copy in .htaccess, if used
- Copy in other files (e.g. replacements for core files that are needed by plugins) from test.yyy.com to xxx.yyy.com
Longer term questions
- What criteria, aside from a resonance with the graphics design, should be applied when picking a theme?
- Compatibility with a WordPress version? [I don't care about the need to add code to show/edit tags. But tracking down deprecated calls can be a pain.]
- Good CSS standards -- sidebar after content, etc. But I'm not qualified to really list these.