Ticket #72 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

Group Controller Implementation

Reported by: ssmith Assigned to: ssmith
Priority: high Milestone: Week 32
Component: Model Version:
Severity: normal Keywords:
Cc:

Description

As a group hierarchy doesn't fundamentally exist for Dal societies (all societies are basically children of the DSU), we are currently going to ignore the Groups_Users_Controllers at the current time.

Instead, we are going to implement a 'superuser' tag in the database, attached to the 'users' table.

Then, all current validation scripts will first check User.superuser for editing permissions.

This will allow me to complete #35, #37, #27

Change History

05/08/05 10:36:20 AM changed by nichols

I assume this isn't a permanent solution?

05/08/05 10:46:25 AM changed by ssmith

  • status changed from new to assigned.
  • component changed from Database to Models.
  • milestone changed from Week 31 to Week 32.

That is correct.

However, at the current time it has been decided that since initially, only top level DSU individuals will be GroupControllers? anyway, that it is much easier to implement a superuser tag.

Later, the code will be refactored so that instead of having all societies being children of the DSU, they will properly be children of their proper umbrella parent.

06/08/05 11:55:38 AM changed by ssmith

  • status changed from assigned to closed.
  • resolution set to fixed.

Closed in revision [86]