the default calendar widget represents the datetime format according to what your translations files are holding for the variable' %Y-%m-%d%H:%M:%S'(there are a few js variables here and there to connect the dots). So, by default, that string is usually translated to '%d/%m/%Y %H:%M:%S' in the file it.py . Moreover, the is_date(time) validators actually "strftimes" the datetime value when it's rendered (look at the represent() method)
tl;dr : usually web2py takes care of "translating" the format given the contents of your translations files > Another thing, create_on is the summer time for Italy, so when it's 18:00, > created_on save 17:00. > created_on by default assumes request.now. request.now holds the local time of the server. If there's a difference between your "real" local time and request.now you should check your server datetime settings (or start working with UTC dates, but that's a totally different matter). -- 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/groups/opt_out.
