Hey!

We will add several GDPR related features with the Update to version 4.4. However, disabling Cookies is not one of them. After attending several Workshops and consulting a lawyer as well there are 2 reasons for that:

– Enfold cookies are no tracking cookies. they do not store any user data and are only used to set website behavior. (actually enfold does not really use cookies itself, apart from the breadcrumb navigation in conjunction with portfolio pages. we will disable setting this cookie is the breadcumb nav is disabled)
– Disabling cookies is, from what we have been told, a feature that should be mentioned in your data security policy but since the web browser has the capabilities to disable them there is no need for websites to implement that feature individually.

Please mind that this is what we have been told by people who are well versed in this subject, but its of course no legal advice. As you probably know a lot of the information that is out there is highly debated, and if it turns out that any of this is required we will change it.

Regards,
Kriesi

Hey!

The ip address is 85.13.149.161

Best regards,
Kriesi

Hey!
Yes thats possible. We need the folder name and the main plugin php file to add it to the check ;) (since we test with is_plugin_active() )

Cheers!
Kriesi

Hi Guys!

We are pretty much working on all of the things suggested here. More features, faster theme, better documentation, improved template builder, etc
In our Github repository there are currently 10 Pull requests with new features waiting and we are adding more every week. We have changed our support system internally and are really a lot faster when it comes to responding to requests. When we previously had a queue that was usually around 200 open threads we are now usually at about 50, sometimes even less. We have started this progress about 2 months ago by hiring new team members and changing our internal hierarchy and are still improving our support and the theme. You should reap the benefits in the upcoming months when the new documentation is ready and the new team members are fully integrated.

About the Mini Updates:

Unfortunately, in order to improve Enfold the way we want a lot of the core structure has to change, and thats why we are holding back with feature updates. Those are also the reason why we are doing these smaller updates. I get why you feel you are real time beta testing, and to a certain degree this is true. The reason why we are doing those smaller updates, and don’t change everything in one big swoop, is that I don’t feel we can afford to break the theme in a way that affects tens of thousands of users. Unfortunately we also can’t test those changes on 1000 different servers ourselves upfront so we need to let the community test those changes in small doses. And I do agree that it must get frustrating if you are one of the few who are affected by those changes once or more, but I also have to tell you that in general the process has been a success for us, since the few issues that our customers encountered were solved fast, and the number of people affected was minimal.

Anyways, I hear you and maybe we can implement a BETA testing feature if we need something similar in the future, where users can opt in to those updates. The only immediate solution for everyone affected several times is to skip those smaller patches and wait for the next big one.

Now a little more detail why we are doing what we are doing:

Our focus for a long time was to carefully pre-select the best possible options and elements for our users and implement them into the theme. Basically we wanted to only add what benefits the most users and let everything else should be added by plugins or custom code. Since the users base has grown a lot and we got much more niche use cases, we agree with most of our users, that we can no longer go that route. So we will add a lot more options and features, and also improve existing ones.
In order to not slow down the theme to an unusable degree we want to make every feature and every element optional. And that is unfortunately really tricky and is the cause for those multiple smaller updates, since it involves CSS and JS file creation/compression on the fly.

To make every option and every template builder element optional we are started splitting up CSS and JS files. This allows us to only load used elements and make sure only necessary JS and CSS is loaded in the front end. We also have added a compression script that bundles all those css and js files into one compressed and minifed version. Next step will be to add an optimization tab in the theme option that allows users to fine tune the optimization themselves. (eg: which level of compression, which files to compress, which elements to exclude, etc) This should also allow us to implement google AMP out of the box. It will also allow us to add any ALB elements that we like, even for niche use cases, since if a user does not need them they will simply not be loaded. Same with additional options: if an option generates a lot of extra CSS or JS we can simply split it up into a new file and it only gets loaded when necessary. That way the only thing we need to take care of is to not make the theme too complicated to use.

As said before: it will take a little while before you can fully reap the rewards of those changes but Enfold will be a much better theme once they are done. More features, options and demos and at the same time faster and more lean and clean out of the box.

Regards,
Kriesi

