On 5 Gru, 23:56, mdipierro <[EMAIL PROTECTED]> wrote: > Whatever you have this should not happening. RestrictedError is an > internal web2py error that means an error has been caught. Web2py > should catch RestrictedError and display the traceback therein. > > Would you, confidentially, send me your app so that I can look at what > may be causing this?
After I repaired it by creating db from web2py and importing data via pg_dump RestrictedError in console disappeared. I think it was because something was incompatibile between db schema and web2py model. I will send you both app and pd_dump output because this is repeatable. Both models differs but I think web2py should show me "normal" ticket with such info. As for problem that even after I corrected the db schema I got strange error: Mystery solved! I restarted web2py again (cleaning tickets and sessions) and again and again, date changed (in Poland there is now 30 minutes after midnight) but date in ticket remained the same. Strange. Then I used "clear the browser cache" and that can do miracles :) It seems that my browser cached this ticket and shown me it instead of normal app. So, now my app works well on corrected model and cleared cache. Thanks for your help, Michał --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
