• Resolved Carlos GOMEZ

    (@cgomezg)


    Hello,
    I found an issue with Vimeo embeds and Complianz.

    • Environment: WordPress 6.8.2, Complianz GDPR/CCPA (latest free version), no other plugins.
    • Issue: When embedding a Vimeo video (using the Share → Embed code), Complianz correctly blocks the iframe but does not generate a valid preview image.
    • Result: In the frontend, the video is blocked but the placeholder has no preview image (empty background).
    • Expected: A placeholder image (thumbnail) should be generated like with YouTube videos.

    Steps to reproduce:

    1. Fresh install WP 6.8.2 + Complianz (free).
    2. Insert a Vimeo video iframe using native embed code.
    3. Enable Complianz and block third-party content.
    4. Observe: Placeholder is created but the preview image is broken (not readable).
    5. Compare with YouTube embed → works fine, preview image is shown.

    Additional info:

    • The placeholder file for Vimeo is created under /uploads/complianz/placeholders/, but it is not a valid .jpg. it is vimeo1039031790-1961333524-48909fc23a8f84db39a4fc1908b2e65a597dba2ccdb3c134c21b5b687284364d-d_295x166?region=us
    • In the frontend HTML, the data-placeholder-image attribute points to this broken placeholder file with the strange long name, so the preview image never loads.
    • Vimeo’s oEmbed API returns a valid thumbnail_url, so the issue seems related to how Complianz processes the URL (includes querystring, e.g. ?region=us).
    • I also checked debug.log with WP_DEBUG enabled, and no errors are reported when this issue happens.

    Can you please confirm if this is a known issue with Vimeo embeds?

    Thanks!

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Antonio Candela

    (@antoiub)

    Hello @cgomezg ,

    Thank you very much for the detailed report and for sharing the steps to reproduce the issue.

    You’re correct, there is currently a bug that prevents the placeholder from being created properly for Vimeo embeds. This is due to a change in Vimeo’s API that we were not aware of. We are already updating our code to adapt to this change, and the fix will be included in the next release of the plugin.

    Best regards,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hi @cgomezg ,

    We have fixed the issue and it will be rolled out in the next version of the plugin.

    Thank you for the report!

    Thread Starter Carlos GOMEZ

    (@cgomezg)

    Hi Antonio,

    Thank you for confirming that the issue has been fixed in your codebase.
    Could you please let us know in which version this fix will be released, and an approximate timeline for the update?
    We will test it again once the new version is available. For us the issue will be fully resolved only after verifying the fix in our environment.

    Thanks.

    Plugin Support Antonio Candela

    (@antoiub)

    Hello @cgomezg ,

    The new version will be released later this weekend and it will include the Vimeo fix.

    I hope this helps.

    Best regards,
    Antonio

Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.