Create new vocabuary for gallery image. Then edit gallery options at admin/settings/node_gallery and check Fields: Taxonomy checkbox.
Then create a gallery, and add some images and fill their taxonomy fields. Now if sort images in "manage images" tab - everything is okey. But if sort images in "Sort images" tab every taxonomy item will be deleted.

Comments

dddave’s picture

Confirmed. Using the "Sort images" tab kills the taxonomy. Using the "Manage Images" tab to sort images works without a problem.

I propose that we get rid of the "Sort..." tab unless it is an easy fix. This tab seems redundant to me because I can do the sorting via the managing tabs. Are there some permission issues attached? But I don't see a special "sort" permission...

Btw: If we already had the new priority "major" this would be a use case.

dbeall’s picture

The original idea for having the sort page was to have 'all' the images from the gallery for sorting purposes.. because the manage images page has a pager with limited images on each manage page.

The problem was sorting an image from page 3 of manage images to the first position was not possible without extra moves.
Also the extra space taken by fields and other possible items can make each image space large on the manage page.
It was also talked about-- having smaller thumbs on the sort page. (NG3 has it using a imagecache preset) The fluid grid/js sorting in NG3 is neat, looks nothing like the manage page and degrades to tabledrag.
The sort page is suppose to display a 'limited' number of functions to make it load faster and easier to sort the entire gallery.

EDIT: guessing that the sort page is messing up because it isn't loading all the related node stuff for each image... ?

This is something we better test on NG3

dddave’s picture

Ok, that is something I could have thought of as purpose for the "sort" tab. So unless this is fixed we need a big red sticker telling users that this happens.

dbeall’s picture

I was hunting for the thread where the sort page came to light and was added, but couldn't find it.

It was something Kmonty had in mind long before it was added..
Justintime or scroogie can probably figure it out when they get back in the mix. Justintime had other work that needed to be done, but he said he would be back in a few weeks..

dddave’s picture

Priority: Normal » Major
dddave’s picture

Version: 6.x-2.0-beta2 » 6.x-2.x-dev
Status: Active » Fixed

This seems to be fixed somehow...

Cannot reproduce anymore.

@all:
Please confirm.

justintime’s picture

Although I never got the chance to confirm that it was broken before, I can verify it isn't broken in 2.x-dev now.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.