Viewing 20 posts - 1 through 20 (of 20 total)
  • Author
  • #960675

    Hi, thanks a lot for pushing out the GDPR Update right on time!

    I couldn’t update our website yet, but I read the changelog to 4.4 and I feel it contains pretty much everything that was needed for compliance. One thing however I am missing. That is the option to use the no cookie url’s for YouTube videos as background videos, e.g. in sections.

    is that possible now or will that option be added in time? I have seen various threads here in the support forum discussing the matter.

    Thanks a lot and keep up the fantastic work on Enfold!


    Hey L+T,

    We didnt knew about that ( honestly I didnt either ).
    We will do let our developers know, if they can work something.

    Best regards,


    Thanks Basilis, I hope they find a quick solution. I consider this to be important for the GDPR complaince. Thx!



    Our solution for now is that you will have to write on your Privacy page, that you are using Youtube and you are loading videos from there.

    Best regards,


    So you now basically state that Enfold is NOT GDPR-compliant! Are you aware of this? Unless YouTube embeds are not supposed to be a part of Enfold elements anymore of course.

    All you need to do is to allow no cookie domains from YouTube in the various elements where you can add videos by link, like background sections or the video element. You really tell us to rely on a half baked idea by mentioning YouTube videos in the privacy policy only, which clearly isn’t compliant?

    Can the Kriesi team please reconsider asap? Thanks and have a good weekend everyone.


    Hi again, I second TF_Photogrüahy’s statement! With all due respect that answer is more than unsatisfying!

    I kindly also ask to please hand that issue to Kriesi and come up with a solution. Please!

    Thanks a lot.

    P.S. I have seen several threads with that request so it’s not only me and TF-Photography!


    Hi, the best simple solution for now It’s embed no cookies version of youtube video:
    <iframe width=”560″ height=”315″ src=”″ frameborder=”0″ allow=”autoplay; encrypted-media” allowfullscreen></iframe>
    then make responsive youtube embed video.
    Simple way to make this is add in your custom CSS:
    .videoWrapper {
    position: relative;
    padding-bottom: 56.25%;
    padding-top: 0px;
    height: 0;
    .videoWrapper iframe {
    position: absolute;
    top: 0;
    left: 0;
    width: 100%;
    height: 100%;
    and cleary add to video

    <div class=”videoWrapper”><iframe width=”560″ height=”315″ src=”″ frameborder=”0″ allow=”autoplay; encrypted-media” allowfullscreen></iframe></div>

    Some video embedding use old school nested object and embed tags. It’s old school and no standard, but this technique was very widely used and it just worked.
    Object/embed suffers from the same problem that iframes do, the width and height are required:
    .videoWrapper {
    position: relative;
    padding-bottom: 56.25%;
    padding-top: 0px;
    height: 0;
    .videoWrapper object,
    .videoWrapper embed {
    position: absolute;
    top: 0;
    left: 0;
    width: 100%;
    height: 100%;
    The above technique is good, but it has several possible limitations:
    1) It requires wrapper element
    2) All old videos need HTML adjustments
    3) All videos need to be the same aspect ratio.
    Otherwise they’ll be forced into a different aspect ratio and you’ll get the “bars”. Or, you’ll need a toolbox of class names you can apply to adjust it which is an additional complication

    Best practice is consider a JavaScript solution! How to work:
    when the page loads all videos are looked at and their aspect ratio is saved.
    Once right away, and whenever the window is resized, all the videos are resized to fill the available width and maintain their aspect ratio
    Using the jQuery JavaScript Library:
    // Find all YouTube videos
    var $allVideos = $(“iframe[src^=’//’]”),
    // The element that is fluid width
    $fluidEl = $(“body”);
    // Figure out and save aspect ratio for each video
    $allVideos.each(function() {
    .data(‘aspectRatio’, this.height / this.width)
    // and remove the hard coded width/height
    // When the window is resized
    $(window).resize(function() {
    var newWidth = $fluidEl.width();
    // Resize all videos according to their own aspect ratio
    $allVideos.each(function() {
    var $el = $(this);
    .height(newWidth * $‘aspectRatio’));
    // Kick off one resize to fix all videos on page load

    Adding Vimeo
    Vimeo uses iframes too, so what works for YouTube will work for Vimeo. The HTML/CSS technique doesn’t need any alteration at all, and the jQuery solution could be fixed changing a single line:

    var $allVideos = $(“iframe[src^=’//’], iframe[src^=’//’]”),

    This solution could be used by the developers and integrated into the theme.
    I did it and it works perfectly.

    • This reply was modified 2 years ago by  lion73.

    Hi Lion, thanks a lot for your impressive reply. For normal videos i already chose the iFrame solution with the no-cookie URL from YouTube. What I didn’t do is add the custom CSS you recommend, I will look into this, thank you very much!

    But what I couldn’t figure out is how to use a no-cookie URL for a background video in a color section. This is what’s giving me the headache at the moment.

    Of course we have added a YouTube passage to our privacy policy like Basisilis suggested. But according to the GDPR, in our case the German DSGVO this is NOT enough.

    So I truly hope the Kriesi team will react and hopefully take Lion’s suggestions into a quick consideration.



    for color section try:

    <div class=”videoWrapper”><iframe width=”100%” height=”100%” src=”″ frameborder=”0″ allow=”autoplay; encrypted-media” allowfullscreen></iframe></div>

    Clearly the content of the page must be long enough to engage the video height.



    @lion73: Thank you very very much, I will try to figure that out.

    But I still believe an implementation into Enfold is mandatory and hope for a positive reaction from the Kriesi team.

    • This reply was modified 2 years ago by  L+T. Reason: typo

    Hi L+T,

    You can request this as a feature here

    If you need further assistance please let us know.
    Best regards,


    what should be possible is to insert on background-video input field the nocookie link version too.
    All other things can be managed this way:
    and the further link to my testpage:
    it uses the enfold surrounding container so it is responsive due to enfold settings of the containers


    what should be possible is to insert on background-video input field the nocookie link version too.

    Exactly Günther. Thanks for your information, I have seen that thread before and will look into this as well.

    However, @victoria, I do not believe this is a feature that has to be requested. From where I stand, and like I mentioned before, there are several other voices claiming the same all over the forum, Enfold is not GDPR compliant the way it is. Although you guys have done a GREAT job on the last update. But currently you advertize Enfold to be compliant while it’s not. At least not fully.

    Either way, Enfold is my theme of choice and will remain of course. It’s just to make a product which is nearly perfect completely perfect… There is no obligation for you, no doubt. But please listen to your users and add the option to use no cookie domains for YouTube videos.



    Hi L+T,

    This was an answer from Kriesi:

    If you need further assistance please let us know.
    Best regards,


    Well, as you obviously won’t do anything about it, I will now have to find solutions following lion’s or Guenni’s advice. Or remove the background video at all. I was faithful you would listen and add this needed feature. Another option for me could be to use another plugin like e.g. YouTube Lyte. This however will not work with background videos. And actually I wanted to avoid using more plugins and just use what’s included into Enfold.

    Of course you are right when you say that YouTube still sets cookies. But if you use the no-cookie URL’s NO cookie will come from YouTube until the user clicks on the play button! Only then cookies will be set, but e.g. no DoubleClick cookies anymore!

    Pretty much all DGSVO (GDPR) specialized lawyers in Germany state it is now obligatory to use the no-cookie URLs! Using an iFrame it’s no problem, using the Enfold fields it’s impossible without the extras from lion or Guenni I suppose.

    I am aware I am anything but important to you, but at the moment stating Enfold is GDRP or DSGVO compliant is simply false advertisement I am afraid.

    Anyway. I have my reply, have seen the same reply in all other threads on the topic and need to solve it myself. Thank you very much nevertheless.




    It is not False advertisment.
    If you read a lot more about it you will learn that if you write on your Privacy Policy, that you are using Youtube and you have youtube links, you are OK with that for your clients.
    if they do not want to see those videos they can block them from their browser.

    Best regards,


    Basilis: Stop making legally binding statements here that are not true.

    A follow-up instruction “Oh, your data has now landed on Google…But next time, next time you can’t allow this by opting out” is as pointless as a goiter and penetrate and trampling the GDPR with your feet.


    And once again I am very angry about Kriesi. Now I’m going to our lawyer for data protection and internet law this Monday. I’ve had enough.

    • This reply was modified 2 years ago by  Hokuspokus.

    @ Basilis, I understand that you have to defend your point of view. What I don’t understand is why you seem to think I am totally clueless on the matter and should read more about it. Do you know anything about my background?

    I most definitely won’t start an argument about false advertising. You guys have to know what you are doing. From a German perspective Enfold is NOT fully GDPR/DSGVO complaint which is a simple fact. And I like to think I can add a “yet” to my last sentence, because as you can see more and more Enfold users tell you the same thing on various threads throughout the Enfold forum. So I am convinced the Kriesi team will continue to not only improve Enfold itself but also improve the GDPR compliance.

    Talking about reading more, I can only advise you Basilis, to read more on the already ongoing lawsuits here in Germany, some because of a missing or insufficient privacy policy, some because of the useage of Google Web Fonts, and some because of not using the no cookie domains from YouTube! I can only provide information in German, but I know you got a bunch of people on the team who speak German. You should really get into this and discuss the matter in your next team meeting.

    I am fully aware that at the moment you find different voices on how to deal with YouTube videos. Stating a passage in the privacy policy is enough to safely use YouTube videos is and remains dangerous and simply wrong.



    If there are technical obstacles to integrate this variant, please say so. If this does not exist, it would be nice to let the user decide which version he likes to use. I think that to get rid of that DoubleClick Tracking-Cookie is positive enough to have that nocookie variant of youtube videos even if an ID is sent – and even if it is only an apparent security, the cookies that clearly violate the GDPR are banned.

Viewing 20 posts - 1 through 20 (of 20 total)

You must be logged in to reply to this topic.