26 May, 2015
1 commit
-
Signed-off-by: Arthur Del Esposte <arthurmde@gmail.com> Signed-off-by: Fabio Teixeira <fabio1079@gmail.com>
03 Feb, 2015
1 commit
-
Part of rails 3 migration Also removes useless line. The check for enabled plugin is made before adding the filter. Besides, that proc was never called.
06 Oct, 2014
1 commit
26 Sep, 2014
1 commit
10 Mar, 2014
1 commit
03 Oct, 2013
1 commit
-
The core extensions now should be created inside the folder lib/ext. They will automatically loaded, so no need for the requires on the plugin class definition file. Further information on how to use this feature here: http://noosfero.org/Development/PluginsArchitecture#Extending_core_classes
07 Oct, 2012
1 commit
-
- Added render_not_found screen when comment id doesn't exist - Displaying message when trying to edit a comment from other page - Fixed a test on ToleranceTimePlugin
01 Oct, 2012
2 commits
-
Conflicts: po/pt/noosfero.po public/javascripts/application.js
06 Sep, 2012
2 commits
05 Sep, 2012
2 commits
30 Aug, 2012
2 commits
28 Aug, 2012
5 commits
27 Aug, 2012
5 commits
25 Aug, 2012
1 commit
24 Aug, 2012
2 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
23 Aug, 2012
3 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.
21 Aug, 2012
6 commits
-
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
18 Aug, 2012
1 commit
17 Aug, 2012
1 commit
-
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
31 Jul, 2012
1 commit