If i edit a node that has already been created, unique field thinks that the field already exists and wont let me submit the edit. I can change the field to something else, then it works, then change it back to the original value and it works. So, editing a node after it has been submitted thinks that the field is not unique. Please help.

John

Comments

arithmetric’s picture

arithmetric CreditAttribution: arithmetric commented
Status: Active » Postponed (maintainer needs more info)

I'm afraid that I can't reproduce this bug. What types of field are you using? Do they have multiple values?

apramakr’s picture

apramakr CreditAttribution: apramakr commented

I still see this issue.. When I create a new node with an existing title field, the message pops up saying the node already exists.
But if I try to edit an existing node, and I click on Save after editing it, it still pops the message out and does not let me re-save the node.

Any help is much appreciated!

apramakr’s picture

apramakr CreditAttribution: apramakr commented
Title: Works except for edit of node » unique field - Works except for edit of node
ChaosD’s picture

ChaosD CreditAttribution: ChaosD commented

i have the same issue. i use a combination of 2 fields that should be unique for a specific content type. if users ( no permission to override unique field settings, thats why i missed that problem as admin) try to edit their nodes, they appear as duplicate.

ericpalace’s picture

ericpalace CreditAttribution: ericpalace commented

Hi all,

I've the same issue. I'm using it in a content type with 2 required fields (title + text field), and the unique field is only the title ones.

I'm using also domains module. Is so strange because It happens only with an specific role, not with the others...

Please let me know if you need more info to reproduce it.

Any help will be so much appreciated.

Thanks in advance!!!

jsmm’s picture

jsmm CreditAttribution: jsmm commented

To make it short: when using this module, nodes cannot be edited!

abrujm’s picture

abrujm CreditAttribution: abrujm commented
Issue summary: View changes

We should add one more condition to check the entity id with the value in the database. This will resolve the issue of editing the content.

AstonVictor’s picture

AstonVictor CreditAttribution: AstonVictor as a volunteer and at DevBranch commented
Status: Postponed (maintainer needs more info) » 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