27 Feb, 2015

1 commit

  • To install:
    
    $ sudo ln -s $NOOSFERO/plugins/stoa/script/stoa-auth-server /etc/init.d/
    $ sudo update-rc.d stoa-auth-server defaults
    $ sudo service stoa-auth-server start
    
    Of course, the stoa plugin must be enabled and properly configure foo
    any of this to work.
    
    It will run on port 4000, and requests must be made to /, e.g.
    
    $ curl -d 'login=USER&password=PASSWORD' http://server:4000/
    Antonio Terceiro
     

24 Feb, 2015

1 commit


23 Feb, 2015

2 commits


22 Feb, 2015

3 commits


20 Feb, 2015

1 commit


13 Feb, 2015

1 commit


12 Feb, 2015

2 commits


11 Feb, 2015

4 commits


10 Feb, 2015

12 commits


09 Feb, 2015

2 commits


03 Feb, 2015

3 commits


02 Feb, 2015

1 commit


30 Jan, 2015

3 commits


28 Jan, 2015

2 commits

  • Created a scope to show only visible and enabled enterprises on environment statistics block.
    Bug fix from #2783
    Eduardo Passos
     
  • When acessing Noosfero through a properly configured HTTPS setup, all
    links will now be generated with https (or without an explicit
    protocol and will just work).
    
    Links generated outside of the scope of a request (models, mailers etc)
    will still use http://. That can be fixed by a localized change to
    Environment#top_url, but for now I expect everyone using HTTPS to have a
    proper HTTP -> HTTPS redirection mechanism.
    Antonio Terceiro
     

27 Jan, 2015

1 commit


22 Jan, 2015

1 commit

  •  - Moved EmailContact class from ext directory to plugin scope
     - Refactored Work Assignment Plugin to accept general articles instead of only uploaded files
     - Protecting methods that are not supposed to be actions
    
    Signed-off-by: Tallys Martins <tallysmartins@gmail.com>
    Signed-off-by: André Bernardes <andrebsguedes@gmail.com>
    Signed-off-by: Hebert Douglas <hebertdougl@gmail>
    Tallys Martins