Details
Assignee
UnassignedUnassignedReporter
lady.oscar.ao3lady.oscar.ao3Roadmap
TagsWorksPriority
MediumComponents
BackEndFrontEndDifficulty
MediumMilestone
Internal 0.9Google Code Issue ID
3945
Details
Details
Assignee
Unassigned
UnassignedReporter
lady.oscar.ao3
lady.oscar.ao3Roadmap
Tags
Works
Priority
Components
BackEnd
FrontEnd
Difficulty
Medium
Milestone
Internal 0.9
Google Code Issue ID
3945
Sentry
Sentry
Sentry
Created March 23, 2014 at 5:48 PM
Updated March 15, 2021 at 5:22 AM
Originally reported on Google Code with ID 3945
What archive revision are you testing on?
v0.9.14.5
What steps will reproduce the problem?
Post a work with some tags
Edit the work and change the order of some or all of the tags
Update, with or without previewing first
What is the expected output?
Expect to see your tag order changes.
What do you see instead?
Instead, the tags are in their original order.
Workaround
Remove all tags, update the work, edit again, then re-add in the order you want.
Notes
This bug exists because tags (taggings) are not given a particular assigned order, as they would be if we used acts_as_list (which we use for ordering chapters, for example). Instead, tags are listed on the work in the same order they exist in and are retrieved from the database. Since reordering doesn’t destroy and recreate the taggings, this order doesn’t change.
We have not yet decided on the proper approach to fix this. Two possible solutions:
Destroy and recreate all taggings when reordering. This might be somewhat inefficient (e.g. it might lead to works' filters being unnecessarily recalculated and the work being unnecessarily reindexed).
Use acts_as_list to make the order explicit. This would require a migration of the taggings table, and we’d also need to determine whether tags should be ordered as one big list, or with each type (fandom, relationship, etc) as its own list (in case we want to change how tags are displayed in the blurb, e.g. make characters come before relationships).