'This content has been modified by another user, changes cannot be saved.'
lefnire - September 29, 2008 - 19:10
| Project: | Addnode |
| Version: | 5.x-1.2 |
| Component: | User interface |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
While attempting to add an inline referenced node using nodeadd, on a few nodes I get this message:
This content has been modified by another user, changes cannot be saved.
I haven't quite pinpointed the issue, so I'm brain-dumping here maybe in case you've encountered this problem before and have advice. Otherwise, I'll re-post if I pinpoint it.
Some hints... it happens on some nodeprofile-enabled nodes, but not all. Also, it seems to happen on nodes where I'd previously defined the content-type without addnode, created the node, added an addnode field to the content type, edited the node to add a nodereference, and clicked submit.
#1
I think it's an incompatibility with nodeprofile and addnode. When I add a nodereference field of widget-type "select" to a node-profile content type, then everything works fine. If the widget-type is "addnode", then
1) when the user either selects -or- inline-creates a referenced node, that node isn't then displayed on the user's node-profile
2) when the user goes back to edit, makes any modifications, he gets that
This content has been modified by another user, changes cannot be saved.error.However, when I manually create a node-profile node (aka, outside of the user-registration process), and add a reference using addnode, everything works out fine. So it seems addnode is either having trouble with node-profile, or with being connected involved with the registration process.
#2
Looks like it's an issue with overlapping elements between subforms on nodeprofile-enabled nodes and addnode subforms. The only way to fix this overlapping issue is by setting #data_separation to TRUE, but this might be impossible as per 201804. See 316068 for the full details.
The small of it is that addnode is incompatible with nodeprofile, and likely to always be that way.