Mte90/Share-Backported

Share to Diaspora* inserts "+" instead of spaces in titles

wazoox opened this issue · 19 comments

This is a behaviour introduced with version 2.0.x. Version 1.3.0 works fine.

Example sharing this page to Diaspora* initializes the windows with the following text:

### New+Issue+·+Mte90/Share-Backported

https://github.com/Mte90/Share-Backported/issues/new

What's expected instead (what happened with version 1.30):

### New Issue · Mte90/Share-Backported

https://github.com/Mte90/Share-Backported/issues/new

Confirmed across several users. Downgrading to 1.3.0 fixes the problem.

Mte90 commented

We have a specific code for diaspora but seems that is not executed https://github.com/Mte90/Share-Backported/blob/master/modal/modal.js#L243 I will work on that.

Thanks for the quick fix friends :)

Mte90 commented

:-D

Today's update broke Diaspora sharing again :/

Mte90 commented

It is this line that create issues, should be on top https://github.com/Mte90/Share-Backported/blob/master/modal/modal.js#L268

Mte90 commented

Fixed in the last release

Hm, + would be a space in encodeURIComponent

@Mte90 Let me know, if you need a hand here :-)

Mte90 commented

On my tests the url is ok: https://share.diasporafoundation.org/?url=https%3A%2F%2Fdaniele.tech%2Fita%2F&title=Home+-+Daniele+Mte90+Scasciafratte
The encode anyway is happening at the top before do the fixes for the various shares.

Mte90 commented

I don't have an account on diaspora to see what is happening

Here's a screenshot (running the current version):
http://imgur.com/Ap6JoX4l.png

Mte90 commented

So seems that diaspora doesn't like + and want them encoded anyway.
It is something that i can do, I will do some tests

Mte90 commented

No I found a wrong variable used in diaspora -.-'

I hereby confirm 2 .0.7 works fine :) Thanks @Mte90 👍

Hello @Mte90, version 2.1.0 upgrade today just reintroduced this bug!

Mte90 commented

Very strange the code is there https://github.com/Mte90/Share-Backported/blob/master/modal/modal.js#L319

I am opening back the ticket to study the situation.

Mte90 commented

There is a new release with a fix, in my tests should be fixed now.