@ismael & @guenni007 I cannot thank you enough for sharing your insights and assistance for my request.

I will definitely look into both approaches.

Fact or Fiction? I have other WordPress users tell me not to use too many plugins because they can conflict with one another and your site, etc. Now, I don’t have enough experience/knowledge on this to share my opinion. When should you use Plug-Ins vs coding (PHP, JavaScript, etc.)? Thoughts?

Thank you again for your help. I’m learning so very much…thanks to this forum and the Enfold Template.

Best Regards,
Julio

Ismael,

This is a wordpress/theme topic.

Check this out: https://make.wordpress.org/core/2020/07/14/lazy-loading-images-in-5-5/#highlighter_892127

Copying certain interesting paragraphs:
By default, WordPress will add loading=”lazy” to all img tags that have width and height attributes present. Technically this is handled on page output, similar to how responsive images are facilitated in WordPress by adding srcset and sizes attributes. To improve server-side performance of the two features, a new wp_filter_content_tags() function has been introduced so that img tags only need to be parsed once while then deferring the modifications to more specific functions related to the feature.

By default, WordPress will add a loading=”lazy” attribute to the following images:

images within post content (the_content)
images within post excerpts (the_excerpt)
images within text widgets (widget_text_content)
avatar images (get_avatar)
template images using wp_get_attachment_image() (wp_get_attachment_image)
Developers can customize this behavior through various filters, the most foundational one being wp_lazy_loading_enabled, which receives the following parameters:

$default: The boolean default of true to filter.
$tag_name: An HTML tag name. While per current WordPress behavior this will always be img, it should be noted that the loading attribute is a generic attribute and may be expanded to support further elements, e.g. iframes, in the future.
$context: A context string as additional parameters, indicating where the image technically comes from, usually a WordPress hook name. Based on how WordPress itself uses lazy-loading, the context can be one of the five values in parentheses in the list above.

And it gives you what the Enfold switch does. Which is great. But then it goes on:

In order to modify the loading attribute for very specific images, there are two different approaches, depending on the type of images:

For images that appear within a content blob (e.g. the_content, the_excerpt, widget_text_content), another new filter wp_img_tag_add_loading_attr can be used, which receives the following parameters:

$value: The loading attribute value, either “lazy” (default), “eager”, or false. If you want to disable lazy-loading for an image, it is strongly recommended to specify false so that the attribute is omitted altogether.
$image: The entire image HTML tag with its attributes.
$context: The context, similar as described for the other filter above.
For example, if you would like to disable lazy-loading for a specific attachment image with ID 42 in size “large” within post content, you could use the following code snippet:

And it gives you the snippet – but doing this is similar to my workaround for a specific image (taking the HTML that is the output and changing lazy to eager)

Theme developers are recommended to granularly handle loading attributes for images anytime they rely on wp_get_attachment_image() or another function based on it (such as the_post_thumbnail() or get_custom_logo()), depending on where they are used within templates. For example, if an image is placed within the header.php template and is very likely to be in the initial viewport, it is advisable to skip the loading attribute for that image.

And the Core Web Vitals issue was actually identified by them but it seems that on their experiment they didn’t consider all the 3rd party calls and javascript running times that can delay the LCP image from being loaded, so they write:
“Experiments using Chrome for Android have shown that the impact of such loading=”lazy” images in the initial viewport on the Largest Contentful Paint metric is fairly small, with a regression of <1% at the 75th and 99th percentiles compared to non lazy-loaded images – yet it is a consideration to make where theme developers can apply some fine tuning for even better user experience.”

So, maybe this could be a good new feature for Enfold? Allowing to Disable Lazy Loading on certain images from inside the Block Editor?

What concerns me is that you don’t see this on your installation. As it seems to solve mine with my HTML insertion/loading eager workaround. And Enfold is amazing when it comes to the ALB as it allows you to Enable/Disable Loading Lazy on an single image basis. All that’s missing is applying the same to a native or non-ALB image.

Please, let me know if my understanding of what is going on is correct. And if so, maybe this can help others who would like to implement my workaround or the one on functions.php that wordpress offers.

Thank you so much!

Havi

for example this (but there are many others like this and it doesn’t seem to have a logic)

public article

Da Lucio Battisti a Giovanni Battista, la Chiesa allo sbando: «Confusione, mi dispiace, se sei figlia della solita illusione e se fai confusione»

same article on the admin side
https://isoladipatmos.com/wp-admin/post.php?post=14857&action=edit&classic-editor=1

• This reply was modified 4 years, 2 months ago by Ismael. Reason: moved to private field

hi Ismael,

