30 Sep, 2015
1 commit
-
Windows systems with pt_br have problem in exporting CSV with comma as delimiter through Excel, so to improve compatibility I decided to loop through delimiter types when parsing and importing recipients. Since I try different types of delimiter and stick with the first one that gives me a valid content, it's always possible (albeit unlikely) the file can be parsed incorrectly.
29 Sep, 2015
4 commits
28 Sep, 2015
5 commits
-
The plugin still has some structural problems
-
Adding a Dockerfile that builds de development environment. I pushed the first built machine with this Dockerfile on the following repository: https://hub.docker.com/r/noosfero/dev/ I'm assuming the responsibility on maintaining this image updated with the lastest master branch. Whoever feels like help maintaining it send an email to noosfero-dev requesting access to the repository.
26 Sep, 2015
8 commits
-
Notification plugin code improvments Improve Environment Notification plugin's code to attempt to [Plugins Architecture Guidelines](http://noosfero.org/bin/view/Development/PluginsArchitecture) The main improvments is related to js and css scope as suggested in MR !650. See merge request !680
-
Split application.css into several partials Keeped controllers/views structure See merge request !666
-
Keeped controllers/views structure
-
This reverts commit 83c318e66c66d82671cccaf3acc7f29c2bacf8d2.
-
This is useful for testing packages, since regular packages created with `noosfero:deb` would have the same version number as the last release ondes.
25 Sep, 2015
10 commits
-
Fix: force utf-8 on content from external feeds Error with feeds encoded with 8-bit ascii: "#<Encoding::CompatibilityError: incompatible encoding regexp match (UTF-8 regexp with ASCII-8BIT string)>" Example of feed that wasn't working: http://www.bahiacooperativo.coop.br/rss/feed.xml See merge request !677
-
Notification plugin A plugin that allows write notifications and display them on the home page. Description: - The environment admin can write notifications through this plugin. - The notification is displayed only on the homepage. - An admin can manage a notification lifecycle by activating or deactivating it. - Users can block a notification, so it won't appear anymore. - Unlogged in users see only the last notification update. - Unlogged in users can not close notification. - There are 4 categories of notifications, each with a specific color. Danger (Red) Information (Blue) Success (Green) Warning (Yellow) See merge request !650 -
Signed-off-by: Arthur Del Esposte <arthurmde@gmail.com> Signed-off-by: Eduardo Vital <vitaldu@gmail.com> Signed-off-by: Gabriela Navarro <navarro1703@gmail.com> Signed-off-by: Fabio Teixeira <fabio1079@gmail.com> Signed-off-by: Jéssica Cristina <jessica.cris1127@gmail.com> Signed-off-by: Simião Carvalho <simiaosimis@gmail.com> Signed-off-by: Victor Navarro <victor.matias.navarro@gmail.com> Signed-off-by: Pedro de Lyra <pedrodelyra@gmail.com> Signed-off-by: Tallys Martins <tallysmartins@yahoo.com.br>
-
Error with feeds encoded with 8-bit ascii: "#<Encoding::CompatibilityError: incompatible encoding regexp match (UTF-8 regexp with ASCII-8BIT string)>"
-
Also fixes another small mistake in pt translation
-
Allow user to remove main image for article or profile Right now if you add an image for a profile or an article, you can change the image but you can't remove it. With this patch the user can remove a profile's or article's image just like the user removes a blog's cover image. To achieve that, this patch makes the removal mechanism part of the `#file_field_or_thumbnail` helper. See merge request !665
24 Sep, 2015
1 commit
-
Additional improvements include: - Makes 'Remove Image' checkbox optional - Very ugly css hack to hide duplicated labels in some forms. I couldn't find another way to avoid the labels generated by labelled_form_for nor could I skip adding labels inside the helper since it's supposed to be generic.
23 Sep, 2015
1 commit
-
Currently translated at 99.7% (2124 of 2129 strings)
18 Sep, 2015
1 commit
-
This will hopefully prevent users who are creating forms for e.g. registration for an event from adding fields for name and email, which will already be added by default.
17 Sep, 2015
2 commits
-
Currently translated at 73.2% (1528 of 2086 strings)
16 Sep, 2015
1 commit
15 Sep, 2015
6 commits
-
As talked with terceiro, it is not a good idea to depend on ENV vars
-
you never know, someone might very well actually have a root@ email ...
-
- PT translations for "Enable appearance editing by users" feature
