Forum Replies Created
-
Posts
-
Hi Mike,
Sorry, I think there might be some confusion.
I’m not referring to the prev/next blog post slides where you can move between post items.
If you look at the page I referenced in my private area, I’m referring to the easy slider’s navigation buttons, which by default appear on mobile as well as desktop.
Lighthouse is flagging an accessibility issue with them. If you run the lighthouse test yourself you can see what I’m talking bout. It shows clearly that it is related to the easy slider.
Hope that helps.
Hi @Günter
Excellent, as always thanks for checking and giving a clear explanation. Issue was I had the image stretch option selected, and I didn’t think that it would function differently simply based on that option.
But good to know for the future, much appreciated.
Hi Gunter,
Can you please take a look at the Partner/Logo Element in the ALB elements. I’ve just tried using it and it doesn’t seem to be outputting srcset at all?
Thanks again
Tim
Hi Victoria,
Excellent thank you, that will do it.
Might it be an idea in each section of the Enfold settings tabs (like Header, Footer, etc) to link directly to the relevant part of your documentation? I wonder if it would reduce support requests for you. I know I sometimes find the documentation hard to find what I need, but a direct link would help that.
Just an idea.
Hey no problem.
It would be good to have styling options for it.
For some reason it appears that it currently doesn’t use the default body/heading font styles? I didn’t spend long playing with it, but at first glance I noticed it was different to the rest of the page, and so I went looking for styling options.
Im sure others will do the same
Thanks for investigating it further.
Really appreciate all the improvements being made to the theme lately.
Hey thanks for implementing this great future so quickly with the new Post Metadata element!
Just a question, when editing an element within it, such as the Author or Last Modified Date elements, the “Styling” tab WITHIN those elements is completely blank.
Not the overall styling tab, just the one for each little individual element.
Is this intentional? Will some styling options be added?
Thanks so much
Hi Ismael,
Great, thanks for looking into it. Hopefully you’ll find a way to resolve it and the browsers reader view issue at the same time.
Regards,
THP
Hi Gunter,
Appreciate the speedy response as always.
Yes, I noticed that Litespeed does that for any images that don’t have a srcset attribute, as I guess its looking for that in the code to inject the lazy loading correctly.
So I’ve done some more digging. Yes, that images size is listed as a thumb in the Image Thumbnails section of Enfold.
I just tried using the same image, but using any other image thumbnail size available from it (including Full Size) – and it works, full srcset added and litespeed showing it up correctly.
It is directly connected specifically to that particular image size thumbnail.
Any ideas?
Thanks again
Thanks Gunter, really appreciate how quickly you reply and action these items.
I noticed you added WP 5.5 lazy loading to the coming soon part as well, that will be great.
Hi Gunter,
Really liking having srcset now in the theme, thanks again.
However, it doesn’t appear to be added for the theme logo? Could you take a look?
Thanks Gunter, really appreciate you adding that to the next release. May want to double check the other ALB elements as well?
Hi Gunter,
I have just updated to the latest version 4.7.6 and was checking a few things out.
Noticed that the testimonials ALB element outgoing links are missing rel=’noopener noreferrer’ – not sure if this was ever added (I think it was?) or for some reason it was stripped out in the latest update, but can you please take a look?
Regards
Tim
Hi,
Well that is excellent to hear Gunter, long time coming but I’m so glad to see work like this happening on the theme.
Im unable to help test at the moment sorry, but really look forward to the release.
And yes, if full support for native lazy loading (and the relevant tweaks like excluding the logo etc) are able to be included soon too that will be another great step forward for Enfold.
Also, WordPress 5.5 will implement lazy loading and image features to reduce layout shift.
It mentions in there that themes can improve the experience even more, such as:
“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.”
Since work is being done on improving image handling in Enfold, would be great if 5.5 compatibility could be considered as well :)
The latest change log for the upcoming version now says:
feature: Responsive images support (srcset and sizes attribute) – using WP logic to ALB elements
Can I get my hopes up???? Will the theme now fully support srcset for ALL ALB elements as of the next release????
I REALLY HOPE SO!
Hey Rikard,
Responding as requested.
Look forward to hearing what you find out, as there’s certainly something going on.
Cheers
Tim
Hi @Ismael and @Günter and team, as you can see I started this thread a year ago. Many others have made similar comments on many other threads.
It really saddens me to hear your latest reply.
I’m not sure how you can have different priorities to something so core in a modern web, and that Gunter was actually working on a year ago.
This is your product, so of course we can’t tell you what to do, but please, please listen to your customers. This feature will benefit every single Enfold user, whether they know it or not!
Perhaps if we knew what these ‘other priorities’ were we may try to understand. But at the moment it just feels like you are neglecting to keep the theme up to date with web standards – not to mention your competition.
I love Enfold and have 9 licenses for it in use. Please don’t take this as an attack, but as a plea for the Enfold team to listen to their customer base and communicate better with us.
Please, please, please reconsider your position on this essential part of the theme.
A lot of interest in getting responsive images in place. Would really, really appreciate a timeline on this please Enfold devs.
Hey guys, sorry to derail this thread a little but can you please prioritise Responsive Images? It’s been in the ‘coming soon’ section for ages now and this is a very important feature that was implemented a long time ago in WordPress itself.
Meanwhile an instagram feed thing has been prioritised over this and finished for the next release – not all of us need this. But all of us would benefit from having proper responsive images implementation.
Why would this fix not be included?
Is there a 4.7.1 release imminent with it included, enfold staff?
@Yigit, thanks for the update, helps us plan when we get clearer information like that.
Can you confirm, will responsive images for all image elements finally be included in this release? I really hope so.
Thanks for all your work, hope to see a roadmap for Enfold for 2020.
Hey @ismael,
Thanks for getting back to me.
So, I have your snipped from an early reply in my child theme functions file, all my products have prices, and I tried enabling reviews to see if that did the trick. Still not quite right.
It does generate some product data (and same if reviews are turned off) but not a complete Product listing for Goole to recognise its actually a product.
Hi,
Has the dev team responded yet?
I do have Yoast SEO installed, but as in my original posts private details, so does the other site. Both of my sites have the same plugins that would touch Schema. The only difference between the two is one site uses standard WooCommerce product pages, the other one uses custom product pages built with the ALB.
Hi Ismael,
I’m sorry, I don’t really understand your response properly.
My basic question is: Is there a fix for this coming?
Adding your snippet still does not allow Google to see the page as a legitimate product.
Thanks
Tim
Hey Ismael,
Thank you, I have tried the code and it works (kind of). In the structured data testing tool is isn’t displayed as a Product, although it does contain the product information. And the description section contains all sorts of duplicate and unnecessary information.
I understand what you are saying about having the required information. But I don’t understand the logic behind how it currently works. Let me explain:
If I am selling a product, then surely I want all the product related schema along with it. However, I might like to customise the look of the product – thus why we would use the ALB to build the product page. Using the ALB doesn’t mean I want parts of the product schema missing, just because I won’t be displaying them on the front end. That is just a design choice, not a technical choice.
It would be a lot more logical to me to grab all the related product data and output it regardless of if it will be shown on the front end or not. But perhaps to keep everyone happy, this could simply be an option in the Theme settings or on each product page – “Include all schema markup even if not displayed on front end? Yes/No” type thing.
I hope that makes sense.
Can I ask, is the code you posted to me above the fix for this, or are your devs looking into this some more for better implementation?
Thanks a lot
They really need to add a WooCommerce Product Image element in the ALB as currently, I think you need to create a standard image or gallery for what you want.
I’ve had the same issue and always wondered why the option to place the product image wasn’t easily available in the builder.
