Pixel Pushing Monkey » wordpress

This is not the new template I was referring to…

steve — Thu, 05 Mar 2009 01:30:36 +0000

Meanwhile I’m working on a completely new template for my blog, I made the decision to temporarily rever the blog’s template to something very simplistic. This will give me the flexibility to be able to add richer content without having to worry about the constraints of the previous blog template, and start looking forward to the eventual implementation of the new one.

I did run into one snag: Since WordPress’s own default theme is really formatted for a fixed width 800×600 screen, it doesn’t jive with my new design & content areas. I looked around and found this theme, which is a 1024 adaptation of the original WordPress template. You can download this template here:

WordPress Default Theme 1024 Wide

Thinking about a new blog template…

steve — Tue, 03 Mar 2009 22:28:10 +0000

I’ve been contemplatinng creating a new blog template… perhaps something that’s completely written from the ground up by yours truly. Can’t say when I’ll have it done, but at least by making the fact public, it might give me enough … Continue reading →

Only solution was to revert…

steve — Mon, 23 Feb 2009 18:11:56 +0000

I still can’t find what’s wrong with AJAXed WordPress. After a few back & forth on the author’s forum here, he offered a few things that I could look into, but nothing I did or could look into solved the problem. The only thing either of us can point to seems to be some weird error thrown by the newest version of WordPress:

Warning: htmlspecialchars_decode() expects parameter 1 to be string, NULL given in /home2

/pixelpu1/public_html/blog/wp-includes/compat.php on line 105

I can’t figure out what that means… there are nothing in the configuration that even points to that directory. Comparing the old “compat.php” in WP 2.7 and WP 2.7.1 revealed that the new compat.php file is incredibly huge compared to the old one, seemingly with a lot more error checking routine than before.

The only thing I can do for now, is revert back to WP 2.7. I’m also considering a new blog layout that will probably make AJAxed WordPress unnecessary anyway…. Things to ponder…

AJAXed WordPress still broken…

steve — Tue, 17 Feb 2009 19:48:50 +0000

AJAXed WP is still broken, but I’ve reactivated it in hopes that the author can come take a look and try to figure out what’s going on. I’ve tried several things, including:

Disabling all addons other than AJAXed WP.
Re-uploading all the files from WP 2.7.1.
Re-uploading AJAXed WP files manually.
Changing back to default theme.

Nothing’s worked so far… I’m gonna try a database repair or something next.

Update:

Performed some database maintenance routines… optimizing and removing overhead. It’s not having any effects.

AJAXed WordPress a little broken right now

steve — Wed, 11 Feb 2009 22:09:40 +0000

I upgraded to WP 2.7.1 today, and it broke some functionality in the “AJAXed WordPress” plugin. So if you click all the “click to continue reading…” links, they won’t work. I’m too lazy to deactivate the plugin right now, since it’ll make my “wall of text” look even more daunting than ever. You can still read the full blog post by clicking on the title.

Hope they fix it soon.

Update: Temporarily disabled the addon and inserted old school —more— tags on the more recent posts.