To repro:
1. I created a regular user
2. as admin i deleted the user
3. I went to register page and entered the same name for the user to register again
4. Now I can't get to the user administration page i get error:
All files must have an owner!
Has anyone else seen this? Any advice on how to get User Admin page to work again?
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by RaĆ¼l Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.
There was a bug in user deletion in RC2. It has been fixed for the final version. You should be able to fix your site by activating and running the garbage collector plugin from Tools admin.
This was related to an issue in RC2 regarding deleted entities and has been fixed in SVN.
The error is produced by entity fragments in the users_entity table, and you should be able to remove it by triggering the garbage collector.
Ahh, kevin beat me to it :)
Hi Kevin and Marcus - Thank you - turned my garbagecollector on - but I'm not sure how it's supposed to work.. all i could do was choose "weekly" from the drop down menu.
After I enabled the plugin I still cannot get to user admin page.
If you don't have cron enabled for your site, then I think that you can activate crontrigger to simulate it.
ok - i have the crontrigger and the garbagecollector enabled...
i tried to go to http://mysite.com/crontrigger
but this does nothing - page not found
thanks for the help first time i've had to do this!
crontrigger does not have a page - it just runs as you are navigating the site.
If the garbage collector has run, your user admin should work now.
ok - i disabled the other plugins i had enabled and the crontrigger worked!
Now I can see the user admin page again.
Thank you!
So - the bug comes back when i enable the Profile plugin.
Any way to fix this?
If I enable the "Profile" plugin - user admin will not show again.
there was still a fragment of the user left in the db table:
entities
This fragment was taken care of but can you all verify this is also fixed in the fix that you made for the final version?
- Previous
- 1
- 2
- Next
You must log in to post replies.