20 Mar, 2014

1 commit

16 Mar, 2014

1 commit

07 Mar, 2014

1 commit

21 Feb, 2014

1 commit

20 Feb, 2014

1 commit

11 Feb, 2014

1 commit

31 Jan, 2014

1 commit

21 Jan, 2014

1 commit

20 Jan, 2014

1 commit

16 Jan, 2014

2 commits

08 Jan, 2014

1 commit

  • 2c251ae8   join_button: Join/Leave/Login Button ... Browse Dir » 
    - Added buttons at members block.
- Added checkbox to show or not the buttons on the community members.
- Removed the render button "enter/leave" when the checkbox that enables the button is unchecked
- Adjusted style CSS and display button
- Added cucumber and unit tests.
- Removed some spaces.
- There are two cucumber tests that wasn't done by the our team that fail if you don't use selenium. The files are publish_article.feature line 20 and search_enterprises.feature line 33 and we didn't modify them.

(ActionItem2844)

Signed-off-by: Arthur Del Esposte <arthurmde@yahoo.com.br>
Signed-off-by: David Carlos <ddavidcarlos1392@gmail.com>
Signed-off-by: Fabio Teixeira <fabio1079@gmail.com>
Signed-off-by: Gabriela Navarro <navarro1703@gmail.com>
Signed-off-by: Leandro Alves <leandrosustenido@gmail.com>
Signed-off-by: Tales Martins <tales.martins@gmail.com>
Signed-off-by: Andre Bedran <bedran.fleck@gmail.com>
Signed-off-by: Eduardo Vital <vitaldu@gmail.com>
    Carlos Andre de Souza
     

07 Oct, 2013

1 commit

04 Sep, 2013

1 commit

09 Aug, 2013

1 commit

26 Jun, 2013

1 commit

14 Jun, 2013

1 commit

01 Jun, 2013

1 commit

29 Oct, 2012

1 commit

15 Aug, 2012

1 commit

20 Mar, 2012

1 commit

06 Dec, 2011

1 commit

11 Oct, 2011

1 commit

16 Sep, 2011

1 commit

04 May, 2011

1 commit

  • 2f6997ed   Fixing some problems with domain for profiles. ... Browse Dir » 
    I've made a selenium test suite for all the problems I've noticed so far, that are the following:

* Profile control panel links in profile image block and profile information block
* Link to user profile in user bar
* Link to user control panel in user bar
* 'Go to the home page' button on not found page, that should link to profile home page or
to environment home page

So I've made the tests, ran them, fixed the problems, and ran the tests again.

(ActionItem1465)
    Caio SBA
     

22 Mar, 2011

1 commit

18 Jan, 2011

1 commit

27 Oct, 2010

1 commit

21 Oct, 2010

1 commit

04 Oct, 2010

1 commit

24 Sep, 2010

1 commit

  • 59489b86   Removing invented %{} 'markup' from links ... Browse Dir » 
    It turns out that Internet Explorer has problems with it. It looks like it
is trying to parse that text as %-escape caracters, and since the parsing
fails, it does not put those links as proper DOM elements but as 'raw'
objects, and thus the .href attribute does not exist (actually an error
occurs if you try to access such attribute on those objects).

This bug was introduced by the HTTP caching commit (ActionItem1608)

(ActionItem1711)
    Antonio Terceiro
     

20 Sep, 2010

1 commit

11 Sep, 2010

1 commit

10 Sep, 2010

1 commit

  • 51455693   Database access optimization ... Browse Dir » 
      * Rewrite ProfileListBlock logic to become simpler and faster
  * Rewrite membership logic to use named scopes instead of loading the
    entire list and doing filters with Ruby code.
  * Moved Noosfero-specific membership logic from access control plugin to
    Noosfero models.
  * Removed useless tests
  * Fixed tests that assumed the slow implementation
    Antonio Terceiro
     

02 Sep, 2010

1 commit

27 Aug, 2010

1 commit

14 Aug, 2010

1 commit

  • 1df72533   First stab at HTTP caching ... Browse Dir » 
    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

2 commits

09 Jul, 2010

1 commit