Pixel Pushing Monkey » uncategorized http://pixelpushingmonkey.com/blog random ramblings of a designer in the valley Thu, 05 Mar 2009 08:36:02 +0000 en hourly 1 http://wordpress.org/?v=3.0 This is not the new template I was referring to… http://pixelpushingmonkey.com/blog/2009/03/04/this-is-not-the-new-template-i-was-referring-to/ http://pixelpushingmonkey.com/blog/2009/03/04/this-is-not-the-new-template-i-was-referring-to/#comments Thu, 05 Mar 2009 01:30:36 +0000 steve http://pixelpushingmonkey.com/blog/?p=189 Continue reading →]]> 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

]]> http://pixelpushingmonkey.com/blog/2009/03/04/this-is-not-the-new-template-i-was-referring-to/feed/ 0 Only solution was to revert… http://pixelpushingmonkey.com/blog/2009/02/23/only-solution-was-to-revert/ http://pixelpushingmonkey.com/blog/2009/02/23/only-solution-was-to-revert/#comments Mon, 23 Feb 2009 18:11:56 +0000 steve http://pixelpushingmonkey.com/blog/?p=185 Continue reading →]]> 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…

]]> http://pixelpushingmonkey.com/blog/2009/02/23/only-solution-was-to-revert/feed/ 0