Welcome the Technical Support section. Help us in assisting you by providing us with a concise and descriptive elaboration of your issues. Be specific and if possible, provide us with a step-by-step instruction in replicating your problem.
ISSUE SUMMARY:
If a user decides to "delete" his profile, the users profile is set to "not enabled", but the user and his profile remains in Joomla.
If the administrator then wants to remove the user from the system - Deleting the user completely, an error is shown
Fatal error: Cannot use object of type stdClass as array in /public_html/plugins/user/jomsocialuser/jomsocialuser.php on line 648
If the user did not try to delete his profile first, it is possible to remove(delete) the user.
After getting this issue, I upgraded to JomSocial 4.2.5 and Joomla 3.6.3 - the issue remains
STEPS TO REPLICATE:
1 Create a new user
2 Log in to Jomsocial as the newly created user
3 Go to the edit profile - here is the option to "Delete Profile"
4 Press "Delete profile"
5 Log into the backend as an administrator
6 See that the user is still there but the "enabled" flag is now removed
7 Mark the user and press Delete
8 Error appears
I cant replicate it at my test site.
and I tried to created new user at your site. but I cant visiting edit profile page.
always got:
Du er ikke autoriseret til at se denne side.
could you please give me the error detail message?
you need to delete the user under jomsocial backend > monitor > members
You cannot access the site as you have to be a "member" - In lack of better, I use the Joomla ACL for this. Which user did you create, I can then set the user up correctly.
I try to delete the user via jomsocial backend -> monitor -> member
I get the error message that I already uploaded:
Fatal error: Cannot use object of type stdClass as array in /public_html/plugins/user/jomsocialuser/jomsocialuser.php on line 648
It is really strange, if I create a new user and then delete him again - it works. It looks like my problem is related to 4 profiles that have been there for a long time - so created on a different version of JomSocial - but since it is not a problem with the new version of JomSocial, I am ok with closing this topic.