In my opinion I'd go for point B, that's would help us with many people testing it. We could also start using as sson as the main features are ok.
- I'm ok with this too. I would copy all current 17_STABLE over 18_STABLE and begin working there (merging every commit to HEAD always). Yep, No? Eloy Lafuente (stronk7) 13:36, 3 March 2007 (CST)
See my access.php for roles and capabilities--they are all standard except for the Print teacher role--this was used to edit roles for the names that will print on the certificate for "teacher". Any ideas for a better way to do this?
- Hi Chardelle, I don't understand the "mod/certificate:teacher" capability. Are you saying that it's used to determine what roles are allowed to print the teacher certificate? Yes? Uhm... it's hard to decide who has that capability by default. Perhaps only admin and every institution has to decide about it, giving to certain users? I'm going to ask to role gurus about this... Eloy Lafuente (stronk7) 13:36, 3 March 2007 (CST)
Manage certificates in 2.0
Could we have a delete certificate feature? I would suggest keeping the record, add a valid/void field plus fields of voidcomment, void date, userwhovoid. Then the teacher/admin could void a certificate, and we could have more display options.
The student might or might not be able to see their void certificate given advanced certificate setting. A filter for the teacher or administrator to see all issued certificates, only valid, only void.
This might allow also an edit where a certificate could be "unvoided" and the comment saved. I would keep it simple and not create a record for every change
I like the 2.0 potential to reissue certificates. Perfect for my "unlawful harassment class" I have to take every year. --chris collman 12:40, 19 September 2010 (UTC)