Scheduled posts generate a flattr Thing too early

Here’s the complete thing:

The plugin creates a thing at different stages of a posts lifecycle. If the plugins is configured successfully the following attempts are made.

1. A post switches state from draft -> published. This does not include scheduled -> published!

If a posts corresponding Flattr-Things does not exist, here is what happens:

2. If somebody clicks the flattr button from the rss feed, the plugins tries to look up if a thing exists for the post. If YES, it’ll redirect the user to the Thing page on flattr.com, if NO it’ll attempt to create the thing. If the Thing is created successfully it’ll then redirect to it. If all of the above failed, it redirects to the post itself on the blog.

3. If somebody clicks the bottom half of the javascript button below a blog post, the JS API will create a Thing on Flattr.com when the flattr click was successfull (user logged in at flattr.com, etc).

If the counter is ZERO and the Thing is not created for some reason, the upper half of the JS-Button is not clickable. You can’t flattr your own buttons so you can not trigger the JS-API to create a thing.

@andsten: If you schedule a post on a basic wordpress installation, there is no attempt to create a thing. There might be a chance that other installed plugins fiddle around with the posts’ state, resulting in the attempt to create the thing. If the Javascript-Button is triggered for some reason on a scheduled post, it’ll create a Thing as well as it can not know that the webpage it sit’s on is scheduled for a later release.
If you have bots sitting on your RSS feed that scrape its content and follow every link in it, it’ll trigger the flattr RSS button thus resulting the the attempt to create the thing.

@cooleisbaer: See 1 😉