I was planning on deleting the records, but they are being referenced from the cmsPropertyData table, and i am not to keen on just deleting from multiple tables.
The only reason is would have deleted out of some tables and not others is if there was a crash during the delete process. The log table should cover anything like that.
cmsMember vs. umbracoNode
Hi there
In the system i work on, some members have been created, then deleted, then created again (with new ID)
The cmsMember table reflect the current users without any problems, and when i browser the members within the Umbraco backend, everything is fine.
But unfortunatly the MemberPicker for some obscure reason, does not look into cmsMember, but does this:
select id, text from umbracoNode where nodeObjectType = '39EB0F98-B348-42A1-8662-E7EB18487560' order by text
Why ?
In the umbracoNode, the deleted members are still present, so when i get the dropdown list i get something like this:
User 1
User 1
User 1
User 2
User 3
User 3
Many of the members are duplicated, which is quite annoing, because the members have been deleted.
Do i really have to create my own member picker to fix this problem ?
Find the orphan records from the umbracoNode table and delete those. Please log this issue on Codeplex to get it resolved asap.
TIA,
/Dirk
Hello Dirk
Thanks for the reply.
I was planning on deleting the records, but they are being referenced from the cmsPropertyData table, and i am not to keen on just deleting from multiple tables.
I'll log it as an issue in Codeplex.
How did you delete them, the API cleans up after itself fairly well.
The reason they are in the umbracoNode table is because a Member is a CMSNode, like a Document, DocumentType, Media, MediaType, etc.
Hi Slace
It is some time ago, but i am pretty sure, it was done via the Umbraco backend.
Or at least i can't remember doing it directly in the database,.
Do you have any clue, why the same data is in both the cmsMember table and also in the umbracoNode table. 1 place should be enough.
I'll look into the source code, and delete the things still in the database by hand.
The records are not deleted.
Thanks Slace for the tip, it reminded me i did have the source code, so i could see how the system did it.
The only reason is would have deleted out of some tables and not others is if there was a crash during the delete process. The log table should cover anything like that.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.