On Tuesday, December 30, 2014 7:32:15 AM UTC-8, Niphlod wrote: > > I don't get what you're asking for. If you choose to create *your* own > policy and part of *your* application uses something that *your* own > policy discards, there's nothing *web2py* can do. > > If it were me, I'd be asking for suggestions that either
a) modify the policy in a way that maintains security but allows the calendar.js to work (this would likely be a suggestion from someone with experience with security policies) b) suggest a way to remove the dependency on 'eval' (this would likely be a suggestion from someone with experience swapping js files under web2py) It's possible that there's a fundamental conflict, though, that makes either type of suggestion difficult. /dps -- 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.
