Closed (won't fix)
Project:
Views Bulk Operations (VBO)
Version:
6.x-1.10-beta2
Component:
Actions
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
19 Aug 2010 at 14:45 UTC
Updated:
8 Jun 2013 at 15:36 UTC
Steps to reproduce:
1. Create an action and select "Modify node taxonomy terms" as the triggered action
2. Under "action to take," select "Delete selected terms"
3. Pick at least one taxonomy term
4. Save the triggered action
5. Click on the triggered action title to modify it
6. Note that the "action to take" is now set to "Add the selected terms"
Currently installed:
- Drupal 6.19 (though it happened under 6.17 too)
- Rules 1.2
- Views 2.11
- Views Bulk Operations (VBO) 1.9
Installed taxonomy modules, though I don't think these affect this, worth noting:
- Taxonomy Access Control 1.2
- Taxonomy Manager 2.2
- Taxonomy Role 1.0b1
Comments
Comment #1
klausiSounds like a VBO problem.
Comment #2
rootworkIf there's any information I can provide that would help us identify the problem, I'd be happy to do so -- this is a really vexing issue for me.
Comment #3
infojunkiePlease try the 6.x-1.x-dev version. Does it preserve the action?
Comment #4
rootworkHmm. I tried the dev version and the newly-released 1.10-beta. It now does seem to preserve the action, but now the terms don't actually seem to be getting removed. I'll have to look into this further.
Is anyone else experiencing that taxonomy terms are not being deleted upon a triggered rule?
Comment #5
infojunkie@rootwork: can you try accessing this action through the stock VBO (admin/content/node2)? Does the action work in that case?
Comment #6
rootworkAh, great test! Yes, that does seem to work. It only fails when it's happening via actions.
I've updated a few modules, so here's what I'm at now (in which it works under the VBO page but fails as an action):
- Drupal 6.19
- Rules 1.3
- Views 2.11
- Views Bulk Operations (VBO) 1.10b2
Comment #7
rootworkUpdating title to reflect issue.
Comment #8
bojanz commentedVBO for D6 is in maintenance mode and will receive only fixes contributed and tested by the community.
Reopen with a patch (if this issue is even valid in latest 6.x-1.x-dev).