Wrapping strings in the plugin code with appropriate gettext functions would allow me to use it in my native language, so that for example ”Flattr this!” could become ”Flattroi tätä!” for my Finnish readers.

In templates/default/layout.html there are elements named ”loading” and ”close”. I don’t know if these names are dictated by Lightbox, but unless they are, I’d suggest renaming them with something more closely tied to their use by Simple Lightbox (such as ”slb_loading” and ”slb_close”, as other elements in the template are). The reason is that I just spent a significant amount of time trying to debug a weird problem with my theme, which was actually caused by ”loading” being an id used by Simple Lightbox and styled in its CSS. It was obviously easy for me to fix this by changing my element’s id, but finding out the cause was time I could have spent with more useful matters.

Thanks for the great plugin, though.

Wait, so post formats are different from post types, the defaults of which are always available? Oh so confusing.

I can reproduce the ”post formats” selection box not showing in both 3.1 and 3.2 RC 2. In fact I wasn’t aware of such feature, as it only shows when posting on the root site (which I very seldom do on my multisite).

I tried disabling all plugins with no effect.

1. Comes packaged inside a subdirectory called ”list-recent-sites.php”, which causes it not to show up under plugins after installing. Can be worked around by moving the files from within ”list-recent-sites.php” up in the directory tree (into list-recent-sites/).

2. Still doesn’t work after the aforementioned workaround and activating: the function displays nothing.

With Autolink URI 2.0.2, URI’s such as https://secure.wikimedia.org/wikipedia/commons/wiki/File:Snowshoeing.ogg are converted wrong: the colon cuts the link so that it points to https://secure.wikimedia.org/wikipedia/commons/wiki/File.

Adding colon into the regexp on line 59 of the plugin fixes this:

(?:\/[a-z0-9:%_|~.-]*)*

Could the developer integrate this fix into the plugin?

…and with 1.1.4 ”You do not have sufficient permissions” is back.

Hi Michael,

I just upgraded to version 0.9.20 of the plugin, and thereafter successfully connected my other blog with my Flattr account. So the issue is resolved for me. Thank you!

Upgraded to 1.0.1 an lo and behold, it now works.

With 1.0, the authorizing does redirect back to my blog, but the authorization hasn’t happened (the link still prompts to authorize). The ”You do not have sufficient permissions” problem also lingers, i.e. the settings cannot be saved.

Also, I seem to be talking to myself here.