13 Aug, 2011

1 commit


11 Aug, 2011

1 commit


09 Aug, 2011

7 commits


08 Aug, 2011

3 commits


22 Mar, 2011

1 commit


27 Feb, 2011

1 commit


13 Jan, 2011

1 commit


10 Dec, 2010

2 commits


09 Dec, 2010

3 commits


07 Dec, 2010

1 commit


21 Sep, 2010

1 commit


20 Sep, 2010

2 commits


17 Sep, 2010

2 commits


26 Aug, 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
     

13 Aug, 2010

1 commit


11 Aug, 2010

1 commit


23 Jul, 2010

1 commit


14 Jun, 2010

1 commit


18 May, 2010

1 commit


01 Feb, 2010

1 commit


30 Nov, 2009

2 commits

  • Conflicts:
    
    	app/views/profile_editor/_organization.rhtml
    	features/support/selenium.rb
    Antonio Terceiro
     
  •   * When a user try to publish an article in some communities
        and there is another article with the same name already
        published in these communities, an exception is raised and
        the exception message will be shown listing the commuinties
        where this problem ocurred.
    
      * If the community is moderated, then no message
        will be shown to the user, but when the moderator try
        to accept the task, an exception message will be shown
        informing that that name is already in use.
    
    ActionItem1309
    Rodrigo Souto
     

31 Oct, 2009

1 commit

  • For some weird reason, in development mode we were being redirected to a
    URL without a port number. Article#url returned with the port number, bur
    Article#view_url did not (only in this context, in an automated test it
    worked ok).
    
    Since in production mode Noosfero.url_options is guaranteed to return an
    empty hash, this has no impact on production servers.
    Antonio Terceiro
     

26 Oct, 2009

1 commit


16 Sep, 2009

1 commit


02 Sep, 2009

1 commit