06 May, 2016

1 commit

  • Fix random selenium fails when trying to log in
    
    The cause of this issue is still undefined as both steps were leading to
    the same page, but with different behaviours.
    
    One possible cause is that clicking the "Login" link should be opening
    the log in modal which is not happening. All the taken screenshots are
    with the "Login" page displaying. Maybe this is still related to the
    previous issues with the selenium click steps addressed by the MRs #780
    and #785.
    
    See merge request !794
    Braulio Bhavamitra
     

29 Mar, 2016

1 commit

  • - Send activation code with delayed job
    - Avoid unecessary user save after update person
    
    Signed-off-by: Gustavo Jaruga <darksshades@gmail.com>
    Signed-off-by: Marcos Ronaldo <marcos.rpj2@gmail.com>
    Victor Costa
     

20 Feb, 2016

1 commit

  • The cause of this issue is still undefined as both steps were leading to
    the same page, but with different behaviours.
    
    One possible cause is that clicking the "Login" link should be opening
    the log in modal which is not happening. All the taken screenshots are
    with the "Login" page displaying. Maybe this is still related to the
    previous issues with the selenium click steps addressed by the MRs #780
    and #785.
    Rafael Reggiani Manzo
     

21 Jan, 2016

1 commit


20 Apr, 2015

1 commit


20 Nov, 2014

1 commit


19 Nov, 2014

1 commit


01 Nov, 2014

1 commit

  • Before testing for stuff in the database, we need first wait for a
    visual cue that the processing actually finished (in this case, looking
    for something in the expected page makes cucumber wait until the page
    actually shows up)
    Antonio Terceiro
     

08 Sep, 2014

1 commit

  • Conflicts:
    	app/controllers/application_controller.rb
    	app/controllers/my_profile/memberships_controller.rb
    	app/controllers/public/account_controller.rb
    	app/helpers/application_helper.rb
    	app/helpers/layout_helper.rb
    	app/helpers/token_helper.rb
    	app/views/account/signup.html.erb
    	app/views/layouts/_javascript.html.erb
    	db/schema.rb
    	test/functional/application_controller_test.rb
    Rodrigo Souto
     

20 Aug, 2014

4 commits


22 Jul, 2014

1 commit


16 Apr, 2014

1 commit


15 Apr, 2014

1 commit


13 Apr, 2014

2 commits


27 Mar, 2014

1 commit

  • (ActionItem3009)
    
    Signed-off-by: Alex Campelo <campelo.al1@gmail.com>
    Signed-off-by: Gustavo Jaruga <darksshades@gmail.com>
    Signed-off-by: David Carlos <ddavidcarlos1392@gmail.com>
    Signed-off-by: Arhur Del Esposte <arthurmde@gmail.com>
    Signed-off-by: Luciano Prestes <lucianopcbr@gmail.com>
    Signed-off-by: Fabio Teixeira <fabio1079@gmail.com>
    alcampelo
     

14 Mar, 2014

3 commits


20 Mar, 2013

1 commit


18 Mar, 2013

1 commit


06 Mar, 2013

1 commit


10 Dec, 2012

1 commit


15 Nov, 2012

1 commit


24 Jan, 2012

1 commit


19 Jan, 2012

1 commit


16 Jan, 2012

2 commits


30 Sep, 2011

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
     

20 Jan, 2010

1 commit


18 Jan, 2010

1 commit

  • 	* Not allowing people to signup without a name
    	* Adding a migrate to set identifier as name for people that are already without a name
    	* Changing the field "Full Name" to "Name" and to become red when not filled
    	* Adding new db:schema
    
    (ActionItem1352)
    Rodrigo Souto
     

30 Dec, 2009

1 commit


30 Oct, 2009

1 commit


09 Sep, 2009

1 commit