08 Apr, 2016

1 commit

  • Signed-off-by: Alexandre Barbosa <alexandreab@live.com>
    Signed-off-by: Arthur Jahn <stutrzbecher@gmail.com>
    Signed-off-by: David Carlos <ddavidcarlos1392@gmail.com>
    Signed-off-by: Marcos Ronaldo <marcos.rpj2@gmail.com>
    Signed-off-by: Victor Costa <vfcosta@gmail.com>
    Carlos Purificação
     

06 Apr, 2016

2 commits

  • Enables push notification for mobile platforms using Google Cloud Message infrastructure.
    
    - Administrators can choose among all available notification
    - Users can activate notifications through API and GUI
    - Users devices MUST be registered through API to use push notifications
    - Other plugins can add users to be notified for each notification.
    - Available notifications can be found in the file "notification_settings.rb"
    
        Signed-off-by: Marcos Ramos <ms.ramos@outlook.com>
        Signed-off-by: Marcos Ronaldo <marcos.rpj2@gmail.com>
    Marcos Pereira
     
  • Add subtitle support to the following core blocks:
    * my_network
    * profile_search
    * categories
    * highlights
    * slideshow
    * article
    * blog_archives
    * featured_products
    * feed_reader
    * link_list
    * location
    * products
    * profile_list
    * raw_html
    * recent_documents
    * tags
    
    Add subtitle support to the following plugins blocks:
    * community_track: track_list
    * container_block: container
    * context_content: context_content
    * display_content: display_content_block
    * event: event
    * gallery_block: gallery_block
    * organization_ratings: organization_ratings_block
    * people_block: people_base
    * profile_members_headlines: headlines
    * recent_content: recent_content_block
    * relevant_content: relevant_content_block
    * site_tour: tour
    * sniffer: interests_block
    
    Signed-off-by: Daniela Soares Feitosa <danielafeitosa@colivre.coop.br>
    Arthur Esposte
     

05 Apr, 2016

1 commit

  • New feature: manage email templates
    
    This MR depends on liquid ~> 3.0.3 and this version is not available on Debian Jessie, just in testing and unstable. So, I will upload ruby-liquid (3.0.4) to Noosfero Debian Jessie archive to satisfy it.
    
    See merge request !814
    Rodrigo Souto
     

01 Apr, 2016

5 commits


31 Mar, 2016

4 commits


29 Mar, 2016

1 commit

  • - Send activation code with delayed job
    - Avoid unecessary user save after update person
    
    Signed-off-by: Gustavo Jaruga <darksshades@gmail.com>
    Signed-off-by: Marcos Ronaldo <marcos.rpj2@gmail.com>
    Victor Costa
     

24 Mar, 2016

1 commit


22 Mar, 2016

1 commit


21 Mar, 2016

1 commit


15 Mar, 2016

1 commit


10 Mar, 2016

14 commits


08 Mar, 2016

2 commits


07 Mar, 2016

1 commit


03 Mar, 2016

1 commit


26 Feb, 2016

2 commits

  •   - changes pagination to use api-pagination gem
      - new endpoints to boxes, activities, and profiles
      - new exposed attributes for some entities
      - other minor changes
    
      Signed-off-by: Leandro Nunes dos Santos <leandronunes@gmail.com>
      Signed-off-by: Marcos Ronaldo <marcos.rpj2@gmail.com>
      Signed-off-by: Michel Felipe de Oliveira Ferreira <michel.ferreira@serpro.gov.br>
      Signed-off-by: Victor Costa <vfcosta@gmail.com>
    Marcos Pereira
     
  • - Adds use of filtered members to mailing queue executed by send_mail action
    
    Signed-off-by: Gustavo Jaruga <darksshades@gmail.com>
    Signed-off-by: Marcos Ronaldo <marcos.rpj2@gmail.com>
    Signed-off-by: Michel Felipe de Oliveira Ferreira <michel.ferreira@serpro.gov.br>
    Michel Felipe
     

23 Feb, 2016

1 commit

  • Also rewriting the file visualization to work consistently with every
    file type. Here is the overall basic behavior now:
    
      * If the request is passed with view=true, content is displayed
        as an article content.
        * If the file has an inline visualization (like images) it's already
          displayed.
        * If not, a download link is displayed.
      * If the request is passed with view=false, the file is provided
        straight, without any noosfero layout being loaded.
    
      * If the file is private:
        * And the user accesses its public filesystem path, apache (this is
          done by noosfero-apache) will redirect the request to rails
          path so that the rails server will provide it considering
          appropriate permissions.
        * And the user accesses its rails path, rails server will provide as
          well.
      * If the file is public:
        * And the user accesses its public filesystem path, apache will
          provide the file.
        * And the user accesses its rails path, rails server will redirect
          to its public filesystem path so that apache provides the file.
    Rodrigo Souto
     

22 Feb, 2016

1 commit