Cookie for X cannot be removed

  • Resolved kexikus

    (@kexikus)


    1 year, 5 months ago

    Hi,

    I’m currently testing this plugin for a website I’m working on and I noticed an issue with the blocking of content from X (Twitter). Actually two issues, but I’ll start with the more relevant one.

    Once consent has been given to always load content from X (which works), this consent cannot be removed. I noticed that in two ways. First of all, when using the [embed_privacy_opt_out] shortcode, it would not show the checkmark for X even after I had given consent. Furthermore, when using the same shortcode with the show_all=1 option, there is a checkmark for X, but it does nothing. Enabling or disabling this checkmark does not influence whether content from X is loaded or not and clicking the checkmark to always allow content from X directly on an embed also does not result in the checkmark being set in the opt-out form. I tested other embeds like Youtube where this works perfectly. I would very much appreciate a fix for this issue since X is among the main embeds we have on our site.

    As for the more minor issue: The text on the blocked X embed still refers to twitter.com instead of X.com. It would be nice if this could be fixed as well.

    Thanks!

Viewing 15 replies - 1 through 15 (of 17 total)
1 2
  • Plugin Author Matthias Kittsteiner

    (@kittmedia)

    1 year, 5 months ago

    Hi @kexikus,

    thank you for noting these two issues. I could reproduce them and will look for a short-term fix.

    Thread Starter kexikus

    (@kexikus)

    1 year, 5 months ago

    Hi @kittmedia

    Thank you for the quick reply. We look forward to a fix. I should add that the second issue with the text was in the German translation of the plugin.

    Plugin Author Matthias Kittsteiner

    (@kittmedia)

    1 year, 5 months ago

    Can you share the content of your provider configuration for X in Settings > Embed Privacy > Manage embeds > X, please?

    Thread Starter kexikus

    (@kexikus)

    1 year, 5 months ago

    Of course:

    But the blocked embed looks like this (using the Gutenberg Twitter Embed block):

    • This reply was modified 1 year, 5 months ago by kexikus.
    Plugin Author Matthias Kittsteiner

    (@kittmedia)

    1 year, 5 months ago

    Can you try add a / at the beginning of the ”Regex-Muster“? This should probably solve it.

    Thread Starter kexikus

    (@kexikus)

    1 year, 5 months ago

    Unfortunately that changed nothing. The regex is now “/^(www.)?(twitter|x).com/”

    Plugin Author Matthias Kittsteiner

    (@kittmedia)

    1 year, 5 months ago

    That’s incorrect. Now the escaping around the dots are missing. The regex must be: /^(www\.)?(twitter|x)\.com/

    Thread Starter kexikus

    (@kexikus)

    1 year, 5 months ago

    Sorry, that got screwed up when pasting it here. The regex is correct in my backend but it still does not work unfortunately.

    Plugin Author Matthias Kittsteiner

    (@kittmedia)

    1 year, 5 months ago

    Can you please share the post content of a post where the embed is not replaced properly with the logo of X?

    Thread Starter kexikus

    (@kexikus)

    1 year, 5 months ago

    It was simply a Twitter embed block with this URL: https://twitter.com/starwars/status/1866664200464167368

    But now that I checked again, the block can no longer embed that URL anyway, so I’ll have to check what’s going on there first.

    Edit: It only shows up as an error in the post editor. The embed is correctly shown in the post itself.

    But I also tried Xs own embed feature copied to an “Individual HTML” block like this one

    <blockquote class="twitter-tweet"><p lang="en" dir="ltr">Episode 3 of <a href="https://twitter.com/hashtag/SkeletonCrew?src=hash&amp;ref_src=twsrc%5Etfw">#SkeletonCrew</a> is now streaming, only on <a href="https://twitter.com/DisneyPlus?ref_src=twsrc%5Etfw">@DisneyPlus</a>. <a href="https://t.co/mcZgBlN2fB">pic.twitter.com/mcZgBlN2fB</a></p>&mdash; Star Wars (@starwars) <a href="https://twitter.com/starwars/status/1866664200464167368?ref_src=twsrc%5Etfw">December 11, 2024</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>

    Again, the embed itself works but it does not respect the cookie setting at all.

    • This reply was modified 1 year, 5 months ago by kexikus.
    Plugin Author Matthias Kittsteiner

    (@kittmedia)

    1 year, 5 months ago

    I could now reproduce the issue and will provide a fix. The problem is a change in the regular expression of Twitter/X, which results in this embed provider not being recognized properly.

    Thread Starter kexikus

    (@kexikus)

    1 year, 4 months ago

    Thanks. We look forward to the fix.

    Plugin Author Matthias Kittsteiner

    (@kittmedia)

    1 year, 4 months ago

    The bugfix is part of the most recent version 1.10.9, now.

    Thread Starter kexikus

    (@kexikus)

    1 year, 4 months ago

    I can confirm that it’s now working as intended.

    A follow-up question though. This might be out of scope for the plugin but would it be possible to also block Twitter embeds that use the Twitter embed code (in a html block) instead of the WordPress embed block? So, something like this one:

    <blockquote class="twitter-tweet"><p lang="en" dir="ltr">Episode 3 of <a href="https://twitter.com/hashtag/SkeletonCrew?src=hash&amp;ref_src=twsrc%5Etfw">#SkeletonCrew</a> is now streaming, only on <a href="https://twitter.com/DisneyPlus?ref_src=twsrc%5Etfw">@DisneyPlus</a>. <a href="https://t.co/mcZgBlN2fB">pic.twitter.com/mcZgBlN2fB</a></p>&mdash; Star Wars (@starwars) <a href="https://twitter.com/starwars/status/1866664200464167368?ref_src=twsrc%5Etfw">December 11, 2024</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
    Plugin Author Matthias Kittsteiner

    (@kittmedia)

    1 year, 4 months ago

    This would be indeed possible. However, I can’t see any benefit in doing so when it’s not necessary, because WordPress already handles Twitter embeds by just using the link.

Viewing 15 replies - 1 through 15 (of 17 total)
1 2

The topic ‘Cookie for X cannot be removed’ is closed to new replies.