Hi,

No idea why the script is reported as a security alert.

The only thing you can try is if you do not need the GDPR stuff to remove our script with the filter and enqueue your own or modify the core file and only use the code within

if( allow_continue )

Maybe there is an option to allow fonts.googleapis.com as a secure link ?

Best regards,
Günter

Hi,

Thanks for your feedback.

Glad we could help you. Enjoy the theme and have a great day.

Feel free to come back whenever you need assistance.

Best regards,
Günter

Hi,

Having a look in your backend:

PHP is very outdated with 5.6.40. You should upgrade to minimum 7.4.xx (or 8.0.xxx) – also for security reasons.
Enfold is also not up to date – we have 4.9.2.1 out since a few weeks.

Also depending on your hoster it could be, that he is doing some caching. You should check this and if yes, maybe he can provide you a staging server without this caching for testing.
WPML has integrated the translation management in core lately (it was a seperate plugin before) – therefore they encourage to use “Translate” and not “Duplicate”.

This also works very well with our Advanced Layout Builder.

We have fixed 2 minor WPML bugs in next Enfold 4.9.2.2 – so if update to 4.9.2.1 does not help we can give you a pre release of 4.9.2.2 to test.

Best regards,
Günter

Hi Tim,

I’ve not really digged into schema.org.

But having a look at https://schema.org/VideoObject and the examples at the bottom of the page the only idea I have would be to add a meta tag like:

<meta itemprop="contentUrl" content="link_to_video" />

right after the opening div of the video element.

Could you check if this helps please?

Best regards,
Günter

Hey Caiser_Souze,

Sorry for the problems.

Please update to the latest version 4.9.2.1. This should fix the problems.

Best regards,
Günter

Hi,

Sorry for the problems.

To me this sounds as a main problem coming from WPML (and maybe in conjunction with the classic editor translations). As far as I know WPML has switched to translation manager (which is now part of the core) and deprecated the classic.

So as a first step please open a ticket with WPML (and you can also add the link to this post there) and provide links to your staging site.

The compatibility team will then check your problem and get in contact with us if necessary.

Best regards,
Günter

Hi,

Checking Enfold for the filter:

$lightbox_img_size = apply_filters( 'avf_alb_lightbox_image_size', 'large', $this->config['shortcode'], $atts, $content );

is used in context of:

‘av_gallery’
‘av_horizontal_gallery’

For masonry elements (class-avia-masonry.php):

$lightbox_img_size = apply_filters( 'avf_alb_lightbox_image_size', $lightbox_img_size, 'avia_masonry', $entry, $this->config );

For slideshow elements (class-avia-slideshow.php):

$this->config['lightbox_size'] = apply_filters( 'avf_alb_lightbox_image_size', $this->config['lightbox_size'], 'avia_slideshow', $this->config, '' );

It might need to extend the filter function and check the additional parameters of the filter if you need more control.

Best regards,
Günter

Hey Tim,

Thanks for contacting us.

A very rough overview of Enfold 5.0 plans you find here:

And we will have a focus on frontend in future (after having spent a lot in backend dev in the last releases).

I added this post to our dev repo.

To your questions:

– caption is used in lightbox title only in this element and is stored in the media library so it is available throughout the site
– custom image links added to media library are used throughout the site (as far as I know) – there is no way to limit them to a gallery. I can think of a filter to allow to customize them – all other would be too complicate and blow up code (and database).

Best regards,
Günter

Hi,

@Guenni007

For the gallery if you look into gallery.php for the filter:

$lightbox_img_size = apply_filters( 'avf_alb_lightbox_image_size', 'large', $this->config['shortcode'], $atts, $content );

it is

$this->config['shortcode'] = 'av_gallery'

This rule should follow in other shortcodes also.

Best regards,
Günter

Hey Jan,

Thank you for your interests on Enfold 5.0 (and oncoming versions).

There are 4 major features we plan. I can only give a rough idea here at the moment as we are still working on it:

– New ALB element “Section Slideshow” (like tab section you can create custom content slides and show them in a slideshow)
– Curtain reveal option for images, columns, images in masonry elements
– Positioning ALB elements inside their surrounding container (position: relative, absolute and this responsive)
– Parallax effect for ALB elements (planned is also left/right)

Best regards,
Günter

Hi,

You have the file events_countdown.php double in the shortcode folders, therefore it is loaded twice and this is causing the problem:

…/httpdocs/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/events_countdown/events_countdown.php which is correct
…/httpdocs/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/events_countdown.php which is wrong – please delete this file.

When uploading the theme via ftp please always delete the complete folder enfold and then upload the new enfold folder.

Best regards,
Günter

Hi guys,

Enfold 4.9.2.1 was released shortly. This should fix the problem.

Best regards,
Günter

Hey aledef,

We are very sorry for the problems.

Thanks a lot for the credentials.

I could locate the problem. It was caused by adding translateable strings for the sidebar names which broke activating them in frontend.
I reverted this back on your test site.

I added the fix to core and we will make a hotfix in the next days.

The file changed is enfold\includes\admin\register-widget-area.php

You also find the modified version here:

https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_4_9_2/includes/register-widget-area.php

Best regards,
Günter

Hi,

if disable the CSS files (= post specific css files) solves your problem you can do that and should be safe.

Just to give you some background:

post specific css files are created on pageload once and exist until the page/post is updated, theme options are updated or a theme version update takes place and are specific for this page/post. They are independent from the merge css or js files option settings and are located in …/uploads/avia_posts_css folder.

Merged css or js files are “static” core files that are needed for every page and only change on theme version update and are located in …/uploads/dynamic_avia.

Hope this helps you for a better understanding.

Best regards,
Günter

Hi,

Sorry for the confusion.
As you do not use js and css file compression (I thought you díd) than “Delete old CSS and JS files?” is not used.
Please ignore everything.

disable the CSS file generation:

There should be no impact at all.

The styles for ALB elements that are written to the css files for each page/post are instead added right before the element in style tags in HTML DOM of the page/post.

Best regards,
Günter