25 Aug, 2012
2 commits
-
ActionItem2306
24 Aug, 2012
8 commits
-
Undo some things, fix some tests, etc
-
Conflicts: lib/noosfero/plugin/context.rb lib/noosfero/plugin/manager.rb test/unit/plugin_manager_test.rb
-
ActionItem2306
23 Aug, 2012
4 commits
-
This way any class can just include Noosfero::Plugin::HotSpot and just invoke the plugins.
-
It was just a wrapper around controller, with no clear goal. In the end, the context will the object which invokes the plugins. Rigth now it means basically a controller, but wait a little bit and see. ;-)
-
This a way the controller is optional, because all data needed to obtain the list of plugins to be instantiated comes from the environment.
22 Aug, 2012
1 commit
21 Aug, 2012
8 commits
-
ActionItem2306
-
Additionally, I have made the "Mark as SPAM" and "Remove" links in the page view comment listing work through AJAX, so that now it is much more practical to remove comments or mark them as spam. ActionItem2306
-
…into merge-requests/181 Conflicts: app/controllers/application_controller.rb app/helpers/application_helper.rb app/models/person.rb app/views/enterprise_registration/basic_information.rhtml lib/noosfero/plugin.rb public/stylesheets/application.css test/unit/person_test.rb test/unit/profile_test.rb
-
ActionItem2306
-
ActionItem2306
20 Aug, 2012
3 commits
-
Plus a small enhancements on the existing UI for comments: turned the "delete" button into a text-only label in the bottom, instead of an annoying icon that shows up when you pass the mouse over the comment balloon. ActionItem2306
-
ActionItem2306
-
While the knowledge about spam and ham is included in the Noosfero core, actually checking comments for spam is delegated to plugins. This way we can have multiple ways of checking for spam. ActionItem2306
19 Aug, 2012
1 commit
-
Conflicts: db/schema.rb
18 Aug, 2012
2 commits
-
Also: - Added migration to remove action_trackers with target nil - Updated db/schema (ActionItem2400)
17 Aug, 2012
11 commits
-
…into merge-requests/212
-
Also replaced "if !" by "unless"
-
…into merge-requests/211
-
That idea could be useful for streaming comment data, but it is not useful to notify plugins that a comment was saved before checking e.g. that it is not SPAM. So this notification must be done by the CommentHandler class, *after* it decided that the comment received is valid (e.g. an antispam plugin decided it is not spam). ActionItem2306
-
…into merge-requests/210
-
…into merge-requests/209
-
(ActionItem2366)
-
…into merge-requests/185