Hey Guenter,

Danke, dass Du meinen Fehler auf Github bemerkt hast – schon korrigiert.

Footer and Socket part of #main

Da .all_colors Teil von #main ist sind die Auswirkungen nicht wirklich leicht abschätzbar.

Was ich mir eher vorstellen könnte (hab aber noch nicht genauer angeschaut) wäre die beiden Teile noch in ein eigenes div zu geben.

Damit sollte man diesen “Curtain” Effekt auch machen können (könnte ich mir auch als Theme Option vorstellen).

Best regards,
Günter

Hi,

We added the filter ‘avf_color_sets’ as you suggested for the next release.

Best regards,
Günter

Hi,

@Guenni007

I updated enfold options for footer (and also metabox in page sidebar):

Select a page to replace footer and keep socket
Select a page to replace both footer and socket

Footer and Socket part of #main

There are rules e.g. for widget title:

#top #wrap_all .all_colors h3{
text-transform: none;
}

This also effects your sample page (see “Adresse” is upper case).
And class all_colors is in #main div.

Best regards,
Günter

Hi,

Thank you for using Enfold and you found the solution.

Enjoy the theme and have a great day. Feel free to come back when you need further assistance.

Best regards,
Günter

Hi,

Thank you for using Enfold – and glad you solved the problem.

Enjoy the theme and have a great day.

Best regards,
Günter

Hi Phet,

I could locate the problem.

CSS for .avia_loading_icon, …. was located in enfold\config-templatebuilder\avia-shortcodes\portfolio\portfolio.css, this file might not be loaded when portfolios are not used.

I moved the stylings to enfold\css\shortcodes.css and kept the default background:

background: rgba(0,0,0,0.7);

Will be in next update 4.8.6.2

Best regards,
Günter

Hi,

Thank you for this feedback and sharing this information.

Glad that everything is working now.

Best regards,
Günter

Hi,

@taaning

Are you using https://wordpress.org/plugins/sg-cachepress/ ?

Please update to the latest version 4.8.6.1 and try to add this code to your functions.php:

https://github.com/KriesiMedia/enfold-library/blob/master/actions%20and%20filters/Performance/avf_post_css_create_file.php

– save theme options (this invalidates and removes all post css files)
– clear server and browser cache

If you need help, please let us know and we can do it for you.

Edit: Please also have a look at this reply:

Best regards,
Günter

Hey Thomas,

Thanks for contacting us.

The post css files hold custom stylings for ALB elements that had been placed inline html style=”..” before.
We started to change this with 4.8.4 for 2 main reasons:

– make the code for the elements better maintainable and readable (and keep it stable) because creating the stylings and layout html has been seperated
– we started to add more styling possibilities to elements like button, notification box, section, columns, … (and will continue with it in oncoming versions) and inline styles do not support everything (e.g hover effects, …)

If you check the HTML of a page you will find the link to the css file:

<link rel='stylesheet' id='avia-single-post-206-css'  href='http://localhost/wp56/wp-content/uploads/avia_posts_css/post-206.css?ver=ver-1628531209' type='text/css' media='all' />

The “ver=…..” is a unique timestamp that is generated when the css file is generated (once on first page load or when it had been invalidated).

The css file(s) are invalidated:
– when a page/post/… is updated
– when saving theme options
– when theme is updated (action ava_after_theme_update is triggered)

With 4.8.6.1 we added filter avf_post_css_create_file to skip generating these files and add it in

<style>..</style>

tags:

see https://github.com/KriesiMedia/enfold-library/blob/master/actions%20and%20filters/Performance/avf_post_css_create_file.php

So on developing sites you can use the filter, on live sites after changing files save theme options and clear server cache should do.

Best regards,
Günter

Hey rvga,

Thank you for using Enfold.

Sorry to say but out of the box and without programming skills this is not possible.

It would need to get a deeper insight what logic is needed to update the element. Then you can decide what way would be the best to store and update this information needed for the element to update correctly.

Best regards,
Günter

Hi,

Thanks for feedback.
Enjoy the theme and have a great day. Feel free to come back when you need further assistance.

Best regards,
Günter

Hey Phet,

Sorry, this is not possible because the masonry galleries use the WP paging logic and this is not bound to a gallery.

This is a known limitation.

Consider to use the “Load more” button feature.

Best regards,
Günter

Hi,

@christiemade

Thanks for feedback and glad it fixed your problem.

Together with the help of @edolmen we could localize a problem with minification plugin and wrong aligned background images.

We are working on a fix for this for the next update.

Best regards,
Günter

Hi,

Update: Above was for original homepage.

I created a new page (see below).

– After create not sure but I think it looked OK in frontend being logged in (except image adjustment)
– I updated the page
– Section is “missing” except button
– Open page not logged in – visible

Checking the HTML:

Logged in the HTML content is present but invisible – CSS files are different for non logged in users:

..siteground-optimizer……. for non logged in

The only idea for that would be (selectable with a theme option):

Add our CSS as inline
<style>...</style>
right before the element for logged in user and only create our post css files when the first non logged in user accesses the page.

Best regards,
Günter

Hi,

I cannot reproduce the problem on my server.

I copied the shortcode to my debug textarea, only changed the attachment id for the background image, and then saved it (as I did not open a modal popup this does not change anything – so the shortcodes are identical to those on your site).

Opening the page in frontend the image is correct.
I also activated YOAST, but this does not change anything – it renders correct.

My first idea was, that a shortcode setting (either a hidden one or a missing attribute) causes this. But I did not find any.

———-

I’ve just seen, that you updated your site to 4.8.6.

Inspecting the CSS for the image it shows:

background-position: 50% 0;

but our theme outputs:

background-position: center left;

Seems, that your minification plugin (or server) translates center to 50%, left to 0 not taking into account, that CSS interpretes this differently. If you change it in dev console to

background-position: 0 50%;

the image position is correct.

(See https://developer.mozilla.org/en-US/docs/Web/CSS/background-position)

As up to 4.8.3 this setting was inline in a style=”….” so it was not changed and worked.

Conclusion 1: This is something we have to change in our theme to become compatible (becomes high priority)

—-

Why it disappeared after saving (cannot reproduce either):

I do not want to change and save your original page – can you (or I) create a test page with the same content – simply copy the content of the debug window into the debug window of an empty page (ALB mode enabled) and save.

Thank you for your help.

Best regards,
Günter