-
Notifications
You must be signed in to change notification settings - Fork 663
recursive disable_entity fails if the code is not logged-in (Trac #1196) #1196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
brettp wrote on 39660109-06-02 (In [svn:3450]) Fixes #1196: ElggEntity::disable() now accepts a 2nd arg for recursive. New users are not recursively disabled for plugins that need to create entities owned by the new user upon entity creation. |
brettp wrote on 39660146-01-18 Reopening because this commit doesn't solve the actual problem, but solves a symptom. Users are now registered as expected, but you still cannot recursively disable an entity when logged out. |
brettp wrote on 40088350-09-06 The problem is that the recursive delete function's $__RECURSIVE_DELETE_TOKEN is based upon logged in user id. |
Milestone changed to |
Title changed from |
Milestone changed to |
Milestone changed to |
Original ticket http://trac.elgg.org/ticket/1196 on 39658668-09-20 by trac user kevinjardine, assigned to unknown.
Elgg version: 1.6
Elgg 1.6 displays a:
"Failed to load new ElggObject from GUID:XXX"
message if a user registers and one or more default widgets have been defined.
The code creates the user and the widget, and then disables the user (until reactivated by the confirmation link).
When disabling the user, the code also attempts to disable all the objects owned by the user, including the widget. However, the code is running with no user logged in, and the widget default access control is set to "Logged-in users". Hence the error is generated.
The disable_entity function attempts to do something to route around Elgg's access controls but this apparently no longer works under Elgg 1.6.
The text was updated successfully, but these errors were encountered: