When using this module with the Taxonomy module, it loads in all the rows from the chosen taxonomy vocabulary in the order that is specified in the Taxonomy weightings, but when you move it from available to selected and back, the rows get added to the bottom instead of returning to their original position.

Is there anyway this module could be altered so that the rows get returned to their original taxonomy weighted position when moved back?

CommentFileSizeAuthor
#5 866658_repopulate.patch2.33 KBmrharolda

Comments

Jarada’s picture

Jarada commented

I am of course referring to Content Taxonomy and not Taxonomy... sorry for any confusion caused...

attheshow’s picture

attheshow commented
Status: Active » Closed (won't fix)

This is going to be some pretty complex javascript to write, for very little benefit to my mind. Patches are welcome though!

askibinski’s picture

askibinski commented
Title: Return to Available Options based on Taxonomy Weight » Return item to Available Options at same position
Version: 6.x-1.7 » 7.x-1.x-dev
Status: Closed (won't fix) » Active

Updated this with a better title and also for 7.x version.

This is actually quite important with long lists, people find it very confusing when items seem to dissapear when you set them back to available.

I agree the javascript could be complex (I'll ask an expert) but it would really polish this module.

mrharolda’s picture

mrharolda commented

Sub

mrharolda’s picture

mrharolda commented
StatusFileSize
new 866658_repopulate.patch2.33 KB

I've hacked a small piece of javascript to repopulate the unselected box with the original values, except those present in the selected box. Note that I'm no javascript/jQuery developer, so it might be a really ugly hack, but it seems to work fine here!

Just think of it as a 'proof of concept' ;)

mparker17’s picture

mparker17
he/him
Primary language English
Location UTC-5
commented
Issue summary: View changes
Status: Active » Postponed (maintainer needs more info)

multiselect-7.x-1.x is no longer supported, because Drupal 7 is no longer supported.

Can you confirm if this is still an issue in multiselect-2.0.0-beta4?

I'm going to mark this issue as "Postponed (maintainer needs more info)"... but when you answer, please change it back to "Active". If there is no reply in ~6 months, then I will mark this issue as "Closed (outdated)". Thank you in advance for your understanding and patience as I try to keep this module's issue queue clear.