03 Nov, 2015
1 commit
30 Oct, 2015
1 commit
-
$ rake updatepo
07 Oct, 2015
1 commit
05 Oct, 2015
1 commit
-
On Ruby 1.9+ these are no-ops
02 Oct, 2015
1 commit
25 Sep, 2015
1 commit
16 Sep, 2015
1 commit
13 Aug, 2015
1 commit
10 Aug, 2015
1 commit
06 Aug, 2015
2 commits
-
also, add missing .pot files for plugins
31 Jul, 2015
1 commit
-
ruby-minitest offers "refuse" as a syntatic sugar to "assert not"
24 Jul, 2015
3 commits
-
Use these two commands inside vim: :!ag -l '..\/..\/..\/..\/test' | xargs perl -pi -E "s/require.*test_helper.*/require 'test_helper'/g" :!ag -l "require File.*'/" | xargs perl -pi -E "s/require File.*'\//require_relative '/g":e ""'"
01 Jun, 2015
1 commit
28 May, 2015
1 commit
-
This avoids solr throwing an error when it tries to filter by unindexed column.
06 Mar, 2015
1 commit
-
Conflicts: plugins/statistics/po/es/statistics.po po/de/noosfero.po po/es/noosfero.po
05 Mar, 2015
1 commit
23 Feb, 2015
3 commits
-
Currently translated at 88.0% (22 of 25 strings)
-
Currently translated at 100.0% (25 of 25 strings)
-
Currently translated at 96.0% (24 of 25 strings)
10 Feb, 2015
1 commit
-
Index lat/lng on articles http://noosfero.org/Development/ActionItem2933 See merge request !46
02 Feb, 2015
1 commit
30 Jan, 2015
1 commit
15 Jan, 2015
3 commits
-
I have deduplicated every message in plugin code that was already in the core. Going forward, plugins should use c_() is they want to reuse the message from the core. If they want to force their own translation, they should probably use _('plugin_name|The message') to avoid overriding translations from the core.
07 Nov, 2014
1 commit
-
Just enabling the plugin (as when running plugins tests) will cause a HUGE download to be made.
19 Sep, 2014
2 commits
04 Jun, 2014
4 commits
22 Jan, 2014
1 commit
-
…into merge-requests/342 Conflicts: plugins/shopping_cart/controllers/shopping_cart_plugin_controller.rb
13 Jan, 2014
1 commit
22 Nov, 2013
3 commits
-
Since there are plugins that need to receive the scope clean (that is without filters applied to it) and since the plugin has the power to not apply the filter when conveys it (also rewriting the interface to keep its consistency), I decided to pass the reposability of applying any filter provided by the core to the engines. Nevertheless, if the plugin returns nil (that's the same that it would return if it was disabled) the core will deal with the filters through the default way (that is without any engine).