frasten

Thank you for your idea. I’ve added this feature in 2.6.0, in a similar way.

It’s currently not possible.
I hope to find the time to implement this sooner or later.

Hi, the switch from ID to class was introduced to allow multiple widgets at the same time (you can’t have multiple equal IDs on the same page).
However, looking at the source of your page, I think that using #trending-posts as ID, it should work the same.

Thank you for reporting, I’ve just fixed this in the trunk, you’ll see it in the next version.

Sure, it will be fixed in the next version of the plugin. Thank you for reporting!

Thank you, I think that there was something wrong at wordpress.com’s side (my plugin doesn’t do anything with https).
Thank you for reporting!

Thank you for reporting. I’d replace echo "</div>" with echo $after_widget;.
Can you test if this works for you, so I can commit the fix?
Thank you!

I got an answer from the developers at wordpress.com:

Any glitches are a result of what we’re doing on our end and we are working to resolve them.

I am now in contact with them, and I’ll try to give them all the feedback they need to fix this issue.

Well, let me explain a couple of things. WordPress.com Popular Posts isn’t incompatible with WP 3.1, or Jetpack, or WP Stats, or whatever.
Simply WordPress.com has currently some issues in its own API interface.
And nobody but WP.com can fix this.
EDIT: And open source is NOT this. I cannot look at the source of their API interface (I would probably have already sent a patch to fix this issue), and this is a huge limitation.

I’ve already contacted WP.com, and I’m waiting for an answer.

You could try to disable/re-enable WP Stats (and reinsert your API key), just in case.

Hi, I’m the developer of WordPress.com Popular Posts.
As you can see, everyone has had issues in the last few days.
Well, sadly it’s not my plugin’s fault, because wordpress.com API system is now returning completely wrong data.
Installing Jetpack incredibly fixes for some users (for me too).
But this could only be a coincidence, because I think they’re gradually fixing these issues to every user.
I’ve read above about some new XMLRPC call, but there’s currently nothing about that in the Stats module of Jetpack.
So, everyone should try to update to Jetpack, and increase the magic number to at least 2 in my plugin’s setting.
This asks for more records from the wordpress.com API, and currently is necessary, due to some wrong or empty records (I don’t know what the hell they’re doing with their database!!!).

Fixed in 2.0.7! ?? Thank you for reporting!

You’re right, I’ve read that article. Thank you for your kind answer.

Again, why should be .htaccess set to 644? And wp-content 777?
I think that .htaccess should be set to 444 and wp-content to 755, to provide a more secure setup.