15 Jan, 2015
3 commits
-
In the process, fixes a `events.feature` scenario
04 Jun, 2014
1 commit
16 Jan, 2014
1 commit
12 Dec, 2012
1 commit
22 Mar, 2011
1 commit
-
Also, fixing all selenium tests (ActionItem1672)
26 Jan, 2011
1 commit
-
+ 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)
10 Dec, 2010
1 commit
-
* Added rss-feed-16.png (a 16x16 image of rss feed) * icon_name now is a class method * removing image_tags with article's icons * added icon_for_article on class to display icons (ActionItem1770)
26 Oct, 2010
1 commit
-
(ActionItem1680)
10 Sep, 2010
1 commit
-
I've tested manually and this works, but I could not make this test work. So, for now I am removing it. :-( (ActionItem1608)
26 Aug, 2010
1 commit
-
(ActionItem1647)
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)
06 Aug, 2010
1 commit
-
(ActionItem1606)
06 Jul, 2010
1 commit
-
(ActionItem1566)
28 Jun, 2010
1 commit
20 Jan, 2010
1 commit
-
* Added migration to add visible to profiles * Some improvements on profile screen * A private profile displays a different profile screen * added profile image, name, description and message * added link to join if profile is a community * added link to "add friend" if profile is a person * Added description in profile * Added field description to organization and person form * Removed link and added button on not_found page * Added css for not access_denied message * Changed css for flash messages * Recent articles doens't list private profile's articles * Private profiles are listed on blocks and searches * Invisible profiles are never listed * Join community popup will be displayed if profile is private * Join community popup will not be displayed if profile is invisible * If an organization is private, it is also closed
30 Dec, 2009
1 commit
-
(ActionItem1354)
11 Dec, 2009
1 commit
-
Trying to not depend on a too specific text
10 Dec, 2009
1 commit
-
If a person asks to publish an article in a community and removes it before approval, is displayed a message (ActionItem1343)
04 Dec, 2009
1 commit
-
ActionItem1309
30 Nov, 2009
2 commits
-
This is saner than clicking "Delete" an arbitrary number of times (this could break at any time in the future) (ActionItem1309)
-
* When a user try to publish an article in some communities and there is another article with the same name already published in these communities, an exception is raised and the exception message will be shown listing the commuinties where this problem ocurred. * If the community is moderated, then no message will be shown to the user, but when the moderator try to accept the task, an exception message will be shown informing that that name is already in use. ActionItem1309