30 Nov, 2010

1 commit


14 Aug, 2010

1 commit

  • 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
     

05 Aug, 2010

1 commit


19 Jul, 2010

1 commit


08 Jul, 2010

1 commit


06 Jul, 2010

1 commit


28 Jun, 2010

1 commit

  • * A lot of environment methods were not using settings_items in yours
      definition. In some cases use the code settings_items instead of
      define the method entirelly is more appropriated
    * The method boxes_limit was defined using LayoutTemplate? class in one
      case and in the other case, using the database.
    
    (ActionItem1568)
    Leandro Santos
     

16 Apr, 2010

4 commits


03 Apr, 2010

1 commit


20 Jan, 2010

3 commits


27 Oct, 2009

1 commit


07 Oct, 2009

1 commit


25 Sep, 2009

1 commit


07 Aug, 2009

1 commit


05 Aug, 2009

1 commit


03 Aug, 2009

3 commits


23 Jul, 2009

1 commit

  • Conflicts:
    	app/controllers/my_profile/memberships_controller.rb
    	app/views/profile_editor/_organization.rhtml
    	po/bg/noosfero.po
    	po/de/noosfero.po
    	po/es/noosfero.po
    	po/fr/noosfero.po
    	po/hy/noosfero.po
    	po/it/noosfero.po
    	po/nl/noosfero.po
    	po/noosfero.pot
    	po/pt_BR/noosfero.po
    	test/functional/profile_editor_controller_test.rb
    Antonio Terceiro
     

22 Jul, 2009

2 commits


06 Jul, 2009

1 commit


20 May, 2009

1 commit


11 May, 2009

2 commits


22 Apr, 2009

1 commit


17 Feb, 2009

1 commit


18 Dec, 2008

1 commit


15 Dec, 2008

4 commits


11 Dec, 2008

1 commit


05 Dec, 2008

1 commit


13 Nov, 2008

1 commit