Tonight I spent some time working on admin users. This included adding a tool to create an admin user, functionality to see if the current user is admin user (using a modified is_logged_in() function), and modifications to the room's dashboard. This last part is more difficult than I anticipated. Test, delete, and edit functionality for rooms by default looks for rooms belonging to the current owner, which is what I want most of the time. I need to find a way to allow admin users to view/edit rooms not made by them.
As for the publishing workflow, right now the plan is that users create/test rooms, and an admin approves it to be considered in dungeon creation. This will be fine for beta tests, but I'm not sure how this would scale. There would have to be some flag that the user could set to say "this is ready for approval". Then, an admin would be notified, and then could test the room and approve it, or send a message back to the users describing why it was denied. I could probably make a table of user id, room name, status, status message. The user could interact with this table to set status to "Ready", and the admin could set status to "approved", "denied", and set a message. Yes.
I also did change avatar (finally!) tonight.
Game log / email / game history
Content creation with inspiration drawn from oldbookillustrations.com
admin users, content publishing workflow
2.5 Hours
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Tonight I spent some time working on admin users. This included adding a tool to create an admin user, functionality to see if the current user is admin user (using a modified is_logged_in() function), and modifications to the room's dashboard. This last part is more difficult than I anticipated. Test, delete, and edit functionality for rooms by default looks for rooms belonging to the current owner, which is what I want most of the time. I need to find a way to allow admin users to view/edit rooms not made by them.
As for the publishing workflow, right now the plan is that users create/test rooms, and an admin approves it to be considered in dungeon creation. This will be fine for beta tests, but I'm not sure how this would scale. There would have to be some flag that the user could set to say "this is ready for approval". Then, an admin would be notified, and then could test the room and approve it, or send a message back to the users describing why it was denied. I could probably make a table of user id, room name, status, status message. The user could interact with this table to set status to "Ready", and the admin could set status to "approved", "denied", and set a message. Yes.
I also did change avatar (finally!) tonight.
2.5 Hours