Brade

Yep, I did notice that and that does solve the validation issue–now I just wish ul wasn’t even an option for the wrapper =]

I’m also hoping that nth-of-type will be an adequate sub for nth-child, but will have to play around with it more.

This markup is problematic to say the least. Don’t like to see it just casually accepted. It also causes problems with nth-child CSS rules, especially if you have an unpredictable number of posts pre-loaded at top.

Grrr, too hard to figure out right now! =(

Very bizarre… I did a case-insensitive search for “oauth” within my site, and there are no other plugins that directly call an OAuth function. I also verified that your code works correctly, and it is not mistakenly re-declaring the class in your module.

Somehow the existing OAuth module on my server is triggering the error (as can be seen from the file location in the Fatal Error). Since I can’t stack trace fatal errors, I have no idea what’s going on. I even tried disabling all other plugins. But I do know that only the “general settings” page triggers the error (“performance” and “feature manager” show up fine).

not working for me either–I am using the “developer mode” with the “echo background_image()” in the img tag. If I set it to normal mode, it works, but that’s not really the method i want to use.

having this problem as well. sadness reigns.

Update: I don’t think it’s cloudflare, as all of my domains are affected (not just the one I chose to use cloudflare with).

On the akismet config page, all the “Server Connectivity” boxes are green, but the above section “Akismet API Key” has the following message in a tan box:
“The key below was previously validated but a connection to akismet.com can not be established at this time. Please check your server configuration.”

So I’m kinda lost. It had worked for a really long time before just recently (and my site’s been on MT (dv) for over 6 months), but I do remember there being a wordpress update in the recent past. So maybe that messed it up somehow?

Just curious, would this be related to the new Cloudflare feature from MediaTemple? I started using this service on my DV account, and that’s really when I started to notice this Akismet problem. Cloudflare does take control of the DNS records for the domain and may be acting as a firewall preventing Akismet access. Just a thought…

Also recommended: not using a retarded plugin that generates smiley faces on your website.