member picker showing legacy data

Press Ctrl / CMD + C to copy this to your clipboard.

Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at

James Crane 34 posts 80 karma points

Mar 30, 2011 @ 02:51

0

Member picker showing legacy data

HI,

v.4.5.2

I'm using the member pick data type, but there's errant members there (some repeated several times). I did initially import members programmatically and have since deleted them - however these items persist.

I have checked tbl cmsMember and tbl cmsMember2MemberGroup and there is no reference to them. In the front end membership section the members are not there either(obvious but I thought I'd mention it). I have used the Member API to list the members present and they do appear here.

I have repuplished the site and deleted umbraco.config, but to no avail. This feels like a caching issue but I'm not really sure where to turn next. I guess I could just write my own datatype but I'd rather solve this.

Thanks

JC

Copy Link
Craig Taylor 29 posts 69 karma points

Mar 30, 2011 @ 17:01

0

Have you tried recycling the application pool or resetting IIS?

-Craig

Copy Link
James Crane 34 posts 80 karma points

Mar 30, 2011 @ 21:53

0

Hi Matt,

Thanks for the suggestion, I have already tried this. These items persistence is proving very aggressive!

Frustrating :-)

JC

Copy Link
Jan Skovgaard 11280 posts 23678 karma points MVP 11x admin c-trib

Mar 30, 2011 @ 22:32

0

Hi James

How did you delte the nodes? Did you do it through the backoffice or through some custom code?

/Jan

Copy Link

James Crane 34 posts 80 karma points

Apr 01, 2011 @ 18:31

Hi Jan,

Sorry for the delay, I've been travelling.

The nodes where deleted through custom code

private void DeleteAllMembers()
        {
            var m_MembershipUsers = Membership.GetAllUsers();
            foreach (MembershipUser m_MembershipUser in m_MembershipUsers)
                Membership.DeleteUser(m_MembershipUser.UserName, true);
        }

Thanks

Copy Link

Jon Boyer 37 posts 59 karma points

Sep 13, 2011 @ 01:12

0

Did you ever solve this? I'm now having the same issue.

Copy Link
James Crane 34 posts 80 karma points

Sep 13, 2011 @ 09:48

0

Hi Jon,

This was a while back now but from memory it turned out to be quite messy. The mistake I made was using the Umbraco API to add members instead of the MS Membership implementation.

I think I had to manually delete nodes from Umbraco tables (well put together some SQL) to deal with the issue in the end. Sorry I can't be more help - I'm about to leave the UK for a couple of weeks now so won't be able to respond any further.Good luck - keep searching though because it is possible to piece together a solution.

Ta

JC

Copy Link
Chris Lord 58 posts 211 karma points

Oct 14, 2011 @ 11:41

0

Hi Guys,

Had same problem today, resolved by manually deleting the records in SQL, the queries I used are;

delete from cmscontentxml where nodeid=1179

delete from cmscontentversion where contentid=1179

delete from cmscontent where nodeid=1179

delete from cmspropertydata where contentnodeid=1179

delete from umbraconode where id=1179

1179 was my rogue member being populated in my member picker property dropdown.

Hope this helps.

Chris

Copy Link
is working on a reply...

Please Sign in or register to post replies

Flag this post as spam?