28 May, 2015

1 commit

12 Feb, 2015

1 commit

20 Jan, 2015

1 commit

  • 6984558b   Add UI to activate and deactivate profiles ... Browse File » 
    (ActionItem3287)
It can be done while edit a profile or in environment administration panel

Signed-off-by: Arthur Del Esposte <arthurmde@gmail.com>
Signed-off-by: David Carlos <ddavidcarlos1392@gmail.com>
Signed-off-by: Fabio Teixeira <fabio1079@gmail.com>
Signed-off-by: Gabriela Navarro <navarro1703@gmail.com>
Signed-off-by: Gustavo Jaruga <darksshades@gmail.com>
Signed-off-by: Luciano Prestes <lucianopcbr@gmail.com>
Signed-off-by: Parley Martins <parley@outlook.com>
    Fabio Teixeira
     

05 Jun, 2014

1 commit

25 Dec, 2012

1 commit

24 Aug, 2012

1 commit

11 Oct, 2011

1 commit

08 Aug, 2011

1 commit

14 Aug, 2010

1 commit

  • 1df72533   First stab at HTTP caching ... Browse File » 
    Implemented cache policy:

  * the homepage is cached for 5 minutes by default. This time can be
    configured with the =home_cache_in_minutes= attribute in the environment.
  * non-profile pages are cached for 15 minutes by default. This time can be
    configured with the =general_cache_in_minutes= attribute in the
    environment.
  * profile pages are cached for 15 minutes by default. This time can be
    configured in the =profile_cache_in_minutes= attribute in the environment.
  * The account controller (/account/*) is not cached at all.
  * The environment administration area (/admin/*) is not cached at all.
  * The profile administration area (/myprofile/*) is not cached at all.
  * Since Varnish will not cache any request that involves cookies:
    * Authenticated users will not benefit from the cache.
    * Cookies are not allowed for unauthenticated users. So, when a response is
      being prepared for an unauthenticated user, all cookies are wiped out.

The contents of the login block and the login/logout part of the header is now
loaded via an AJAX call to /account/user_data. This way we can cache almost all
pages without caching user-specific data.

We are also changing substantially how the flash[:notice] messages work. From
now on, instead of setting flash[:notice], we must set session[:flash]. It will
work more or less like before, except that session[:notice] will be consumed by
the AJAX call to /account/user_data that is done during all page loads instead
of being consumed automatically by Rails. The only exception to this is the
media_panel, because it uses a different layout.

(ActionItem1608)
    Antonio Terceiro
     

28 Apr, 2010

1 commit

03 Oct, 2009

1 commit

15 Sep, 2009

2 commits

17 Jul, 2009

1 commit

11 May, 2009

2 commits

29 Nov, 2008

1 commit

27 Sep, 2008

1 commit

23 Aug, 2008

1 commit

06 Feb, 2008

1 commit

16 Jan, 2008

1 commit

13 Nov, 2007

2 commits