12 Mar, 2012
2 commits
26 Jan, 2012
2 commits
-
This reverts commit 866d64b6ca3bf756f34f9d9e034dab22cf588658. This commit broke features/environment_name.feature :(
24 Jan, 2012
2 commits
-
(ActionItem2070)
-
(ActionItem2070)
16 Jan, 2012
2 commits
-
This reverts commit 5ee0d0eebb51c4507e19adc86c9c8f1edd994a30.
22 Nov, 2011
1 commit
-
This reverts commit 26e7f6658d9d47584be570c1715a032111306316.
14 Nov, 2011
1 commit
-
(ActionItem2070)
10 Oct, 2011
1 commit
-
(ActionItem2075)
07 Oct, 2011
1 commit
30 Sep, 2011
1 commit
30 Nov, 2010
1 commit
-
Removing all that mess feels *very good*. ActionItem1761
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)
05 Aug, 2010
1 commit
19 Jul, 2010
1 commit
08 Jul, 2010
1 commit
-
Conflicts: app/models/environment.rb features/publish_article.feature test/unit/application_helper_test.rb test/unit/blog_test.rb test/unit/environment_test.rb
06 Jul, 2010
1 commit
-
(ActionItem1578)
28 Jun, 2010
1 commit
-
* A lot of environment methods were not using settings_items in yours definition. In some cases use the code settings_items instead of define the method entirelly is more appropriated * The method boxes_limit was defined using LayoutTemplate? class in one case and in the other case, using the database. (ActionItem1568)
16 Apr, 2010
4 commits
-
Signed-off-by: Antonio Terceiro <terceiro@colivre.coop.br>
-
* This patch includes another unnecessary stuff just discovered unnecessary.
-
* This patch just removes all the help animations and its contents that are surely unnecessary.
-
* This patch includes all the substitutions of help animations to 'small' tagged content. * This solutions was used because the contents in these cases were important and shouldn't be removed.
03 Apr, 2010
1 commit
20 Jan, 2010
3 commits
27 Oct, 2009
1 commit
07 Oct, 2009
1 commit
25 Sep, 2009
1 commit
07 Aug, 2009
1 commit
05 Aug, 2009
1 commit
03 Aug, 2009
3 commits
23 Jul, 2009
1 commit
-
Conflicts: app/controllers/my_profile/memberships_controller.rb app/views/profile_editor/_organization.rhtml po/bg/noosfero.po po/de/noosfero.po po/es/noosfero.po po/fr/noosfero.po po/hy/noosfero.po po/it/noosfero.po po/nl/noosfero.po po/noosfero.pot po/pt_BR/noosfero.po test/functional/profile_editor_controller_test.rb
22 Jul, 2009
2 commits
-
* moved box "enterprise activation" to control panel * require login to activate enterprise
-
* move leave logic to profile_controller * use lightbox to leave confirmation, like join * store location to remember to where redirect
06 Jul, 2009
1 commit
-
We are trying to fool the spam robots, in the case they look for the first field matching something that looks like "e.*mail".