Support » Plugin: Better Click To Tweet » adding quotemarks automatically & some devices rendering wrong

  • Thanks for the great plugin! So far, very happy with it! I just have one thing to ask about and one thing to point out that’s still buggy.

    1. automatically add quotemarks around quotes

    I would like it so that quotemarks (curly quotes) automatically (so not having to add them manually in the shortcode) appear around the quotes when displaying them in the website, but also in the url to tweet. I can make the changes in CSS using :before and :after pseudo classes and setting the content as the quotes. However, these quote marks then don’t appear directly in the html and thus in the url to be tweeted

    It should look like this:
    https://twitter.com/intent/tweet?text=“text+to+tweet”&via=hander&related=hander&url=url

    But with css only appears like this (no quotes around text+to+tweet):
    https://twitter.com/intent/tweet?text=text+to+tweet&via=hander&related=hander&url=url

    I can obviously add the quotes when defining the $short variable directly in the plugin, but then of course those changes are lost with any update.

    Do you have any suggestions and/or hooks that can be used with your plugin to make these changes so that quotemarks don’t have to be added manually?

    2. I saw the other support tag being solved about quotes not rendering properly with certain devices. However, we are still seeing it happen occasionally. I think it’s probably with some strange device (so not android or iOS) as it doesn’t happen so often. If possible, it would be great to have it fixed as well. I’m sorry though I can’t be more specific with what devices for now, but I can try and get more information if need be.

    Examples:
    @ missing and + showing: https://twitter.com/lethalcupcake/status/702271787812286466
    @ missing on handler: https://twitter.com/pinkurlers/status/704923500738428928

    Thank you!

    Renee

    https://wordpress.org/plugins/better-click-to-tweet/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Ben Meredith

    (@benmeredithgmailcom)

    Hey Renee,

    Sorry for the delay here.

    Regarding question #1, let me do some testing with adding a filter to populate a field just before the $short variable. That would be the only way I could accommodate that request that doesn’t break the plugin for everyone else. Thanks for the impetus to figure that out. I’ll keep you posted.

    Regarding #2, I am unable to reproduce that bug, so unless you can figure a way to reproduce it predictably, I’m not going to be much help. Let me know if you can pinpoint the device having issues. With tens of thousands of sites that the plugin is running on, I’m surprised that more people aren’t reporting this issue.

    Thanks again for your patience with my slow support!

    Have a great day!

    Hi Ben,

    Thanks for the reply and my turn to apologize for the slow response!

    However, we were able to figure out a device that is still showing the + in-between the quotes. It is an obscure one, but apparently it’s still happening in Silk, the browser for Kindle Fire. This is the example: https://twitter.com/kissling93/status/726058548023566337

    Thanks for being so helpful with everything. It’s really great and kudos to you!

    Best Wishes,
    Renee

    Plugin Author Ben Meredith

    (@benmeredithgmailcom)

    I just tested on my son’s Kindle Fire, and the silk browser seems to have worked just fine. Perhaps it’s the Twitter client on the Kire?

    Here’s a screenshot of that

    I am running the Silk browser 49.3.1.2623.105.10 (holy version number, Batman!) On a Fire HD 6 (4th gen)

    Since I can’t replicate the issue, it’ll make it tough to fix.

    I’m still thinking through issue #1 above, but I haven’t made an update that doesn’t thoroughly break things. I’ll keep you posted there.

    Thanks again! I totally understand. I don’t have a Kindle that I can test myself, but it is possible they are using another twitter client. I’ll see if I can find out more, and I’ll try and do some more testing myself and see if I can get to the bottom of it. Thankfully (and also then harder to test), it only seems to happen in rare cases so all in all your plugin really does the trick!

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.