Hi Andy,

Yes I am aware of that, however they only allow paying costumers to submit tickets, and since I haven’t purchased anything from WooThemes until now, I am unable to do so.

Regards,

José

Hi again,

Thanks for your suggestions.
I will go with your advice and stick to “hiding with CSS” as that seems to be the cleanest and most future-proof solution available.

However, I am still struggling with the issue of having some products showing up more than once in my ‘shop’ page, although I think I have gathered some more information on the problem.
It seems to be a problem with WooCommerce itself, as I have tried totally deactivating the infinite scroll functionality, and even switching themes between Enfold and Storefront (WooCommerce default theme) and I still get some products showing duplicates (on different pages).
It seems to be related to the ‘sorting options’ in WooCommerce because I don’t see any duplicate products if I choose the ‘Default Sorting’ or if I ‘sort by average rating’, but I always get duplicate products if I ‘sort by popularity’ or ‘sort by newness’ / most recent (which is the sorting I want to use).

I still have the development version available in case you want to do some tests on it, the credentials for access are still the ones provided on my OP.

I’m going to try and reach Woothemes support as well, since I believe this problem to be with their plugin, but any help you might be able to provide on this will be very much appreciated.

Best regards,
José

I have been fiddling around some more and I think I may have found a reasonable solution.

In my child-theme functions.php I added:

add_action( ‘woocommerce_pagination’, ‘woocommerce_pagination’, 9 );

add_action( ‘woocommerce_after_shop_loop’, ‘woocommerce_pagination’, 9 ); //add woo pagination again

I also tried adding:

remove_action( ‘woocommerce_after_shop_loop’, ‘avia_woocommerce_after_shop_loop’, 10);
add_action( ‘woocommerce_after_shop_loop’, ‘dz_woocommerce_after_shop_loop’, 10);

function dz_woocommerce_after_shop_loop()
{
echo “</div></main>”; //end content
}

with the intention of removing avia_pagination which became redundant, while still properly closing the content container, but somehow the avia_woocommerce_after_shop_loop function is still being loaded and it was messing up my HTML structure (trying to close the content container twice), so I ended up removing that second block of code for now, and I think I’ll end up just hiding avia_pagination through CSS.

Any suggestions to improve this solution will be much appreciated.

EDIT:
As I have been doing some further testing to this, I came across some weird behaviour: if I’m using woocommerce’s default ordering for my products, the lazy load seems to work properly, however when I’m sorting my products by “Most Recent” (which is what I have to use for the production site), some products are being loaded more than once. I am currently at a complete loss as to how I can troubleshoot this problem so, again, any insight on this will be greatly appreciated.

EDIT 2:
So this morning I gave it another go, tried changing my ‘Container Selector’ from .products to main.template-shop and suddenly I no longer have repeating products, so I think that fixed my latest and biggest problem. Now I’d just like to know if there is a way to prevent avia_pagination from being loaded for the shop pages in my child-theme, but I can live with having it hidden through CSS.

Best regards,
José

• This reply was modified 9 years ago by dZ_EB. Reason: found solution for issue from first edit

Hi Ismael!

I was having trouble opening that link, but I quickly found out it’s publishing settings had changed to scheduled and it was saying it had missed schedule, but I just had to change its status back to published and it got back to normal.

I saw your snippet did exactly what I wanted, and that you just had to change unset($trail[1]); to unset($trail[2]);.

Thank you very much for the help!

Best regards,
José

Ok so in the meantime I have been fiddling a bit more with the sliders and I think I’m realizing that I was getting the fullscreen slider’s correct behaviour, and I either have to give some ‘safe margins’ to the text in my images so it won’t get cut, or use the fullwidth easy slider instead, which will always keep my images’ proportion but won’t always fit so nicely on the screen, depending on resolution.

For now I’ll be using the fullwidth easy slider , at least until we can get new images done for it.

Hi again,

I have set up a ‘test copy’ of my site so there’s no problem with changing stuff there, and I’m providing a link to a post with the issue on the ‘Private Content’ of this reply (although the issue happens with all posts).

I tried adding that snippet you provided to my functions.php but it didn’t solve my issue (I suppose that is because it was just meant as an example and would need adjustment for my specific case).

• This reply was modified 9 years, 1 month ago by dZ_EB. Reason: forgot to mention testing of the suggested code snippet

Hi Andy,

Thanks for the support!

The solution you linked to does what I wanted, but only if I do that change directly in the main theme files.

I am using a child-theme for most of my customizations, and I tried doing that change in the child-theme (replicating that part of the theme’s folder structure on my child theme and duplicating the class-breadcrumb.php file into it) so it would be a bit more ‘update proof’, but I guess that logic of working with child-themes only works for template files and such, as it doesn’t seem to be working with this file.

Would it be possible to do this change in a more ‘child-theme friendly’ way?

Best regards,
José

Thank you very much for such a quick reply!

I hadn’t noticed the video’s link was in the footer, as I was under the impression that the facebook feed widget I have in the footer only linked to the facebook posts themselves.

I followed your suggestion of wrapping the facebook feed’s shortcode in that footer widget, with the snippet you gave me and the problem is solved.

Again, thank you very much.

I will now open another thread for the breadcrumb issue.