First load is okay. After reloading the page, I get a large chunk of HTML copied a second time. Notice that the highlighted section is what gets duplicated.
I think it’s somehow copying and pasting x characters from bottom. This makes very little sense, because no other website is having this issue in Chromium. Safari/Firefox loads this page just fine.
EDIT (2009/12/23): Looks like one of the newer build has fixed this. Hooray!
REMINDER TO SELF: Times are finally set to the correct Central Standard Time.
This is more of a summary post on what I’ve been doing with this WordPress installation.
I’ve finally taken some time with WordPress, and it seems like Ultimate Tag Warrior is no more. Luckily, WordPress has nice importers from people who used other tagging plugins in the past.
There are still a few bugs I have to work out with the code I changed when I did use UTW.
I noticed this a while back, but never really looked into it. After poking around the int3rw3bz0rz, it seems like there was an actual bug with the timestamps.
Sidenote: Blogging Bundle. Holy crap, get some nested comments… or a forum… or SOMETHING ELSE. This is seriously why I think blog comments are broken, but that’s another project idea for another day.
Regardless, this is what you want. From the MacroMates wiki:
Specifying Date Created
There has been a few problems related to correct dates. This comes from the fact that the dateCreated argument (in the XML-RPC protocol) has no time zone info, and until WordPress 2.2 it was interpreted mostly as server time.
Starting with WordPress 2.2 this field is GMT and dates should be offset correctly.
Unfortunately WordPress 2.2.1 introduced a Z in the date format which breaks Ruby 1.8.2’s XML-RPC parser — so if you use WordPress 2.2.1 then you need to update your installed Ruby version. If you have MacPorts installed then you can run sudo port install ruby and update your PATH. See RubyVersionIssues for help with that.
Even more unfortunately, the next version of WordPress will revert its date handling to before 2.2 and so, after that release, dates will again use the wrong offset.
Just need to be really careful and just set the timestamp in the “Date” field by adding the appropriate amount of offset. For this post, I would have to add 6 hours to the hour every time I update to make sure I’m not adding a 6 hour offset.
Updated. Feels good to be back in the blogging game.
While trying to find directions to a far, far away city (a friend of mine is going to Yale for Law… Nice, Stephen!) (oh… and it’s 14 hours, looks like I’m flying…), I find a very strange bug with Google Maps on Camino.
Looks like the links of the hovering bubble after you searched an address doesn’t work. In fact, if you click on them, they just disappear, as if you clicked on any of the white area within the bubble. It should be enlarging the bubble and adding a field for saved search or a drop down menu for My Maps. or Strange. Works on Firefox, though.
Maybe tonight after work I’ll look into it more.
And yes, there’s a reason for the “Crap” post. It’ll be up on here soon enough.
Update: Nevermind on that bug. I wasn’t able to replicate it at home. It was a strange bug though… I wonder if it was just because I was running an older Mac OS X.