sorting problem saving sortable multi select field with wp pages:

[w3b-beweb]

Debug info:

• Redux version: the very last 😄 (3.3.9.10)
• Wordpress 4.0.1
• Redux not in dev_mode
• Redux embedded in my theme
• no js or php warnings/errors

In my redux config I've a sortable multi-select field, filled up with Wordpress pages; here's the code:

array(
    'id'            => 'oweb_opts_home_feat_pages_1',
    'type'          => 'select',
    'multi'         => true,
    'sortable'      => true,
    'title'         => 'Pages',
    'subtitle'      => 'select which page(s) you want to feature on homepage',
    'data'          => 'pages',
    'required'      => array('oweb_opts_home_feat_1_type','equals','0'),
    'placeholder'   => 'Select one or more'
),

All seems to work well (the "required" condition, the multiselect and UI reorder features etc) BUT the ids of selected elements are always saved in the same order, regardless of the order selected via UI. Here is a dump of the saved option (the same every time) with 3 pages selected:

'oweb_opts_home_feat_pages_1' => array (3)
    string (4) "1565"
    string (4) "1550"
    string (4) "1526"

they are always sorted in chronological reverse order, no matter what I do during selection. It seems very odd to me there's a bug like this, so am I missing something obvious (not for me!)?

[kprovance]

It looks like - when that feature was added, the sorting (before my time), no one bothered to write the code in the javascript that would reorder the selected option items to match what was on the page. So yeah, the resorted order won't save properly.

That's going to be a bit of an undertaking to get working properly. I won't have the time to do it for the foreseeable future. You're free to add the functionality and submit a pull request if you like, otherwise, I'll get to it when I can. No ETA on that.

[kprovance]

Oh, you know what? I was completely wrong! Ha! It's a glitch in the vendor library we use for sortability. I couldn't believe this kind of a bug existed for so long. It turns out the sortable library was appending the necessary order...just incorrectly. The fix is simple. I will push an update later today. Sorry about the mis-diagnosis. Good thing I listen to that nagging feeling in my gut, eh? ;-)

[kprovance]

Fixed in 3.3.9.11 :)

[w3b-beweb]

Thanks Kevin (and kevin's gut!) for your quick support, it works as expected now.