VoxPelli

I can’t see that how the Flattr plugin would be setting any cookies in a WordPress blog? There is no mentioning of “cookie” in its entire code base and I also can’t see any reason for why there it would set any.

Can you elaborate on why you believe that it’s the Flattr plugin that is setting this cookie?

The multi-author feature works well for me when using dynamic buttons and not using the presubmit function, so it’s not completely broken at least.

@michael: Perhaps the presubmit feature submits things in a wrong way for multi-author blogs? Have you tried that out? I myself am not familiar with that piece of the plugin.

This is the feed that I have been looking at: https://www.wrint.de/feed/
Apparently not the same as the one Instacast uses which is https://feeds.feedburner.com/wrint/wrint ?

I can’t find any reason for this – there’s no code in the Flattr plugin that can do this that I can see. Maybe another plugin is doing something weird? But I can’t see why it would do that either.

Anyone having an idea of what might cause this?

For some weird reason the rel=payment links in your feed has double-encoded ampersands in it.

My own test-blog hasn’t got its ampersands double-encoded and I checked one of Tim Pritlove’s which should also be running one of the latest versions of the plugin and he hasn’t got that problem either.

I will see if I can find a reason for your double-encoding.

Just released 1.0.2 to fix this – thanks for reporting!

You’re not supposed to get a box for a Google URL – you just add the links yourself to the user description box using plain old HTML ?? The only thing the plugin does is removing some of the filters that would otherwise remove parts of the links.

Rather embarrassing bug :/ Fixed in 1.0.1 which is out now – thanks for pointing it out!

New release is out! Marking this as resolved for now – if you find something that isn’t then post a new topic or update this and mark it as not resolved (assuming that you can do that?)

@gerital: You should be able to use https://developers.flattr.net/api/resources/things/#check-if-a-thing-exists or https://developers.flattr.net/api/resources/things/#get-a-thing depending on whether you know the id of the flattr thing or not. We support both JSONP and CORS in our API so you should be able to easily do the requests in javascript if you like.

Just a note – this seems to be an inclusion made by the more-fields plugin, not the Flattr plugin, so we can’t fix it in the Flattr plugin.

Michael has included this fix in an official release so I’m marking this as resolved.

There will be a couple of fixes for this in the next version (0.99.4) – if you after that release still finds issues where it isn’t compatible with WP_DEBUG than please alert us to those specific issues since then we haven’t found them ourselves ??

__DIR__ was introduced in PHP 5.3.0 so if you’re running something older than that you will get this error. I haven’t tested the plugin myself in anything older than PHP 5.3, but I will fix this specific error in the next release and if we’re lucky than everything else in the plugin will already be working for older versions of PHP.

Thanks for reporting! I will fix this and it will be part of the next release.