09 Jan, 2014

1 commit

  • 9f616e0b   access_level: Custom permission for community users to access an article ... Browse File » 
    - Added a field on article new/edit to specify which users can access the article
- Added a relationship has_and_belongs_to_many between Article and Person
- Created a new table article_privacy_exceptions for has_and_belongs_to_many
- Added cucumber tests
- Added a new cucumber step to add a user to the exception users list

(ActionItem2852)

Signed-off-by: Alex de Souza <campelo.al1@gmail.com>
Signed-off-by: Athos Ribeiro <athoscribeiro@gmail.com>
Signed-off-by: Andre Bedran <bedran.fleck@gmail.com>
Signed-off-by: Arthur Del Esposte <arthurmde@gmail.com>
Signed-off-by: Carlos Andre <carlos.andre.souza@msn.com>
Signed-off-by: Fabio Teixeira <fabio1079@gmail.com>
Signed-off-by: Gabriela Navarro <navarro1703@gmail.com>
Signed-off-by: Gustavo Jaruga <darksshades@hotmail.com>
Signed-off-by: Matheus Faria <matheus.sousa.faria@gmail.com>
Signed-off-by: Tales Martins <tales.martins@gmail.com>
    Arthur Del Esposte
     

22 Aug, 2013

1 commit

21 Mar, 2013

1 commit

  • 2ceaba7c   Fixed test: features/edit_article.feature ... Browse File » 
    Some tests were breaking because since Selenium Driver 2, hidden
elements aren't available for interaction. However some elements started
to get unaccessible because some depend on hover on other elements and
the current version of Capybara doesn't support hover yet.

Avoid interaction with hidden elements is nice, but for the sake of
having the tests running while there isn't any touchable way of
displaying those elements through adequate methods, I'm overriding this
behaviour of Selenium Driver 2 with: Capybara.ignore_hidden_elements =
true.
    Rodrigo Souto
     

05 Mar, 2013

2 commits

10 Dec, 2012

1 commit

19 Jan, 2012

1 commit

22 Mar, 2011

1 commit

16 Dec, 2010

1 commit

10 Dec, 2010

1 commit

09 Dec, 2010

1 commit

26 Oct, 2010

1 commit

21 Sep, 2010

1 commit

20 Sep, 2010

2 commits

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
     

23 Jul, 2010

1 commit