05 Jun, 2015

1 commit

01 Jun, 2015

1 commit

30 May, 2015

2 commits

26 May, 2015

1 commit

20 Aug, 2014

1 commit

30 Jan, 2014

1 commit

  • de0aceaa   rails3: fix assert_kind_of Array ... Browse File » 
    On rails 3.2, the return type of some queries changes from Array to ActiveRecord::Relation.
An assertion that check if these attributes has been assigned (with a value != nil) should be enought.
This avoids future problems with api changes.
    Victor Costa
     

14 Oct, 2013

1 commit

30 Nov, 2012

1 commit

11 Dec, 2011

1 commit

11 Oct, 2011

1 commit

27 Feb, 2011

1 commit

31 Jan, 2011

1 commit

26 Jan, 2011

1 commit

  • e7464a3d   Multitask ... Browse File » 
    + Multi-processing tasks.
  + Graciously show/hide functions with the smooth slide of
  + Jquery. ^^
  + Using Unobtrusive Javascript.
  + Customized messages for each task type.
  + Button "Set all to approve/reject/skip".
  + Icons related to the task action.

  * Missing
    - Need to make selenium tests.

(ActionItem1527)
    Rodrigo Souto
     

27 Aug, 2010

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
     

16 Apr, 2010

1 commit

30 Nov, 2009

1 commit

  • a8418460   Articles published with the same name aren't ignored ... Browse File » 
      * 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
     

03 Feb, 2009

1 commit

11 Nov, 2008

1 commit

05 Sep, 2008

1 commit

29 Aug, 2008

1 commit

22 Aug, 2008

1 commit

20 Aug, 2008

1 commit

05 Jun, 2008

1 commit

28 Feb, 2008

1 commit

22 Feb, 2008

3 commits