Pixel Pushing Monkey

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 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.

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.