Coexistence with prepopulate module
| Project: | Vocabulary Permissions |
| Version: | 5.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
I just discovered that, depending on the module weights, users can create nodes with "restricted" vocabulary terms if they feed the terms through the prepopulate module. (The prepopulate module allows default form field values to be "pre-populated" by embedding them in the URL query string for the add-node page.)
However, I don't consider this to be a bug -- this is a feature that makes the vocabulary permissions module much more powerful.
First, I restricted a "categorization" vocabulary with vocabulary permissions. Then, I created customized links to the add-node page with the "categorization" term already in place. The user cannot see or edit the preloaded categorization term, but it is silently added to the node.
This allows me to keep track of where and how the new node was created. There is no other module that I can find that gives me this capability.
--- My feature request---
To get the behavior that I want, the vocabulary permissions module weight must be changed so it is HIGHER than the prepopulate module weight. I'm either looking for a less hackish way to toggle this behavior, or I want the current behavior to be documented so it doesn't unexpectedly change in the future.
#1
The vocabperms weighting caused problems and has been removed. Are you using the current version? Did you run update.php?
#2
My original feature request might not have been clear. By default, the vocabperms module does not have any weighting. I want it to have a higher weight (11 in my case) so it allows other modules (like prepopulate) to perform their configured behavior first.
Can you describe the problems that the weighting caused?
#3
There was a weighting fix recently that set the weight to -99. Making it a lower weight than taxonomy totally broke the module. I don't think that the module should be responsible to setting it's weight higher just so that the prepopulate module works. Most weight settings I've used are to make the module itself work, and the weights are used to get around certain ordering within core Drupal. I don't know of any modules setting weights just so that some other (previously unknown, obscure) contrib module will work. Why do you think that vocabperms should do this, rather than setting it yourself.