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.
It would be possible to integrate with the Domain Access module?
For example, nodes that can not have duplicated titles in the same sub-domain, but can be included again in another.
1) Subdomain x: title "hello" (unique)
2) Subdomain y: title "hello" (unique)
Comment | File | Size | Author |
---|---|---|---|
#5 | unique-field-domain-access-1530728-5.patch | 3.22 KB | askibinski |
#3 | unique-field-domain-access-1530728-3.patch | 1.37 KB | askibinski |
Comments
Comment #1
rogeriodec CreditAttribution: 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 CreditAttribution: askibinski at ezCompany 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 CreditAttribution: askibinski at ezCompany commentedMaking a better patch, last one had an empty module_exists and no settings options.
Comment #5
askibinski CreditAttribution: askibinski at ezCompany commentedHere is an improved patch with added options per content type for scoping.
Comment #6
askibinski CreditAttribution: askibinski at iO commentedHmmm... testing this some more, the join does not actually seem to be executed. Weird, should work.
Comment #7
AstonVictor CreditAttribution: AstonVictor as a volunteer and at DevBranch 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