I'm for it given a few outstanding things: - If this only occurs in the move view now, I don't think we need the three-tuple return from can_move. Let's just have the api be raising a PageMoveException that can include the error message in it. - Need to document this (there's already a Page permissions section). - Need to include some tests.
On Fri, Jun 6, 2014 at 9:05 PM, Ahmad Khayyat <[email protected]> wrote: > Is there no interest in this feature? > > I kinda need it right now. Can we decide one way or the other? The code is > already there. Calling can_move() during page creation is separated into > its own commit. > > Pull request: https://bitbucket.org/stephenmcd/mezzanine/pull-request/63/ > > > -- > You received this message because you are subscribed to the Google Groups > "Mezzanine 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. > -- Stephen McDonald http://jupo.org -- You received this message because you are subscribed to the Google Groups "Mezzanine 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.
