I am not sure if this is the right place to post this. I have imported members using the CMS import and all is working well until I try to delete any of the members created.
I am getting an error (popup in the bottom right)
Error handling action
Object reference not set to an instance of an object.
The members usernames were all numbers so i tried to change to them to letters but no luck. I am out of ideas?
Thanks for getting back. There were no errors in the Umbraco log? Strange.
Anyways, i changed the username to letters and tried again. This time it was succesful. I imported again (with the username as letters) and then went into the member, changed the username to letters and tried to delete it which was succesful.
Perhaps an issue if you import with numerics only for the username?
I'm just assigning values. Must be something in the underlying system that is causing this behaviour will look into the behaviourt of Umbraco when I have the time. Thanks,
Deleting Member after CMS Import
Hello,
I am not sure if this is the right place to post this. I have imported members using the CMS import and all is working well until I try to delete any of the members created.
I am getting an error (popup in the bottom right)
Error handling action
Object reference not set to an instance of an object.
The members usernames were all numbers so i tried to change to them to letters but no luck. I am out of ideas?
Hi Kenny,
So you mapped integers to the username then it makes sense that the username is a number. Can you send the exception, it's in the Umbracolog table.
Thanks,
Richard
Hi Richard,
Thanks for getting back. There were no errors in the Umbraco log? Strange.
Anyways, i changed the username to letters and tried again. This time it was succesful. I imported again (with the username as letters) and then went into the member, changed the username to letters and tried to delete it which was succesful.
Perhaps an issue if you import with numerics only for the username?
Kenny
Hi Kenny,
I'm just assigning values. Must be something in the underlying system that is causing this behaviour will look into the behaviourt of Umbraco when I have the time. Thanks,
Richard
is working on a reply...