a) I find it the easiest to have all the validation and checking to be done in onvalidation, ondelete, etc.. Unfortunately this doesn't happen in 2 situations out of 5 for deletion (again the question of the inconsistency). b) The asking of the password only occurs when the user decides to delete the record. If he enters edit to simply edit, there would be no sense in asking for the password. There is no extra step here.
quinta-feira, 11 de Abril de 2019 às 15:58:20 UTC+1, Anthony escreveu: > > On Thursday, April 11, 2019 at 7:54:46 AM UTC-4, João Matos wrote: >> >> They don't. I have everything working (the redirection to request for >> supervisor password on record deletion in the grid, using a link), the >> checks for record deletion in the edit form also work, except for the cases >> I pointed out. >> > > Yes, but just because everything is working does not mean (a) that was the > easiest way to achieve the end goal or (b) you haven't compromised user > experience to stay within the bounds of the available built-in > functionality. For example, if a special password is needed to delete a > record, it would be simpler to just enter it up front rather than first > submitting the delete request and then having to enter the password on a > separate page. Not only is that an unnecessary extra step, but it may > surprise the user if the UI makes no indication ahead of time that a > special password is required. > > Anthony > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
