coisosonthego

After changing some CDN settings, I confirm version 13.0 is also working again for me. Thanks!

I can confirm this is also happening on my site, with both Yoast and Yoast Premium plugins versions 12.9.1 and 13.0.

Your advice helped me realize another plug-in was loading a custom jQuery version. Loading the default version solved the issue.

Thanks for your help!

Hi chad

You can create links to categories using your catalog URL followed by /?categories=X or /?categories=X,Y, where X and Y are categories’ IDs. You can check the ID for a category by entering its edit screen or just by checking the URL when hovering a category in the plugin’s Categories page.

• This reply was modified 5 years, 10 months ago by coisosonthego.

I’m currently on version 4.4.6, just updated it the other day.

Thanks for your reply. Indeed my client’s case may be somewhat specific, we have some products that are quite similar except for one or two features (like power supply voltage, number of outputs etc.), and most of the customer questions we reply to by e-mail involve this.
That’s why I believe it would be great to make it visually clear to the user what exactly is different between products “SMD-02” and “SMD-02E”, for example. I think that is precisely why our customers would compare our products.

(what if you are comparing four product and they all have different values for a field?). In that case, you could say everything should be highlighted (including categories and sub-categories, etc.) because they’ll have different values for each product as well. And that would detract from the UI

In these mockups you can see how the comparison between two very similar products and four very different ones would work for us. The field highlighting is subtle and I don’t think it would be troublesome even if all the fields in all products in a comparison were to be highlighted.

Thanks for taking the time to look into this topic and for clarifying the usage of the Field_Display_Comparison function.

I understand if you feel this feature would really serve a small subset of the plugin’s users.

Thanks for confirming.

Thanks! I hadn’t noticed they had specific classes.

As per my client’s request, the staging site is password-protected. Is a screenshot enough context? https://i.imgur.com/ZBKfrkB.png

I’m sure this is the plugin I use ??
I’ll do some more testing next week and will let you know.

Hi Scott

I see… It’s just that those issues disappeared when I removed the widget from my page. Maybe Facebook is doing something behind the scenes?

Hi Scott

The issue of using images larger than needed has indeed been fixed in 1.9, but PageSpeed is still complaining about items requested by the plugin:

Compressing https://connect.facebook.net/pt_BR/sdk.js could save 118.6KiB (69% reduction).
Compressing https://staticxx.facebook.com/connect/xd_arbiter.php?version=42 could save 21.5KiB (65% reduction).
Compressing https://staticxx.facebook.com/connect/xd_arbiter.php?version=42 could save 21.5KiB (65% reduction).

Leverage browser caching for the following cacheable resources:
    https://connect.facebook.net/pt_BR/sdk.js (20 minutes)

I’m not sure these could be in your scope to fix, but thanks for your continued work on the plugin!

Sorry for taking so long to reply, but that was exactly what I needed. Thanks, Barry!

Thanks! The issue was caused because masonry no longer includes the imagesLoaded function. So I loaded the imagesLoaded script separately by adding it in my functions.php file.

I’ve enabled WpDiscuz, you can see it in action here.