17 Jan, 2014

1 commit

  • The following improvements have been made:
      - Created action that displays sub-organization and
      super organizations of a given organization.
      - Created a block that display related organizations.
      - List mother organizations to person's membership if
      he/she is member of a sub-organization.
    
    (ActionItem2499)
    (ActionItem2825)
    
    Signed-off-by: Arthur Del Esposte <athurmde@yahoo.com.br>
    Signed-off-by: Aurélio A. Heckert <aurelio@colivre.coop.br>
    Signed-off-by: Daniel Bucher <daniel.bucher88@gmail.com>
    Signed-off-by: Gabriela Navarro <navarro1703@gmail.com>
    Signed-off-by: Marcos Ramos <ms.ramos@outlook.com>
    Daniel
     

03 Oct, 2013

1 commit

  • The core extensions now should be created inside the folder lib/ext.
    They will automatically loaded, so no need for the requires on the
    plugin class definition file.
    
    Further information on how to use this feature here:
    http://noosfero.org/Development/PluginsArchitecture#Extending_core_classes
    Rodrigo Souto
     

18 Aug, 2012

1 commit


31 Jul, 2012

1 commit


23 Jul, 2012

1 commit


22 Jul, 2012

1 commit


20 Jul, 2012

1 commit


19 Jul, 2012

3 commits


18 Jul, 2012

2 commits


15 Jul, 2012

2 commits


05 Jul, 2012

3 commits

  • Rodrigo Souto
     
  •   1. organization_members: allows plugins to extend the list of members of
      an organization.
    
      2. has_permission?: allows plugins to add permission to some user to
      perform some action over a profile or environment. This hotspot only
      allows plugins to expand access, not to revoke access.
    
      3. new_community_hidden_fields and
      enterprise_registration_hidden_fields: allows plugins to include new
      hidden fields in the following forms.
    
      * Also including a monkey patch to include some features from the gem
        fake_arel that requires activesupport-2.3.14 and
        activerecord-2.3.14. This them allows OR with scopes without loading
        them.
    Rodrigo Souto
     
  •   * Every class now can declare that it is able to inlcude hotspots by
        declaring 'acts_as_having_hotspots'. It's important to note that
        every class that have hotspots must define an instance method named
        'environment' that returns the environment associated with the
        instance.
    
      * Now the enabled_plugins method is centralized in the Thread.current
        making the plugins instantiation happen only once by Thread. Every
        request reinstantiate the plugins since every request creates a new
        Thread. The models that access this method only instantiate it if it
        wasn't instantiated already.
    
      * Since the models doesn't reinstantiate the plugins in the same
        Thread and the tests run in only one Thread, the tests that have
        some plugin stuff must clean the instantiation in the teardown.
    Rodrigo Souto
     

22 Jun, 2012

1 commit


21 Jun, 2012

1 commit


05 Jun, 2012

2 commits


01 Jun, 2012

1 commit


26 May, 2012

2 commits


24 May, 2012

2 commits


22 May, 2012

1 commit


21 May, 2012

1 commit


20 May, 2012

2 commits


17 May, 2012

3 commits


16 May, 2012

2 commits


15 May, 2012

1 commit


14 May, 2012

2 commits


05 May, 2012

1 commit


02 May, 2012

1 commit