Forum Replies Created
-
Posts
-
Hey Tim,
I agree with 1 – 3. Working on a solution to improve it. Icon styling was kept to be backwards comp. with version before adding the new color stylings. But I have an idea to implement it.
ad 4) I have it in the dev repo – but currently postponed and no ETA.
Best regards,
GünterHi,
In the next update you will find an option checkbox:
SEO Support -> Support ALB Elements To Qualify Links
Replaces theme support ‘avia_rel_nofollow_for_links’ which already allowed to set the nofollow.
Best regards,
GünterHi,
We removed all HelveticaNeue from the fallback list.
Helvetica, Arial, sans-serif should do as fallback.
Will be in next update.
Best regards,
GünterHi,
Yes, this frame above allows to use $ for jQuery in “code to manipulate DOM goes here” and is executed when DOM is ready.
(function($){ var i,j,k; $(function() { // $ code to manipulate DOM goes here }); })(jQuery);Variables i,j,k can be accessed from inside “code to manipulate DOM goes here” but are invisible from outside the frame.
Best regards,
GünterHey!
Added a selectbox for image sizes to following elements:
Image
Image with hotspots
Magazine
MasonryWill be in next release.
Best regards,
GünterHey Guenter,
If you check https://api.jquery.com/ready/
$(function() {is enough as long as you do not need “Aliasing the jQuery Object”.
(function($){ ..... })(jQuery);is used to encapsule the code section from other js code (= like code in a function in php) to avoid name conflict.
Best regards,
GünterHi,
For the next release I added a new theme option:
“Main Menu -> Menu Handling for Mobile Devices In Landscape Mode”
This allows for mobile devices to keep burger menu also in landscape mode if portrait mode screen width has a burger menu.
If you would like to have a beta release to test let us know please.
Best regards,
GünterHi,
No, I did not test it – and I did not have this on my radar up to now.
If you find time to test it and want to share your experience with us, we would appreciate it.
Thank you once again for your input to improve Enfold.
Best regards,
GünterHi,
Thank you for this feedback.
I started digging a bit with google and now got a better understanding for the problem.
I found this article (you probably might know already): https://wp-rocket.me/blog/critical-css/
“Eliminate Render-Blocking Resources: WP Rocket Fixes It”
I add this topic to our dev repo so we keep an eye on it in future.
Best regards,
GünterHey Thomas,
Thanks for the ideas.
The decision to load the post css files late are that the CSS rules set in an element and placed in this file must override default CSS rules and we tried to use weakest selectors wherever possible to allow custom CSS rules (if necessary).
If you use filter ‘avf_post_css_create_file’ (return false) the CSS rules are placed inline in style tags right before the elements instead of the post css file.
Question is, what are “critical” CSS rules. We could consider to add those to a second post css file that is loaded first (or add them inline in header).
Best regards,
GünterHi,
FYI: the fix was added to next release 4.8.6.3.
Have a great day and enjoy the theme.
Best regards,
GünterHi,
Select Your Editor -> Use Classic Editor
Disable Block Editor For Selected Post Types:You can only disable block editor for post tyes, means with Strg + Click select the post types you never want to use block editor.
e.g. if you select page and posts these will always open in classic editor (only “Edit” is visible),
portfolio will have “Classic Editor” and “Block Editor” links below title on “Portfolio Items” page.Best regards,
GünterHey Guenter,
add_theme_support( 'avia_gutenberg_post_type_support' );– adds an additional selectbox to theme option “Editor”
– you can select for each page/post/.. which editor you want to use to editBest regards,
GünterHi,
documented in place
in the file where we add the filter we add a comment with the parameters.
Best regards,
GünterHi,
Can you please add the following code:
.avia-related-tooltip{ position: absolute; z-index: 9999999; padding: 0; width: 200px; border-radius: 2px; box-shadow: 0px 3px 13px 0px rgba(0, 0, 0, 0.1); border-width: 1px; border-style: solid; padding: 15px; margin-top: -10px; } .avia-related-tooltip .avia-arrow-wrap{ top: auto; bottom: 0; position: absolute; left: 50% } .avia-related-tooltip .avia-arrow-wrap .avia-arrow{ border-top: none; border-left: none; top: -4px; }at the bottom of enfold\css\shortcodes.css (will be added there in next update)
or until next update to the Quick CSS field.
FYI: Code is moved from enfold\config-templatebuilder\avia-shortcodes\blog\blog.css which is not loaded when blog is disabled.
Best regards,
GünterHi,
Please read this reply: https://kriesi.at/support/topic/background-image-is-not-displayed-anymore-after-update-to-enfold-4-8-6-1/#post-1317645
Maybe it helps to fix your problem.
And please update to 4.8.6.2 (latest release)Best regards,
GünterHi,
Via a filter in child theme – currently not.
You can update the core file enfold\footer.php in line 295 you find:
echo av_icon_string( 'scrolltop' );Replace this with:
echo av_icon_string( 'scrolltop', false );You need to update this whenever you update the theme.
If we might add a filter in future version it will be documented in place.
Best regards,
GünterHi,
Sorry for the problems.
When loading the page I get following error for
GET https://your_site_name/wp-content/uploads/avia_posts_css/post-5.css?ver=ver-1629459115 ---- Status403 Forbidden VersionHTTP/2 Übertragen894 B (752 B Größe) Referrer Policystrict-origin-when-cross-originThis file holds the CSS to display the background images and other styling needed for this page (this was added starting with 4.8.4).
One user could solve it by enable query parameters (which he had blocked before) needed to invalidate browser cached post-5.css file when page is updated (?ver=ver-1629459115).
Alternate way (but not recommended, only if your server configuration makes it absolutly necessary) is to disable file generation by adding this to your functions.php file:
For testing and until you find a solution with your hoster it is OK.
Best regards,
GünterHi,
Did you read https://make.wordpress.org/core/2021/06/07/wordpress-5-8-adds-webp-support/ chapter “Using WebP images”
Seems not all browsers support webp yet.
There is a polyfill to load: https://github.com/chase-moskal/webp-hero
Best regards,
GünterHi,
Thank you for the feedback.
The pastebin version is already merged for the next update.
The code as written in #1316178 is missing the priority and number of parameters – should be:
add_filter( 'wp_get_attachment_image_attributes', function( $attr, $attachment, $size ) { if ( $size === 'shop_single' ) { unset( $attr['loading'] ); } return $attr; }, 10, 3 );Glad that this fixes the problem.
Best regards,
GünterHi,
Glad we can help you.
Enjoy the theme and have a great day. Feel free to come back when you need further assistance.
Best regards,
Günter
