14 Sep, 2012
1 commit
-
Comments with no author would break the wall. This fixes this issue. Comments are shown similar to the ones in article pages, displaying an specific icon to unknown users (non logged users) and other icon to removed users. Shows author name only if it exists (i.e if the author has a profile or if the name was provided for a non logged user) (ActionItem2445)
29 Aug, 2012
1 commit
-
Removes from activities the ActionTracker::Records which are redundants to certain profiles. (ActionItem2402)
19 Jul, 2012
1 commit
-
Also removed not used monkey patch Removed comments on CSS file
21 May, 2012
1 commit
17 May, 2012
3 commits
07 Mar, 2012
1 commit
-
Conflicts: app/views/shared/block.rhtml debian/changelog debian/control script/production
29 Feb, 2012
1 commit
-
* Also making activity removal be available for users who has permissions to edit the profile instead of the owner of the activity. (ActionItem2055)
04 Jan, 2012
1 commit
11 Dec, 2011
1 commit
27 Nov, 2011
1 commit
-
Conflicts: app/controllers/admin_controller.rb app/controllers/application.rb app/controllers/public/account_controller.rb app/controllers/public/content_viewer_controller.rb lib/noosfero/i18n.rb test/functional/account_controller_test.rb test/functional/admin_controller_test.rb test/unit/contact_test.rb test/unit/profile_test.rb
11 Oct, 2011
1 commit
-
Libs added * jquery-validation * colorbox * recaptcha (ActionItem2074)
10 Oct, 2011
1 commit
-
* Refactoring profile management to use tokeninput * Also, adding support of tokeninput to the core * Adding attributes validated and cnpj to enterprise * Environment option to define enterprise as validated by defaul * Making profile namedscopes consider subclasses too * Adapting enterprise icon and identification to meet Bsc expectations * Adapting profile info actions to meet Bsc expectations * Adapting control panel buttons to meet Bsc expectations * Adapting core product to meed Bsc expectations * Adding and fixing plugin hotspots (ActionItem2085, ActionItem2087, ActionItem2086, ActionItem2088)
30 Sep, 2011
1 commit
13 Aug, 2011
1 commit
-
(ActionItem2052)
10 May, 2011
1 commit
-
(ActionItem1996)
03 Apr, 2011
1 commit
-
Conflicts: test/unit/image_gallery_test.rb
22 Mar, 2011
1 commit
-
Also, fixing all selenium tests (ActionItem1672)
27 Feb, 2011
2 commits
-
* Forbidding folders to be created inside blogs. * Avoiding folders on the blog's posts until it's decided what's going to be done the the folders that are already inside blogs (migration). (ActionItem1892) -
(ActionItem1884)
22 Feb, 2011
1 commit
27 Jan, 2011
1 commit
-
* if he is also last member, the next user to join organization will become admin * if has other members, admin must choose some user to become admin * Generalized enterprise add_member interface. * Using json to manage action after join/leave/add/remove community/friend through ajax. * Person.members_of now returns unique profiles (ActionItem1400)
04 Jan, 2011
1 commit
-
Done: * Plugin loading process * Infra-structure for plugins registering and event activations. * Three fixed routes for plugins. * Methods to define plugins meta-information. * Interface for activation and deactivation of plugins in the environment panel. * Hotspots: - Buttons in the control panel. - Tabs in the profile (including expanded_template method). - New attributes for profile. * Possibility for the plugin to add new tables. * Mezuro prototype. Missing: * Test integration. * Dependencies integration. * Possibility to add behaviours in noosfero base models.
07 Dec, 2010
1 commit
-
(ActionItem1769)
21 Oct, 2010
1 commit
-
Users can delete own profiles Organization admins can delete organizations Environment admins also can remove others profiles (ActionItem1716)
04 Oct, 2010
1 commit
-
(ActionItem1303)
25 Sep, 2010
1 commit
24 Sep, 2010
1 commit
-
(ActionItem1673)
21 Sep, 2010
1 commit
-
* The users member of a community shoudl be notified with the information of where that noficication is. * The friendship relationship should be notified to the both users * If the article is created automaticaly according its template this article should not be notified * The article approval should not notify the article with the user who aproved it as the user that made the article (ActionItem1303)
20 Sep, 2010
2 commits
-
Also: * Adding links to the profile-image balloon. * Removing add-friend and join-community confirmation steps. -
(ActionItem1303)
12 Sep, 2010
1 commit
-
(ActionItem1303)
11 Sep, 2010
1 commit
-
(ActionItem1303)
02 Sep, 2010
1 commit
-
The HTTP caching feature conflicts with it. This was a crappy feature, anyway. (ActionItem1608)
27 Aug, 2010
1 commit
14 Aug, 2010
3 commits
-
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) -
(ActionItem1630)
23 Jul, 2010
1 commit
-
After creation/edition of an article, the user is redirected to the article Used back_to to store the page to return (ActionItem1424)