27 May, 2013

1 commit


19 Jan, 2013

1 commit


15 Nov, 2012

1 commit


25 Oct, 2012

3 commits


24 Oct, 2012

2 commits


28 Sep, 2012

1 commit


13 Sep, 2012

1 commit


22 May, 2012

1 commit


21 May, 2012

3 commits


17 May, 2012

6 commits


07 Mar, 2012

1 commit


29 Feb, 2012

1 commit


04 Jan, 2012

1 commit


11 Oct, 2011

1 commit


12 Sep, 2011

1 commit


11 May, 2011

1 commit


22 Mar, 2011

1 commit


27 Feb, 2011

1 commit


01 Feb, 2011

1 commit


27 Jan, 2011

1 commit

  • * if he is also last member, the next user to join organization will become admin
    * if has other members, admin must choose some user to become admin
    * Generalized enterprise add_member interface.
    * Using json to manage action after join/leave/add/remove
    community/friend through ajax.
    * Person.members_of now returns unique profiles
    
    (ActionItem1400)
    Daniela Feitosa
     

06 Nov, 2010

1 commit


04 Oct, 2010

1 commit


25 Sep, 2010

1 commit


24 Sep, 2010

1 commit


20 Sep, 2010

1 commit


12 Sep, 2010

1 commit


11 Sep, 2010

1 commit


02 Sep, 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