LinkedIn posts are double url encoded

  • Petri

    (@petrir)


    9 years, 4 months ago

    I am still trying this plugin out. Everything else seems to work fine except for LinkedIn sharing. The post title converts spaces to %20 in LinkedIn and the post content converts spaces to plus signs, all other special characters are %-encoded.

    Another problem is that the LinkedIn post content doesn’t show the excerpt but the start of the WP post content. All the other share buttons contain the excerpt, so the excerpt should be OK.

    If I look at the sharing link the plugin creates I can see the spaces in the title encoded as %2520 so they are doubly url encoded for some reason.

    My plugin is version 4.2.7. Is it just me? What is messing this up?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter Petri

    (@petrir)

    9 years, 4 months ago

    ..cont’d..

    Here is an example post:
    https://metis.fi/en/2017/01/airtime-fairness-en/

    Most of the pages don’t have share buttons, but the top navigation leads to the posts where they appear.

    • This reply was modified 9 years, 4 months ago by Petri.
    Plugin Author Access Keys

    (@access-keys)

    9 years, 4 months ago

    Hello there,

    Thank you for your notification.

    We will check the issue in details and we will soon release and update of a plugin with fixes.

    Thanks

    Plugin Author Access Keys

    (@access-keys)

    9 years, 4 months ago

    Hello there,

    We have released an update of a plugin with this bug fix. Please update the plugin and let us know if this solved your issue or not 🙂

    Thanks

    Thread Starter Petri

    (@petrir)

    9 years, 4 months ago

    Thanks for prompt service!

    It is better. The double encoding is solved and the title is correct. However, some characters are still coming out wrong in the post content, for example ä appears as ä in the LinkedIn post. I’ve seen this happen when text is transmitted as text/utf-8 when it really is ASCII. The receiver assumes there is no need for character escapes so they are not converted.

    Here is a case example where there is an ä in both the title and start of content. The title comes out right while the content doesn’t. For some reason they are encoded differently:
    https://metis.fi/fi/2017/01/wpa2-fi/

    The other problem remains. The LinkedIn post text is from the WP post content, not the excerpt like the other services.

    • This reply was modified 9 years, 4 months ago by Petri.
    • This reply was modified 9 years, 4 months ago by Petri.
Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘LinkedIn posts are double url encoded’ is closed to new replies.