1) I don’t get an error in the Enfold > Theme Options > Theme Update panel but an error in the Envato Market plugin because more more fields are checked in the https://build.envato.com/create-token besides the

• View and search Envato sites
• Download the user’s purchased items
• List purchases the user has made

But on a other website where I use the Enfold it is the other way around, I created a token with ONLY

• View and search Envato sites
• Download the user’s purchased items
• List purchases the user has made

Here the Envato Market plugin gives no error message, but the Enfold > Theme Options > Theme Update panel gives an error upon validation.
See reply: #1337804

But please forget this,because this is not why I opened this ticket.

The real issue is the masonry BUG I started this thread for, which has not been solved!
The theme is upgraded to the latest version.
The two masonry.php are put in place, so the load more button is working again.

But the BUG is still there!

When I use the code you sent me,

add_filter("avf_masonry_entry_content", function($content, $entry, $atts) {
    return $entry->post_excerpt;
}, 10, 3);

it does not resolve the bug, it merely removes the excerpt everywhere.
But excerpts must be possible as well, that’s why we put the setting in the masonry on “Show tittle and element”.
When the owner puts in a text in the excerpts section of a portfolio item, it should appear, and it does.
But the BUG appears when the owner removes a text from the excerpts section of a portfolio item, see my former posts for screencaptures.
Please check the screencapture in the private content. The green checked items are correct excerpts, the red crosses are items that had previously added excerpts, that were removed later, but still persist in the masonry with extra breaks and content.

I am sorry to say, I am using the Enfold themes for quite some customers and quite some years now, but the way this is handled is not very satisfactory.

thanks,
Karin

• This reply was modified 4 years, 2 months ago by karinorage.

hi Ismael,

re 1: The envato market plugin still returns these error messages:

Incorrect token permissions, please generate another token or fix the permissions on the existing token.
Please ensure only the following permissions are enabled:

• View and search Envato sites
• Download your purchased items
• List purchases you’ve made

Additional Error Details:
Found too many permissions on token..
sale:verify

Updating with Thema Options > Thema Update is working.
For me that’s important enough, I don’t see the relevance of having the Envato Market plugin, so I will de-activate it.
It may be confusing for Enfold users to advise to use the Envato Market plugin as it gives error messages concerning checked boxes in the https://build.envato.com/create-token/ while Enfold advises/requires more boxes to be checked.
Here’s some info I found: https://forums.envato.com/t/token-error-found-too-many-permissions-on-token/278370

re.2 : Please advise where exactly to put the php-files. I have upgraded to 4.8.9 and I am using the child-theme

thanks,
Karin

Hi Guenni007, hi Mike,
I don’t understand the purpose of the filter, but whatever…

If I use the php script as recommended
either the whole headline has disappeared or even a whole paragraph.
But the css works fine if I add an !important.

try to deactivate ampersand via php

commented php

Thanks a lot for supporting me

Stefan

• This reply was modified 4 years, 2 months ago by steridhh.

Hi Yigit
So, i tested it with deactivating plugins.
First I deactivated one by one or groups (i.e. all Contact Form 7 Plugins), then I deactivated ALL plugins except the The Events Calendar plugin (because this is needed for the events).
Unfortunately the Advanced Layout Builder still did not work for this one user.
Have you any other idea?
Or should I send you the content of functions.php of the Enfold Child theme?
Best regards
Mike

Perfect! Thanks a lot, Guenni007!

Any idea on how to hide the head and footer on those posts? In my case it is a custom post type. Should be possible with a modification to the single.php file of the CPT – what do you think?

Even better would be a script to hide head and footer only if the entry is shown inside an iframe? Do you think that is possible?

Best regards,
Daniel

Hi Ismael
You said with the class name “big-prev-fake”. The theme doesn’t generate this container
And just downloaded a enfold from themeforest
And it seem you use.
We didn’t add this class to our images.

gallery.css line 69
.avia-gallery .big-prev-fake{
display: none;
}

gallery.js line 77
// since 4.8.8.2 we have a hidden img to support scrset and sizes – fallback to old version if missing
var newPrev = _self.find( ‘.big-prev-fake img’ ).clone( true );
if( newPrev.length == 0 )

gallery.php line 684
$thumbs .= “<div class=’big-prev-fake‘>{$prev_img_tag}</div>”;
$thumbs .= ‘‘;

Hi,

Sorry, login should be good now.

I have turned off all the plugins and im still getting the same error. Also, debugging is turned on now.

Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 16384 bytes) in /home/devcganet/public_html/wp-includes/formatting.php on line 486

• This reply was modified 4 years, 3 months ago by acscreativenew.