Beta: Weight, Dimensions, Attributs

Beta
#1

Hi!

I am noticing that Weight, Dimensions and Attributes are combined in the Product Additional Information element.

I think that to the minimum, Weight and Dimensions should be in their own element (which are the actual additional information), and Product Attributes as separate element and/or Dynamic content shortcode.

Even better, Weight and Height values could also be called separately to allow more design possibilities.

Also, I understand that calling each attribute+s values by its own ID could be problematic for layouts, but I’d still like to have that freedom. :slight_smile:

1 Like
#2

Hi @Misho,

Thanks for pointing this out! We realize there are still a few things to be desired on the WC front, so keep them coming as you think of them. This one isn’t as easy to work out as I’d hoped after looking into it. Regretfully at the moment we’ve got to leave the whole Attributes output combined in the Product Additional Information element. What you’re seeing there is just the native WC markup for the product attributes tab.

The conditions are based off the has_attributes WC method available on their Product class. They don’t have methods to directly check for height/weight, but there is a way to enumerate attributes. We’ve discussed exposing them all in the Looper/Consumer pattern. That’s a bit of work to do, and beforehand we want to have some better table styling available in the builders first so the example elements will work nicely. I’m going to move this to our WC overflow list so we can come back to it.

1 Like
#3

Hi @alexander

I’d like to place one more wishlist item here. :slight_smile:
You guys were most likely discussed this internally. This is probably exactly what you wrote in the comment above.

WooCommerce Attributes Looper with Conditions

Imagine a variable product that has sizes and colors.

Sizes would by default end up in the dropdown menu.

Far better UX is if the sizes are shown as buttons, even if they are not available, like on this mockup:

attr

In this example 5 sizes are possible, but the L size is currently not available. That is my point here: I imagine a condition that shows a different button in case the Attribute is not added.

Similar could be done with colors and any other variation.

Thanks!

1 Like
#4

Hi @Misho,

Yes! We’ve discussed doing something like this. There are several WooCommerce looper types that would be helpful to add, especially attributes. It’s on the radar, but hasn’t been prioritized for an update yet.

So we’re about to push out the ACF Repeater beta. The way you access those would be via Dynamic Content (and a new looper type called Dynamic Content). Once you’ve played around with it, I’m curious on your thoughts on if the WooCommerce loopers should be handled in a similar way (Dynamic Content) or if you’d expect something more first class like a dedicated looper type.

2 Likes
#5

Hi @alexander,

Just to continue on the topic for some future reference. :slight_smile:

I have now discovered that ACF Pro doesn’t have an option to add fields to WooCommerce Attributes natively. That would allow a future Attributes looper to pick up something like an image attached to a particular attribute. For example, we could have a bag that comes in several strap designs:

image

Those designs (attributes) need to have uploaded pattern images associated to them.

There is a way to add ACF fields to Attributes though, with a custom function.

It would be fantastic if Pro could go around some of those hurdles and allow getting such results for product variations and attributes, even if that means supporting Custom functions. :slight_smile:

#6

We definitely want to be able to looper over variations and product attributes but at this point any big WooCommerce additions like that are back burner while we work on responsive styling. Some great ideas here for sure though.

3 Likes