I’m only 3 months behind in deploying the update to WordPress 3.2.1!
JSON, the admin
A little bit tidier
Edge cases covered
Also switched to the TwentyEleven theme, removing both the header image and sidebar. Simple and clean.
Getting ready to change the homepage of my gaarf.info domain to the Modular Page I have been working on. In preparation, I have updated to the latest version of the blogging engine, and opted to ditch my old Hemingweb 2.0 theme in favor of the new default theme.
The theme used here, h2o, is becoming somewhat of a monstruosity. I really should write a completely new one. But for now, iterating already allows a little refresh, so behold a new hackishly re-tweaked theme!
Because of Twitter, I rarely post anything anymore… so I went from two-posts on the homepage to just one. The header was also changed, hiding the description so that focus is now completely on the latest tweet block and it’s awesomely mind-blowing font-size animation.
Let me know what you think in the comments!
WordPress‘ new admin interface is very nice.
The upgrade process was smooth as usual.
Growing tired of H20. I think I’m going to tweak a theme again. This time I’ll base it on YUI AutoGrid minimal and have support for widgets.
Then again, why mess with what works already ?
I moved to WordPress 2.6 in an attempt to fix my Twitter badge being so unreliable. Also I wanna play with the WordPress iPhone app. Here’s my upgrade worklog…
- found that my cache directory, used by MyTwitter’s SimplePie instance, had become owned by “nobody” and could no longer be deleted
- deactivated all plugins, most notably wp-cache
- uploaded virgin WP to a the web server
- moved previous wp-config.php,wp-content/uploads, google analytics secret file, favicon, and h2o theme to new WP directory
- renamed old and new directories so my docroot is now the 2.6 install, and the un-deletable folder is isolated
- ran wp-admin/upgrade.php
- downloaded and installed updated plugins
- MyTwitter was still behaving unreliably. Tinkered around and decided to remove the bundled SimplePie and instead use SimplePie Core
- … but that didn’t help. Still seems like the Twitter RSS feed being fetched – and cached – sometimes contain no items. Or just one item. I think the issue could be caused by a change in how Twitter responds to feed requests, and/or how SimplePie handles this.
- added some error handling to mytwitter.php, modified the plugin slug and renamed to folder to ignore update prompts
- even with wp-cache re-enabled (expires after 60sec), the new cache directory now remains under my ownership – MyTwitter issue (SimplePie cache expires after 900sec) probably not related to file rights.
Will have to keep poking at this until I find a solution. Then again, Twitter is known for failing, so maybe this is appropriate ?
UPDATE: I am now convinced the problem with MyTwitter comes from SimplePie. I de-activated SimplePie Core, wrote a custom parser/cache-manager with roughly the same interface (but using Twitter’s JSON feed instead of RSS), and tweaked MyTwitter accordingly. Let’s see if that does it…