rhertzog

Just to be clear, obviously the part “//domain.com” is completely wrong in the URL that he gets. It’s the hostname of the original URL and it shouldn’t end up in the relative URL.

Also the plugin doesn’t work when the URL of the link is different from the URL of the displayed image (quite a common case):

I get this for instance:
<a href="https://badminton-sorbiers.fr/files/2013/07/photo-bad.jpg"><img src="/files/2013/07/photo-bad-174x300.jpg" alt="photo bad" width="174" height="300" class="aligncenter size-medium wp-image-1064" /></a>

instead of the expected

<a href="/files/2013/07/photo-bad.jpg"><img src="/files/2013/07/photo-bad-174x300.jpg" alt="photo bad" width="174" height="300" class="aligncenter size-medium wp-image-1064" /></a>

So maybe you need to also take care of the replacing what you find in the href attribute…

I have the exact same problem… as he said, the initial URL submitted by the media browser starts with https:// because we’re using SSL to protect the administrative area (everything in /wp-admin/).

So you need to strip https:// in addition to https://

Replace str_replace("https://","",$imageurl); with preg_replace("/^https?:\/\//","",$imageurl);

In fact this is my use case for this plugin. I don’t want to hardcode https:// in URL because I want visitors to load the pictures with the same protocol that they used to load the page that they are visiting. My SSL certificate is self-signed and browsers won’t load pictures from self-signed https servers when they are visiting a non-https page.

Yeah, this is a much needed update that ought to be relatively easy. Except that you have to provide the new icon in several sizes for the various themes.

Tested it and it seems to work fine. Thanks!

I tested it here and it seems to work fine for me.

Michael, can you elaborate? simple-urls does not change anything for “normal” posts.

It adds a new custom “post type” however and those posts would be better ignored as they are only “redirections” and not real posts. Ideally the flattr plugin would have an option to select which custom post types must be registered on Flattr and which one must be ignored.

But I have not seen any bad interaction between both plugins.

In none of my cases, did I change the permalink. That said probably that drafts and scheduled posts do not have a definitive permalink yet… but those are not yet published and should not be sent to Flattr yet.

Well, no, it’s unrelated. See for example:
https://flattr.com/thing/171760/People-behind-Debian-Meike-Reichle
vs
https://flattr.com/thing/172437/People-behind-Debian-Meike-Reichle-member-of-Debian-Women

Compare this one, auto-generated:
https://flattr.com/thing/171896/Le-plan-secret-derriere-le-format-de-paquet-source-Debian-%5C3-0-quilt%5C

To this one, generated by users who clicked on the button:
https://flattr.com/thing/172064/Le-plan-secret-derriere-le-format-de-paquet-source-Debian-3-0-quilt

The auto-submit feature is useless currently as it doesn’t use the public permalink.

Furthermore it even submits an entry when I update a scheduled article that is not yet published (or when I schedule it for the first time). In that case it uses a temporary link “…/?p=XXXX” instead of the expected permalink.

And it submits stuff which are not regular posts. I have the simple-urls plugin and when I create a redirection link with that plugin, it’s also submitted to flattr.

All this is pretty annoying…

Thanks donncha. It works.

No, it doesn’t if your .htaccess is empty. I get this:

`Mod Rewrite Rules
Mod Rewrite rules cannot be updated!

You must have BEGIN and END markers in /usr/share/wordpress/.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:

# BEGIN WordPress
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
# END WordPress

Refresh this page when you have updated your .htaccess file.`

And there’s no button “View rewrite rules”.

I noticed the same problem. It’s really annoying in particular because I don’t understand why Flattr needs to change the default excerpt function.

You can easily deactivate this by removing those 2 lines in __construct():
remove_filter('get_the_excerpt', 'wp_trim_excerpt'); and add_filter('get_the_excerpt', array($this, 'filterGetExcerpt'), 1);

Same problem here with wordpress 3.0 with multisite enabled.