Download & Extend

Allowing users to bypass/ignore unique field constraints

Project:Unique field
Version:6.x-1.1
Component:Code
Category:feature request
Priority:normal
Assigned:Unassigned
Status:closed (fixed)

Issue Summary

I'm dig'n the use of the unique field contrib. I'm using it for one of my groups to ensure that an author can only create one group. However what I'm finding is that in some cases there is a need for user #1 to create multiple groups and I'm not able to get around the unique field setting.

Would any of the following (or something similar) be possible in a future release?

a) Control unique field setting by role?

b) Allow user #1 to override unique setting at time of content creation. The reason I word it this way is I would want user #1 to have to make the decision to allow duplicate values when creating content instead of always allowing user #1 to make duplicates.

Comments

#1

Title:Option to ignore unique validation by role, user, etc.» Allowing users to bypass/ignore unique field constraints
Component:Miscellaneous» Code
Status:active» needs work

I think the easiest way to implement this would be to add an access permission that allows users to bypass/ignore the unique field constraints when they submit a node and get the error message back.

Therefore the module still would provide a warning about the duplicate value, but also permits authorized users to decide for the particular case whether a duplicate value is appropriate.

I can't promise to make this change a priority. If you or anyone else would like to sponsor development of this feature, please contact me.

#2

Status:needs work» fixed

This work was sponsored by J-Seed Ventures, Inc. (http://www.j-seed.com) and is included in the latest release.

There is a new permission that grants users the ability to bypass the restriction and submit the node. If you are using the first user (uid 1), then you will always get this choice even if you don't have the specific permission.

#3

That is great news! Thanks for putting out a very useful module!

#4

Status:fixed» closed (fixed)

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

nobody click here