Small update: I found a workaround and already applied it to your server. the theme should work fine now, however, as long as the JS file can not be loaded the theme will fallback on not generating an improved version of those files, so you loose a little bit of optimisation.

Hi everyone. Sorry but this one took longer.

I was able to fix the issue on some level. “Only” did take me 10 hours to get to the bottom of this issue, which is actually two-fold :/

The first problem (very technical): for some reason the API to the mediaelement video, which is usually passed as a javascript data object, is no longer passed in Safari. (might be a mediaelement bug, probably introduced with the latest WordPress update)

I was able to circumvent that. It is now again possible to use the Video in Safari manually.

The second issue is Safari itself and its new policy regarding autoplaying content. You can read more about it
here: https://webkit.org/blog/7734/auto-play-policy-changes-for-macos/

Long story short: a user can change which kind of autoplay is allowed (with sound, without sound, no autoplay at all) but if it is disabled there is no chance that we can force the video to play without user interaction. So if autoplay is disabled by the user in safari there is nothing we can do about it.

Those fixes will be included in the patch tomorrow.
Cheers!
Kriesi

Hey!

Die buttons die wir in Enfold verwenden sind keine “like” buttons die mit facebook (oder anderen netzwerken) kommunizieren, sondern share links. Diese share links enthalten, anders als die “like” und +1 buttons, kein Javascript und können daher keine daten an die sozialen Netzwerke senden bevor sie geklickt wurden. Sie sind daher aus Sicht des Datenschutzes unbedenklich ;)

lg!
Kriesi

Just a quick notice: The Update (v 4.0.7) is now available on Themeforest :)

Hey Guys!

Thanks for the notice. This is an issue caused by very old PHP versions, so we unfortunately missed it. Sorry for that! The update (v 4.0.7) is already on its way to Themeforest and will be available within the next 15 Minutes or so. An alternate way to fix the problem is to update your servers PHP version. If you dont know how to do that please simply wait for the patch ;)

Sorry for the inconvenience.
Best regards!

Kriesi

Hey!

The problem is actually the way you set up the site and images. I am afraid that with the way the theme works this is problematic, since scale image to show the full image and parallax does not play well together. I would do it with a fullslide element with a single image. I set up the about page to work that way so you get an idea of how you could accomplish it for other pages as well.

Best regards,
Kriesi

Hey!

I guess we can write german? Should make things a little easier to understand ;)

Ich habe leider ein problem das lokal zu reproduzieren also mach ich oder verstehe ich wohl irgendetwas falsch.

Hier nochmal die schritte:

1. Theme installieren
2. Seite mit 5 page anchors anlegen und zwischen jedem genug text das ordentlich platz zum scrollen ist
3. Menü anlegen mit anchor-links.

Soweit korrekt? Wenn ich die seite dann über einen externen link oder auch internen link öffne, bin ich immer am korrekten page anchor. (Sowohl bei mir am testserver als auch bei dir unter vonsalm.de)

Unterschiedliches verhalten zeigen die Seiten wenn ich dann auf der seite selbst navigiere. da fährt deine zum falschen punkt und bei mir passts.

Ist das so mal korrekt?

Hi,

As you can see on our maps the new google way of mobile implemtation is already implemented. http://kriesi.at/themes/enfold-2017/pages/contact/

On a mobile device, by default, scrolling the page down will not interact with the map. It will just display the notice implemented by google to use 2 fingers to interact with the map.

If you use a two finger scroll or a pinch on the map that will work fine then.

Best regards,
Kriesi

Hi,

I read a little more and am afraid without the mod_security I can’t tell for certain if its causing the problem. At this stage I would also recommend for your hosts assistance and ask to disable the feature temporarily to see if this is indeed causing the problem. You can also ask them for the log file which might help as well :)

Best regards,
Kriesi

Hey!

Unfortunately this was removed by google as an api option. Pancontrol basically only exist now in outdated versions of the google maps api. Therefore I am afraid we will remove it as well…

Best regards,
Kriesi

Hey!

Please send me a mail to (Email address hidden if logged out) with the amount you charge/word and a few ideas of what you would post about. We had some writes in the past but I think the impact of those articles were not very big. I would probably be willing to try 1/month and see how that works out…

Best regards,
Kriesi