Closed (fixed)
Project:
Unique Field AJAX
Version:
2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
10 Nov 2017 at 07:29 UTC
Updated:
5 Oct 2021 at 18:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
drholera commentedAnd 1 more patch with better unique checks.
Comment #3
bloomt commentedHow hard would it be to patch it for the date field as well?
Comment #4
drholera commentedI've found a small bug in the previous patch. Here is the new one.
About date field. I hope I'll have enough time to check it this or next week.
Comment #5
drholera commentedComment #6
drholera commentedThe last one was kind of broken. I've added fixes.
Comment #7
rgristroph commentedI've read through this patch, and we've been using it for a month or so, and it seems to work fine.
Comment #8
duckduckgoose commentedA slight modification to the last patch to fix a bug that was sometimes preventing edits to the field config itself after marking the field unique.
Comment #9
Nitish k commentedI tried this patch, worked for number field but the content type in which I applied for unique field I am not able to add multiple paragraphs.
Comment #10
dqdTremendous work done here already! Heads up! But please let's file patches against latest dev to stack up the features correctly for a next release candidate.
This sounds suspicious. Set it to needs work. We need more tests here. Can #9 provide more info? Did you used the latest patch of #8 and did you tested it with a patch version from before also?
Comment #11
andyd328The patch in #8 is working for me with a single entry integer field used against 8.x-1.2.
My feeling is that the patch, despite its small size, contains too many unrelated changes. To get my use case working the only change I needed to make was adding 'integer' to the field type list in unique_field_ajax_form_field_config_edit_form_alter().
I haven't tested the patch beyond my immediate needs, but perhaps if the code quality changes are addressed separately it will be easier to pull apart how patch #8 caused issue #9 - if it did.
Comment #12
arnaldopThis is a great patch and is working for me just fine.
However, the numeric field has arrow controls to increment and decrement the number.
If the users uses those controls, the JavaScript
keyupevent does not fire.I tweaked it locally to use the
changeevent, which fires whenever there is a change to the field.Does anyone have any thoughts or recommendations on this?
Thanks for the great module and a great patch!
Comment #13
arnaldopHere's the patched patch, with the change from the
keyupevent to thechangeevent.I also changed the JavaScript file name to better reflect the contents.
Comment #14
dqd@#13 can you please
provide a interdiff(done) between #13 and #8 ? ... Thanks for keeping up this work!Comment #15
dqdNever mind, done for those who want a quick review ...
Comment #16
joelpittetComment #17
abhaypai commentedWorks as expected.
Comment #19
3liWill work on adding this to the 2.x branch
Comment #21
3liComment #22
3liComment #24
3li