17 Jun, 2015
16 commits
-
Add a follower for the article the commit message for your changes. Lines starting
-
Conflicts: app/models/article.rb
-
Conflicts: app/models/article.rb
-
Conflicts: app/views/cms/_event.html.erb
-
Conflicts: app/views/cms/_event.html.erb
-
Conflicts: Gemfile public/proposal-app public/stylesheets/application.css
-
This reverts commit dca569a4b682f150e8e9e3116ea7b14843651e44, reversing changes made to 364e52a3cfbc1b6a0943d99e31dba1880e1111fa.
16 Jun, 2015
16 commits
-
Conflicts: lib/noosfero/plugin.rb
-
folder: let word wrap work (do not short filenames) See merge request !503
-
This also removes short_filename as it is now unused
-
Expire LocationBlock cache on profile's location change http://noosfero.org/Development/ActionItem3217 See merge request !259
-
Search category with an autocomplete http://noosfero.org/Development/ActionItem3149 See merge request !227
-
Speed up role assignments fetch http://noosfero.org/Development/ActionItem3197 See merge request !252
-
(ActionItem3149)
-
Add column last update in the CMS file listings http://noosfero.org/Development/ActionItem2982 See merge request !105
-
Conflicts: app/views/cms/_view_items.html.erb config/locales/en.yml
-
Fix JS from fullscreen This patch fixes the JS that was returning null on article view page and not making the "Zoom in" of image feature appear. See merge request !602
15 Jun, 2015
3 commits
-
Signed-off-by: Gabriela Navarro <navarro1703@gmail.com>
14 Jun, 2015
1 commit
-
Support plugin to be defined as module instead of object 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. See merge request !482
13 Jun, 2015
2 commits
-
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
2 commits