27 Jan, 2011

1 commit

  • b8ade540   Procedure after last admin leaves organization ... Browse File » 
    * 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
     

10 Sep, 2010

2 commits

  • 37e4ba3e   Send e-mails through environment ... Browse File » 
    * Environment admin can send e-mail to all environment users
  * Community admin can send e-mail to all community members
  * Added migrate to create mailing
  * Added job to send mailing

(ActionItem1659)
    Daniela Feitosa
     
  • 51455693   Database access optimization ... Browse File » 
      * Rewrite ProfileListBlock logic to become simpler and faster
  * Rewrite membership logic to use named scopes instead of loading the
    entire list and doing filters with Ruby code.
  * Moved Noosfero-specific membership logic from access control plugin to
    Noosfero models.
  * Removed useless tests
  * Fixed tests that assumed the slow implementation
    Antonio Terceiro
     

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
     

12 Jul, 2010

1 commit

05 Feb, 2010

1 commit

10 Aug, 2009

1 commit

07 Aug, 2009

1 commit

30 Jul, 2009

1 commit

23 Jul, 2009

1 commit

22 Jul, 2009

1 commit

06 Jun, 2009

1 commit

20 Apr, 2009

1 commit

12 Jun, 2008

1 commit

11 Jun, 2008

1 commit

04 Jun, 2008

1 commit

02 Dec, 2007

2 commits

13 Nov, 2007

1 commit