Posts Tagged ‘install’

Upgrading a blog to Wordpress 2.3 and changing your Ultimate Tag Warrior tags

Wednesday, December 5th, 2007

I upgraded the poetry knook today from WordPress 2.1.3 to 2.3. Including backing up the database and user files, the process took about an hour. Be sure to follow the upgrade steps (in order!). I have heard that logging into administration during an upgrade can cause problems.

WordPress 2.3, which was released back in September, includes among other things: a native tag system, plug-in and platform upgrade notification, post management interface improvements, roll your own dashboard, and roll your own RSS libraries. Many of these items have been addressed by plug-ins. Tagging especially comes to mind. I love Ultimate Tag Warrior and use it on all my blogs.

But I have to say goodbye to Ultimate Tag Warrior (well, not really, I hear there’s a UTW hack compatible with WordPress 2.3), because, as in all platforms, the best third party features eventually get implemented by the parent company. I recommending reading, How to Switch from Ultimate Tag Warrior to WordPress 2.3 Tagging, if you currently use Ultimate Tag Warrior and are upgrading to 2.3. I still had errors and installed UTW Theme Compatibility Thing but it did not work for me in listed related posts. For my related posts, I installed WordPress 2.3 Related Posts Plugin, since I couldn’t get UTW’s related posts tag to work.

As for mass editing and management of tags in WP 2.3, I am liking the features of Simple Tags. I have not used their tag clouds and related posts features however.

I think it took about as long to install WP 2.3 as it did to write this post, so check your plug-ins’ compatibility and then upgrade!

CUSTOM THEME NOTES:

Sounds easy doesn’t it? Well, not exactly if you use a customized blog and do not just download an upgrade ready-to-wear theme. You will need to change out all your UTW tags to WordPress tags (at the time of posting, this wiki is incomplete). Below are specific items I had issues with when upgrading:

  • Be sure to update your tags.php with the native WP tags instead of the UTW tags–although with the UTW Theme Compatibility Thing plug-in, you should be able get away with not changing these tags. There are no where near as many options with the native tags, so you may have to change the format of the tags in your blog.
  • I have had problems with the Dagon Design Sitemap Generator plug-in since the category database schema has changes. Update to the latest version to fix this.
  • Unlike UTW’s use of the tag.php for listing posts filed under a tag. The native tagging system of WordPress 2.3 uses the archive.php (just like viewing a category). Takes a glance at the code of /wp-content/themes/default/archive.php in order to customize your “Posts Tagged with ????” pages. It took me a while to figure this out in my customized themes.
  • I suggest creating a mod_rewrite entry in your .htaccess similar to “RewriteRule ^tag/(.+)$ http://www.example.com/archives/tag/$1/ [R=301,L]“, since tags will now be under the URL set for permalinks in the Options menu (e.g.- http://www.example.com/archives/tag/)
  • According to the Wp 2.3 ChangeLog, there are deprecated functions you will need to update in your template. Template tag permalink_link() has been deprecated in favor of the_permalink(); permalink_single_rss() has been deprecated in favor of the_permalink_rss().
  • I like to use variable font sizes (i.e.- ‘em’ instead of ‘pt’) for accessibility issues. The WordPress 2.3 tag, wp_tag_cloud, has problems with the unit, ‘em.’ Use ’smallest=1&largest=1.01&unit=em’ for the parameter to keep all the tags the same size.

Macromedia Dreamweaver 8 crashing on startup and close

Tuesday, October 30th, 2007

For a long time, I have had problems with Macromedia Dreamweaver 8 crashing at the close of the program. I had never had a problem with Macromedia Dreamweaver 8 crashing at startup until the other day. I surmise that Macromedia Dreamweaver 8 had closed and crashed as it usually did, but this time it wrote an invalid or corrupt Site Cache file. It took me a few hours to remove all parts of Macromedia Dreamweaver 8 from my system, but I finally found the corrupt site cache file in users/{username}/library/application support/macromedia/common/8/Sites/

Six plus hours uninstalling and re-installing Adobe Creative Suite 3 (OS-X)

Tuesday, October 30th, 2007

Adobe Illustrator CS3 crashed every time I tried to print to a CD on my Epson Stylus Photo R220. I decided to re-install Adobe Illustrator CS3. I did an uninstall with the uninstaller found in /Applications/Utilites/Adobe Installers. I then tried to re-install Adobe Illustrator CS3 with the installation DVD. Twenty minutes into the installation, it said
“Please insert Adobe ExtendScript Toolkit 2 to continue installation” I googled the error and found this Adobe support page, Message “Please insert Adobe ExtendScript Toolkit 2 to continue installation” when you install, reinstall or repair a CS3 Suite or CS3 application (Mac OS) I could not find a “Add or Remove Adobe ExtendScript Toolkit 2 alias” in /Applications/Utilites/Adobe Installers, so I decided to re-install the whole suite!

One of my co-workers warned that I needed to completely remove CS3 preferences, plists, and all those other files that OS-X applications install but never remove!!! I finally found this Adobe Support page, Remove CS3 prerelease software (Creative Suite and individual applications). I figured that it would remove release software, too. I believe that it does, but be sure you know what you doing when you use it. This script runs from the terminal, so it mainly a UNIX shell script that deletes folders and files.

I am now back to Illustrator 13.0.0 instead of 13.0.2, but only after more than six hours of uninstalling and re-installing Adobe Creative Suite !


Books Now Reading

My Sites