SOLVED: Variation Swatches Label wrong order

Bugs
1

If I use Variation Swatches the “Labels” are in a wrong order,
I have sizes with attribute variation size from 52 to 60 cm.
But Bricks Builder Element Add to Cart Variation Swatches show the Buttons (label) in the wrong order the latest sizes added in the product are in the bottom of the list
[0] => 55-cm
[1] => 56-cm
[2] => 57-cm
[3] => 58-cm
[4] => 59-cm
[5] => 60-cm
[6] => 54-cm
[7] => 52-cm

If I use the old plugin for swatches " WCBoost - Variation Swatches" the order are ok.
52-cm
54-cm
55-cm
56-cm
57-cm
58-cm
59-cm
60-cm

Looks like the plugin is ordering by “name” before adding it to the page.
$attribute_orderby = ! empty( $taxonomy->attribute_orderby ) ? $taxonomy->attribute_orderby : 'name';

But Bricks Builder element is not ordering it showing the latest added to the product in the bottom position and this is not right.

Screenshot-2025-09-13-at-17.50.58
Screenshot-2025-09-13-at-17.50.58671×606 78.1 KB

2 Likes
2

Hi Sandro,
Thanks so much for your report!

Have you tried changing the attribute order to “Name (numeric)” in WooCommerce » Products » Attribute settings?

image
image2586×1190 216 KB

Best regards,
timmse

3

Thanks for the answer but nothing change if I modify the sort order in the attribute page. :pensive:

Link of a video:
https://www.dropbox.com/scl/fi/zdxu3hifb8vyjsugyivut/bricks-variation-swatches.mp4?rlkey=byk78lwbaqv01mdxz0403bwn3&st=9mcslqis&dl=0

4

I see and I’m able to replicate the issue. We’ll update this thread once it’s fixed.

2 Likes
5

Still not working with Bricks Builder 2.1 Beta… :pensive:

Please please fix this bug before the final release, unfortunately, I have customers who are annoyed by the messed-up order.
:pray:

6

Same issue here. I’m going to use a plugin as a temporary workaround. Hoping this gets fixed soon!

7

Same problem. From my research it seems that Bricks label swatches prioritize variant IDs, so newly added variations are at the end of the list, even if the attribute order is manual.

8

Looking at the code of the element and with help from AI I am able to sort (Label, in my case).

I added a line in the theme folder:
includes/woocommerce/elements/product-add-to-cart.php
Line 1424 after the $options (Bricks Builder beta 2.1)

$options   = $args['options'];

// Insert this usort line and use the echo just to check
usort($options, function($a, $b) {    return intval($a) - intval($b);});
echo '<pre>';print_r($options);echo '</pre>';

It is working but I am not sure it affects the following code.
Maybe someone could check it as a temporary fix.

9

@timmse +1 same issue.
Why don’t you fix many of the bugs in the new versions? What kind of approach is this? There are lots of issues, but instead of solving them, you keep releasing new features while existing bugs are ignored and left unresolved. This mindset needs to change. Yes, new features are nice, but without addressing the existing problems, they mean nothing. Honestly, I’m really exhausted.

10

// temp solution : add to functions.php

add_filter('woocommerce_dropdown_variation_attribute_options_args', function($args){
    $attr = $args['attribute'] ?? '';
    if (! $attr || strpos($attr, 'pa_') !== 0 || empty($args['options'])) return $args;

    $terms = get_terms([
        'taxonomy'   => $attr,
        'hide_empty' => false,
        'orderby'    => 'menu_order',
        'order'      => 'ASC',
    ]);
    if (is_wp_error($terms)) return $args;

    $order_slugs      = wp_list_pluck($terms, 'slug');
    $current_selection = array_map('strval', (array)$args['options']);
    $args['options']   = array_values(array_intersect($order_slugs, $current_selection));
    return $args;
}, 9999);
3 Likes
11

Thank you @serdar, perfect! :heart_eyes: :star_struck: :heart_eyes:

12

A glance at the changelogs clearly shows that every single version contains far more bug fixes and improvements than new features :eyes: The last release was a beta version intended for testing new features—but even this beta contains far more fixes and improvements than new features.

This report was confirmed a week before release, and unfortunately the fix didn’t make it into the beta, just like others that will be fixed either in the stable version or in one of the next versions.

Thanks for your interim fix :fist:

1 Like
13

The same problem, still waiting for an official fix. Could you please reply here after fixing it?

14

Yep, we’ll reply to the thread and change the title from WIP (work in progress) to solved when the time comes :v:

15

I have installed Bricks Builder 2.2, but the problem is still there :unamused_face:
This bug was reported in september 2025.

Screenshot 2026-02-12 at 11.09.41
Screenshot 2026-02-12 at 11.09.41710×603 44.7 KB

16

I honestly don’t understand why such a simple issue isn’t being fixed quickly. How long are we supposed to wait? When will the WooCommerce side finally get proper attention? Isn’t it embarrassing to leave something like this unresolved? I can fix it with 3–4 lines of code, but the entire Bricks team hasn’t been able to solve this for several releases?

1 Like
17

~Half a Year Almost, Really! :eyes:

1 Like
18

We fixed this issue in Bricks 2.3, now available as a one-click update in your WordPress Dashboard.

Please read the changelog entry before updating, and let us know if you continue to experience issues.