07 Jul, 2015
1 commit
-
Conflicts: test/fixtures/article_followers.yml
06 Jul, 2015
3 commits
03 Jul, 2015
3 commits
-
ready for Serpro's captcha
02 Jul, 2015
1 commit
01 Jul, 2015
7 commits
29 Jun, 2015
2 commits
28 Jun, 2015
2 commits
27 Jun, 2015
3 commits
26 Jun, 2015
1 commit
23 Jun, 2015
2 commits
-
This reverts commit d829f145d43f82403250c76d7ba11c4639e047a4.
-
This reverts commit 9630118f0fb6f1c516e4a0641919a65bb2e8c33a.
19 Jun, 2015
1 commit
18 Jun, 2015
4 commits
17 Jun, 2015
6 commits
-
Add a follower for the article the commit message for your changes. Lines starting
16 Jun, 2015
2 commits
-
Conflicts: lib/noosfero/plugin.rb
-
This also removes short_filename as it is now unused
13 Jun, 2015
1 commit
-
This makes possible for a plugin to be defined as module and have its main class defined inside it with the name Base (e.g. MyPlugin::Base). The advantages of this is to correctly scope plugins constants inside the module. There are many conflicts with the core if the plugin is defined as klass, for example: - if you define a MyPlugin::DisplayHelper you'll get the error 'warning: toplevel constant DisplayHelper referenced by MyPlugin::DisplayHelper' and your class won't be loaded unless you put a "require 'my_plugin/display_helper'" - `require` is also needed for contants with the sames of constants declared under Noosfero::Plugin. For example, if you define a MyPlugin::Manager or MyPlugin::Settings, Noosfero::Plugin::Manager or Noosfero::Plugin::Settings will be returned instead of your plugin's definition. - other hard to debug errors may also happen. This also encapsulates loading procedures into methods of Noosfero::Plugin.
12 Jun, 2015
1 commit