If a user tries to submit a new node, that violates the unique 'constraint' (configured with Unique field), he gets rejected with a message that a field should be unique.

It would be great if that (default) behavior could be altered so that the module would create new revision on the node, that is already in the database.

CommentFileSizeAuthor
#1 on_duplicate_create_revision-7.x-1.x-0.patch2.14 KBfuzzy

Comments

fuzzy’s picture

fuzzy commented
Status: Active » Needs review
StatusFileSize
new on_duplicate_create_revision-7.x-1.x-0.patch2.14 KB

I just created my first patch (hope it's OK).

This patch should implement the functionality described in the post above.

astonvictor’s picture

astonvictor commented
Issue summary: View changes
Status: Needs review » Closed (outdated)

I'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