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
     

05 Aug, 2010

1 commit

15 Dec, 2008

2 commits

  • a6fdacba   ActionItem862: English review and pt_BR translation update Browse File »
    Antonio Terceiro
     
  • 0ba97d30   ActionItem833: port unifreire-specific changes as configuration into master branch ... Browse File » 
      * making fields appear on signup form
  * environment has a list of Category subclasses that must be available for users; if there is only one category type available, no need of asking for category type
  * environment has a setting categories_menu which enables/disables the category menu. If it is disabled, then no need to ask for a color in the menu
  * add a configuration to the environment called disable_gender_icon. When it is false, don't display gender icons.

  * adding css for profile_data
  * adding required on label for schooling fixing javascript
  * adding fields on signup and option to admin manage
  * adding required message on required fields
  * adding partials for person/enterprise/community fields
  * adding methods for person/community/enterprise custom_fields
  * adding option to admin manage person fields
    Daniela Feitosa
     

23 Jan, 2008

1 commit

13 Nov, 2007

2 commits