Only solution was to revert…

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…

Share this on your favorite social website:
  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • email
  • LinkedIn
  • Live
  • MySpace
  • Tumblr
  • TwitThis
This entry was posted in uncategorized and tagged , , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>