30 Sep, 2015

2 commits


29 Sep, 2015

5 commits


28 Sep, 2015

1 commit


23 Sep, 2015

1 commit


11 Sep, 2015

1 commit

  • * models should use acts_as_having_image transparently
    * force margin zero in HTML mailing
    * using require_dependency instead of require to avoid error:
      "superclass mismatch for class MailingJob"
    * now plugins can schedule jobs via whenever rubygem
    * improve 'sample-data' scripts to create some blog posts
    
    signed-off-by: Joenio Costa <joenio@colivre.coop.br>
    Larissa Reis
     

12 Aug, 2015

2 commits


11 Aug, 2015

2 commits


10 Aug, 2015

3 commits


09 Aug, 2015

1 commit


07 Aug, 2015

2 commits


06 Aug, 2015

4 commits


05 Aug, 2015

1 commit


03 Aug, 2015

1 commit


29 Jul, 2015

1 commit


27 Jul, 2015

1 commit


24 Jul, 2015

1 commit


22 Jul, 2015

1 commit


21 Jul, 2015

3 commits


13 Jul, 2015

1 commit


16 Jun, 2015

1 commit


14 Jun, 2015

1 commit


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.
    Braulio Bhavamitra
     

11 Jun, 2015

2 commits


09 Jun, 2015

1 commit