10 Mar, 2015
2 commits
-
When config/noosfero is a symlink to /etc/noosfero/plugins (or to any other location, really), relative symlinks do not work.
09 Mar, 2015
1 commit
-
somehow dash does not say anything, but bash complains.
27 Jan, 2015
1 commit
26 Dec, 2014
1 commit
-
Installing out-of-tree plugins with $ ./script/noosfero-plugins enable /path/to/plugin will just work. (Manually creating the symlinks should already work, but what the hell) Also, install relative symlinks to allow relocation of the Noosfero tree.
08 Nov, 2014
1 commit
02 Nov, 2014
1 commit
25 Sep, 2014
1 commit
27 Aug, 2014
1 commit
30 Jul, 2014
1 commit
-
Base plugins are enanbed by default and cannot be disabled at the system level, but can be disabled per-environment at the web UI. A part of the required changes also fix the Noosfero plugin infrastructure, in special migrations, on Rails 3.
29 Jul, 2014
1 commit
06 Jun, 2014
1 commit
-
Also: - check return of before_disable.rb when disabling plugins - fix rails3: instance_eval -> instance_exec (ActionItem2859)
08 Apr, 2014
1 commit
-
Making every plugin run its tests with independently, with only its migrations and only it enabled.
21 Aug, 2013
1 commit
-
(ActionItem2776)
28 May, 2013
1 commit
20 May, 2013
1 commit
-
(ActionItem2676)
07 May, 2013
1 commit
-
Conflicts: app/models/article.rb app/views/layouts/application-ng.rhtml lib/noosfero/plugin.rb script/noosfero-plugins
03 Apr, 2013
1 commit
-
Now the plugins can create the folders 'step_definitions' and 'support' under the folder 'features' to extend cucumber features as it pleases. The plugins with any extension gain 2 new profiles on the cucumber.yml file. For example, for mezuro plugin, it will have the 'mezuro' and 'mezuro_selenium' cucumber profiles that will load the appropriate files. So if you extend cucumber with new steps, hooks, etc; and you want to run the cucumber tests of mezuro plugin with all these extensions you must include '-p mezuro' on the cucumber call (or '-p mezuro-selenium' to run selenium profile). This is already handled by the rake task that runs the plugins' tests. So it'd be much better to run 'rake test:noosfero_plugins:mezuro:{cucumber,selenium}' instead. Also: * Moving plugins' 'features' folder to the plugin' root instead of inside the folder 'test' (just following Rails convention). * Moving specific steps and hooks of mezuro from core to the plugin. * Requiring plugin to be enabled to run any of its tests.
27 Feb, 2013
1 commit
-
After/Before enable/disable Also: alerting user to run reindex after enabling solr.
30 Aug, 2012
1 commit
27 Aug, 2012
1 commit
09 Mar, 2012
1 commit
01 Mar, 2012
4 commits
-
It also needs a database migration run, but since ./script/production will now run `rake db:migrate`, user don't need to perform this this step explicitly.
13 Oct, 2011
1 commit
27 May, 2011
1 commit
-
(ActionItem1987)
10 May, 2011
2 commits
02 Mar, 2011
2 commits
-
Run it without any arguments for usage.
