Closed (outdated)
Project:
Unique field
Version:
7.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
27 Nov 2009 at 17:14 UTC
Updated:
18 Apr 2024 at 09:01 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
Platinum commentedComment #2
ChaosD commentedsubscribed
would it also be possible to summarize the messages or completely customize it with tokens? i.e. if i have 3 fields to be checked for uniqueness and 2 are duplicates it says :
Hint: A similar post has already been created at nodetitle[link]
Click here[link-bypass] to post anyways
instead of:
Comment #3
giorgio79 commented+1
Comment #4
tiw commentedAny solution to create customized error messages?
Thanks,
Comment #5
pbeakley commentedSubscribing! Although for now I think I'm going to need to use Rules to make this happen.
Comment #6
GroovyFX-Matts commentedSubscribing
Comment #7
giorgio79 commentedThis could be taken care of by integrating with Rules #859714: Rules Integration
Comment #8
benmalen commentedSubscribing. This is exactly what I was going to request, but for 7.x
Comment #9
DickSwart commentedSubscribing - Any solution to create customized error messages?
Thanks
Comment #10
adamgerthel commented+1 for this. I need it for D6
Comment #11
wjaspers commentedWorking on a 7.x patch at this moment. Will backport once finished.
Comment #12
wjaspers commentedThis introduces error handling on a per-content-type basis. The message of choice if the scope is across "ALL" content will be the error message that exists for the content (type) currently being edited. More work needed to make it use the custom message for different scopes.
Comment #13
dreftymac commentedPROBLEM:
CCK unique_field module does not support configurable actions when a field duplication rule is violated.
The only action available is the display of a standard error message.
The error message is always the same regardless of the duplication context or node type.
WORKAROUND-001:
Use the stringoverrides module to change the default error message.
(See http://drupal.org/project/stringoverrides)
### ********************
### original
The @label field requires a unique value, and the specified value is already used.
### ********************
### replacement
The @label specified already exists in the database, Please click here for more details.
BENEFITS-001:
Using this method, it is possible to get (minimal) Rules integration.
Rules integration can be done by triggering a rule whenever the user clicks on the link in the custom error message.
Just make a custom rule to do whatever action you want.
(See http://drupal.org/project/pathrules)
PITFALLS-001:
This only provides a way to change from one singular fixed error message to another.
This still does not provide custom error messages for each duplication context.
This does not provide robust legitimate Rules integration.
Comment #14
wjaspers commentedString overrides are most often intended for internationalization and localization purposes. As easy as it would be to use them, I don't think its very practical, and adds maintenance for site owners.
My patch didn't introduce any rules integration, so I have no idea where you're getting that part from.
Comment #15
jordanmagnuson commentedBeen using #12 patch on a production site, and it seems to work well. Any chance of getting this committed?
Comment #16
giorgio79 commentedAnother solution http://drupal.org/project/field_validation
Comment #17
delacosta456 commented@giorgio79 most of people have tried field_validation with the "Unique value on multiple field" option and it doesn't work most of the time. That is we we refer to this module
Comment #18
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