photo

Baseball: Ohtani pushing limits of Angels’ conservative approach on We love sports

May 21, 2018, 7:37 p.m.

LOS ANGELES (Reuters) - The Los Angeles Angels have made it their mission to shield Japanese rookie Shohei Ohtani from overexposure in the early season, but as the two-way star proves his worth he may be forcing the team...

Baseball: Ohtani pushing limits of Angels’ conservative approach

karina kniaseff

Nov. 24, 2018, 12:52 a.m.

Django tips and tricks

How to make django timezone aware on Django tips and tricks

Feb. 23, 2018, 2:34 a.m.

As far as I know there is no way for the browser to tell the application what is the user's timezone.
That is a problem when you want to run an international site, mostly when users from different places save time related stuff.
Some people suggest to just ask the user what his timezone is.
I did not want to bother them with that, so I created this little hack.
this involves a context processor and some javascript.

So lets start with the context processor in django.
you start by writing your context_processor.py file

 from django.utils import timezone
 def timezone_processor(request):
     # look for a cookie that we expect to have the timezone
     tz = request.COOKIES.get('local_timezone', None)
     if tz:
         tz_int = int(tz) # cast to int
         # here we decide what will prefix timezone number
         # the output of tz_str will be something like: 
         #                Etc/GMT+1, GMT+0, Etc/GMT-2
         if tz_int >= 0:
             tz_str = 'Etc/GMT+'+tz
         else:
             tz_str = 'Etc/GMT'+tz
         # this forces timezone
         timezone.activate(tz_str)
     # Now we tell the template that we have a timezone
     return {'local_timezone': tz}

For the context processor to work you must declare it in settings.py

 TEMPLATES = [
     {
         .........
         'OPTIONS': {
             'context_processors': [
                 .........
                 'myapp.context_processors.timezone_processor',
             ],
         },

Ok, so this code just create a timezone string and activates it.
A template context processor returns a dictionary that will be sent to the context of the template when rendering. Here we are returning local_timezone.
But where this cookie come from? Lets go to the template and make this javascript trick.

 <!-- if django already knows timezone we will not run it again -->
 {% if not local_timezone %}
     <!-- getTimezoneOffset does the trick! -->
     <!-- it return minutes so we divide to get hours -->
     timezone = new Date().getTimezoneOffset() / 60;
     document.cookie = 'local_timezone=" + timezone;
     <!-- set a cookie with this value and we are done -->
 {% endif %}

*for simplicity I didn't include cookie expires nor half hour timezones like North Korea.

So it's first time the user enters the site. Django doesn't know yet it's timezone.
As local_timezone comes empty, we run this javascript lines, get the timezone offset and save it in a cookie.

Next page the user enters, the context processor will read that cookie and will activate the appropriate timezone.
If you need to activate it the very first time, just make it refresh after setting the cookie.

Well that's it, hope this helps you.

Cat videos

on Cat videos

Jan. 12, 2018, 2:21 p.m.

2

jogovi53

March 16, 2020, 5:40 p.m.

CANTABRIA ANTIGUA (I)
El poeta Silo Itálico, situando en un bélico tiempo la colosal figura de 'un cántabro llamado Laro' (LA GUERRA PÚNICA, XIV, 45-67) que pelea como es costumbre de su pueblo con un hacha de doble filo, elogiará las cualidades y el dinamismo de esta gente:

'El cántabro, invencible ante el frío, el calor y el hambre, se lleva antes que nadie la palma en toda clase de trabajos. ¡Admirable amor a su pueblo! Cuando la inútil edad senil comienza a encanecerle pone fin a sus años, ya no aptos para la guerra, envenenándose con el tejo. Para él es imposible vivir sin la guerra, pues toda la razón de su vida la pone en sus armas, considerando un castigo vivir para la paz.' SILIO ITÁLICO, La guerra púnica, II, 326-331)