Jeroen Dalsem

recursive disable is also not scalable and will (currently) also trigger events.... you could go for disable all `where guid = or parent_guid = ` query on entities and tackle...

that only solves removing the wait time from user... still need to have something for the time in between... or are you willing to accept the risk pages returning errors...

I like the STATE column... we could use it also for disabled states... it would remove the need for an extra where clause

a solution for this will not make it to Elgg 3.0

> We changed the all activity listing to not show comments/responses. > So the create blog river activity no longer shows the responses / comments. This way there is no...

This needs more thinking and probably is going to be breaking. Putting this on Elgg 5 for now.

we are not going to pursue this at the moment

> Or integrate a better administration dashboard design? Any ideas on this @rjcalifornia

> an entities table record exists for a user but no corresponding row in users_entity i think that "corruption" could be intended for a certain use case. Custom User Class...

That may be true, but it will not cover all the use cases + it's harder to implement and forces people to use innodb