24 Jul, 2015

1 commit

11 Jun, 2015

1 commit

22 May, 2013

1 commit

27 Mar, 2013

1 commit

12 Dec, 2012

1 commit

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
     

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
     

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
     

30 Jul, 2010

1 commit

08 Jul, 2010

1 commit

01 Jul, 2010

1 commit

  • 6aa4927c   Custom fields fixed ... Browse File » 
     * Fixed fields that weren't in the custom fields options.
 * Included "Display on creation|registration" feature for
   organization fields.
 * Included fields dependencies:
     [field]   -> [dependencies]
     required  -> active, signup
     signup    -> active
 * Javascripts to grant the dependencies on the radioboxes.
 * Changing the validation of fields presence message.
 * Also removing some unwanted endline spaces.

(ActionItem1509)
    Rodrigo Souto
     

28 Jun, 2010

1 commit

19 Apr, 2010

1 commit

16 Apr, 2010

2 commits

  • 6a7965a4   Remove inverted logic in environment features ... Browse File » 
    (ActionItem1482)
    Antonio Terceiro
     
  • 542135da   Fixing the Enterprise Registering Process ... Browse File » 
    * The registration has two validation type: region and admin.
		+ Admin
			- There is no validator to choose.
			- The regions to choose are states (This might be changed
			  in the future).
			- The admins of the environment recieves the task to approve
			  the registration of this new enterprise.
			- The region field isn't displayed.
		+ Region
			- If there isn't any validator, shows a message that it's
			  not possible to register any enterprise and don't show the
			  form.
			- Show only the regions where is registered at least one
			  validator.
			- The region field is displayed.
   	* The required fields are highlithed.
	* The fields that are active or required are set through the
	  administration panel.
	* Only the fields name and identifier are always required.
   	* After registering a new enterprise, the user is set as an admin of
   	  it.
   	* The cancel button in the register form is working properly.
   	* In the "Validator" step, the radio button is choosing a default
   	  option.
   	* Cancel radio_button in the task validation has a "Rejection
   	  Explanation" field that is required.
   	* Some navigation buttons added.
   	* Changed some buttons to labelled buttons.
	* The "Register a new enterprise" button is an admin option.

(ActionItem1482)
    Rodrigo Souto