Closed (outdated)
Project:
Unique field
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
13 Apr 2012 at 03:36 UTC
Updated:
18 Apr 2024 at 09:01 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
rogeriodec commentedWell, I realized that I can avoid this by placing the field "author" in combination with other fields, since (in my case) the author of the node will always be a different user.
Yet the suggestion remains open.
Comment #2
gaëlgI could make it on rc1 by altering a bit the module with this logic in unique_field_match_value():
This allows me to do that in my custom module:
Comment #3
askibinski commentedHere is a new patch against 7.x.
Unlinke the code in previous comment, I don't rely on the domain_source module which is optional.
Comment #4
askibinski commentedMaking a better patch, last one had an empty module_exists and no settings options.
Comment #5
askibinski commentedHere is an improved patch with added options per content type for scoping.
Comment #6
askibinski commentedHmmm... testing this some more, the join does not actually seem to be executed. Weird, should work.
Comment #7
astonvictor commentedI'm closing it because the issue was created a long time ago without any further steps.
if you still need it then raise a new one.
thanks