Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
A client requested the ability to change taxonomy terms during the moderation process. I've added that in the attached patch. This patch should work in situations without taxonomy.module is not enabled. It should work for structured taxonomies - free tags may be another story.
Enjoy!
Comment | File | Size | Author |
---|---|---|---|
#3 | Modr8 Settings for CCK and Taxonomy | 57.74 KB | quicksketch |
#3 | Setting taxonomy and fields during moderation | 59.79 KB | quicksketch |
#3 | modr8_taxonomy_cck.patch | 6.46 KB | quicksketch |
#1 | moderate_taxonomy.patch | 1.73 KB | quicksketch |
modr8.moderate_taxonomy.patch | 2.09 KB | mfredrickson |
Comments
Comment #1
quicksketchThanks Mark, we use this on many of our sites for re-categorizing photos that have been uploaded into the wrong gallery (a taxonomy vocabulary). Here's a reroll to the latest 5.x and a few spacing fixes. I'm interested in getting this added as part of modr8 directly, but I think we'll need a configuration form to adjust what vocabularies should be shown, or just be able to enable/disable the feature site-wide rather than having it always there if taxonomies are available.
Comment #2
sirkitree CreditAttribution: sirkitree commented+1
Comment #3
quicksketchI don't normally expand an issue into two like this, but the changes are so close to each other the submitted patches would cause conflicts with each other. This takes the taxonomy patch by mfredrickson and adds configuration so you can enable it for only specific vocabularies rather than using all of them. I tested this with free-tagging and normal vocabularies and it works both ways.
The big expansion is that this patch now also supports CCK fields. After configuring which CCK fields you'd like to add to the moderation form, you can modify any CCK value during moderation. The use-case I experienced for this was using node reference fields. Sometime the end-user will node reference content to an incorrect parent, though the item should be approved.
I tested the CCK fields with: Node reference, text, number, fivestar, link, address, date, and even image. All of them work fine as long as you don't use Ajaxy-like buttons provided by imagefield and link modules.
Comment #4
sirkitree CreditAttribution: sirkitree commentedsweet, very nice patch. this is highly useful.
Comment #5
pwolanin CreditAttribution: pwolanin commentedHmm, interesting - it would be nice if modr8 could be restructured to support these sorts of added operations without weighing down the core module. Any thoughts?
Comment #6
giorgio79 CreditAttribution: giorgio79 commentedGreat stuff! Is this forgotten? :)
Comment #7
pwolanin CreditAttribution: pwolanin commentedYeah, fell off the radar - care to test and maybe roll a patch for 6x. too?
Comment #8
digi24 CreditAttribution: digi24 commentedIt would be really great to see a patch for Drupal 6. I tried to port #3, but I am having trouble to get the subforms to be displayed. (I am aware that the form_alter commands changed between D5 and D6)
Comment #9
Andrew Gorokhovets CreditAttribution: Andrew Gorokhovets commented+1