Forum Replies Created
-
AuthorPosts
-
Hi,
Glad that it works now.
Please have a look here: https://kriesi.at/support/topic/post-css-and-caching-issue/#post-1316059
Could the query string cause the problems in your setup ?
Best regards,
GünterAugust 11, 2021 at 1:26 pm in reply to: Masonry Gallery Preloader Spining Wheel in Page Preview Mode. #1316265Hi 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ünterAugust 10, 2021 at 2:51 pm in reply to: Earliest version of PHP to be able to use latest Enfold? #1316082Hey mterrianrode,
Thank you for using Enfold.
Actually Enfold should be able to deal with 7.0 or higher – this message is not php related.
Can you try to increase your memory limit – see https://docs.woocommerce.com/document/increasing-the-wordpress-memory-limit/
Best regards,
GünterHi,
Thank you for this feedback and sharing this information.
Glad that everything is working now.
Best regards,
GünterHi,
Please update to the latest version 4.8.6.1 and try to add this code to your functions.php of the child theme:
– save theme options (this invalidates and removes all post css files)
– clear server and browser cacheBest regards,
Günter- This reply was modified 3 years, 3 months ago by Günter.
Hi,
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:
– save theme options (this invalidates and removes all post css files)
– clear server and browser cacheIf 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ünterHey 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:
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ünterHi,
Thanks a lot for your help.
Glad that this solves your problem.
Do you need any further assistance to this or can we close this topic?
Best regards,
GünterHey 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ünterAugust 9, 2021 at 12:20 pm in reply to: Issue with background colors -> Background Gradient #1315831Hi,
Thank you for the credentials.
I had a look in your backend. Though it says 4.8.6 the file structure shown by theme editor in backend is different than it should be.
e.g. enfold\config-templatebuilder\avia-shortcodes\columns.php, enfold\config-templatebuilder\avia-shortcodes\section.php
have been moved to
enfold\config-templatebuilder\avia-shortcodes\columns\columns.php
enfold\config-templatebuilder\avia-shortcodes\section\section.php——
There is an updated section.php file based on 4.8.6 (merged into oncoming release planned for the next days):
I would suggest
– you update your staging site with ftp (delete the complete enfold folder)
– replace enfold\config-templatebuilder\avia-shortcodes\section\section.php with the content of
https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_4_8_6/shortcodes/section.php
– save theme options (this invalidates our post css files and forces a rebuild)
– clear server and browser cacheThis should solve your problem
Best regards,
GünterAugust 9, 2021 at 7:51 am in reply to: Bug report: Lockable Custom CSS Class inside Custom Elements not working #1315776Hi,
Thanks for feedback.
Enjoy the theme and have a great day. Feel free to come back when you need further assistance.Best regards,
GünterAugust 9, 2021 at 7:48 am in reply to: Enfold 4.8.5 breaks Masonry Gallery – images not showing #1315773Hi,
Glad we could solve the problem.
Enjoy the theme and have a great day.Best regards,
GünterAugust 7, 2021 at 1:24 pm in reply to: Using multiple masonry gallery with pagination, on the same page. #1315029Hey 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ünterHey Guenter,
No, we use only default WP implementation. This adds attribute
loading="lazy"
to images and this uses browser implementation.
Best regards,
GünterHi,
@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ünterHi,
What I can think of is adding a filter for the sizes attribute – if you think this helps you.
Best regards,
GünterHi,
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 – visibleChecking 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ünterHi!
Thanks, will create a new page to check and let you know.
I open the homepage both logged in with my account and in another browser not logged in I see image in both centered.
Best regards,
GünterHi,
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ünterHi!
Thanks, I’ve copied the shortcode and will be back, as soon as I’ve found the problem.
If possible, please leave the code in functions.php. Thank you.
Cheers!
GünterHey edolmen,
Thank you for the login.
I would need access to the underlying shortcode. As I cannot edit functions.php of the child theme, can you please add the following into this file:
add_action('avia_builder_mode', "builder_set_debug"); function builder_set_debug() { return "debug"; }
This adds a textarea in backend where I see the shortcode and can copy it to my dev server to check, what is causing the problem.
Do not forget to make a backup of functions.php for a fallback.
Best regards,
GünterHi,
After updating the php file – did you:
– save theme options (this invalidates our post css files and forces a rebuild)
– clear server and browser cacheIf this does not help we need access to the shortcode of the page so we can check it on our dev server to find the problem.
Please enable debug mode by adding the code provided in this link to your functions.php file which can be accessed from Appearance > Editor
This lets us view the shortcode for all the page elements.
Then we would need WP admin access to your site and the link to the page and which section is not working.
I would suggest you open an own thread so the private content is only visible to you and our moderators.
Best regards,
GünterHi,
Thank you for pointing at this.
I added it to our dev repo – but at the moment I cannot provide a quick solution and no ETA for a possible implementation. There are too many things to take care of and this needs testing.
Did you check https://stackoverflow.com/questions/19837035/media-queries-check-min-height-and-min-width ?
Maybe this helps you to find a solution for your install.
Best regards,
GünterHi,
Glad everything is working for you now.
Enjoy the theme and have a great day. Feel free to come back when you need further assistance.
I will close this thread for now.Best regards,
GünterAugust 6, 2021 at 9:47 am in reply to: Bug report: Lockable Custom CSS Class inside Custom Elements not working #1314779Hi,
I recheched again.
ALB Image Element
Custom Element has “Lockable Custom CSS Class” my-locked-image and is set to locked
Child Element has “Custom CSS Class” my-image ( and my-locked-image in red border )HTML output for image container div has following classes (both classes are included):
class="avia-image-container av-kp01nouk-24ebddcda538fba55c28445e767ecf49 av-styling- av-hover-grow avia_animated_image avia_animate_when_almost_visible av-rotateInUpLeft avia-align-center avia-builder-el-0 avia-builder-el-no-sibling my-image my-locked-image avia_start_animation avia_start_delayed_animation"
Can you please create a WP admin account for us so we can check it ?
And also specify steps how to reproduce please.Best regards,
GünterAugust 5, 2021 at 4:39 pm in reply to: Bug report: Lockable Custom CSS Class inside Custom Elements not working #1314690Hey Dommel,
Thank you for using Enfold.
“Lockable Custom CSS Class” is intended to be set and locked in the custom element (= parent) and is then used in the child element.
Create a custom image element and lock it there. When using this you see the class in a read only field in the child and you cannot change it.
If you use a “normal” image element both fields can be filled. The result is that both classes are used – in .avia-image-container.
Best regards,
GünterHi,
Glad your problem is solved.
Enjoy the theme and have a great day. Feel free to come back when you need further assistance.
I will close this thread for now.Best regards,
GünterHi,
The 2 filters have been deprecated, the action is still valid.
There is a new theme option “Enfold WPML Language Flags” in Header Tab.
That should remove the flags.
Best regards,
GünterAugust 5, 2021 at 11:51 am in reply to: Color Sections + Boarders NOT working! Please help! #1314629 -
AuthorPosts