Repair Flattr-Button on mainpage

[Drake81]

No description provided.

[nonchip]

fixed by calling FlattrLoader.setup(); onload (make sure the async flattr script at the bottom of body is also loaded), because the auto mode only works for links defined in HTML and if the script is loaded sync in header, which both doesn't apply (we're loading it async at the bottom of body, just above piwik, AND most buttons are generated on run time by angular).

(section about removing <script async removed, because it doesn't apply here)

[nonchip]

i don't know for sure if pull request #67 will also fix the other buttons created by angular, we might have to call FlattrLoader.setup(); again after creating any new buttons (e.g. after rendering the podcast list)

[nonchip]

note: that sometimes fixes it (depending on the async load order), but at least now we know we have to handle button creation and call FlattrLoader.setup() dynamically

[luto]

document-readonly.html#L14

[nonchip]

ok, i'm pretty sure we could use this, except we have to make sure to use unique id attributes (or don't use them at all, there's document.currentScript, except for some IEs, do we support them?). looking into that

[luto]

currently we support newest chrome, firefox, opera (== chrome) and sometimes safari.

[luto]

unique ids aren't a problem, though, just use the document name as id (e.g. id="{{doc.name}}_flattr" or so).