18 Sep, 2014
1 commit
12 Sep, 2014
21 commits
-
This will force the latest ruby1.8 (which provides an alternative entry for /usr/bin/ruby) to be configured before Noosfero is stopped. This is hopefully the final touch to have clean upgrades from squeeze+noosfero-0.47 to wheezy+noosfero-1.0, at least with regards to proper package management.
-
This reverts commit 9acab92a5a40244819b27fd5d9cb4a6b71fcb575, which does not fix anything. On the contrary, it makes the situation a lot worse.
-
We need ruby >= 1.9.3 to be already configured (hopefully) before even starting to replace the old noosfero package; before ruby is fully configured, there is no /usr/bin/ruby because of the update-alternatives dance, which only finishes right before dpkg is done configuring ruby.
-
Ai1954 manage friends shows the wrong number of persosns per page Changed the number of friends shown per page, to improve usability. ActionItem1954: http://noosfero.org/Development/ActionItem1954 See merge request !219
-
Ai3300: In rails3, plugins' paths are being appended See merge request !317
-
This feature was removed and the test was not updated. It makes no sense for an article block displaying a blog to display pagination links.
-
At some point the display color became an arbitrary color and the tests were never updated.
-
It was breaking the integration tests (messing with internals of an old version of exception_notification), and the tests are testing that exception_notification actually works which is _not_ a job for the Noosfero test suite.
-
That is already done in lib/noosfero/i18n.rb
11 Sep, 2014
8 commits
-
Conflicts: AUTHORS app/controllers/public/content_viewer_controller.rb debian/changelog lib/noosfero.rb po/de/noosfero.po po/eo/noosfero.po po/es/noosfero.po po/fr/noosfero.po po/hy/noosfero.po po/it/noosfero.po po/noosfero.pot po/pt/noosfero.po po/ru/noosfero.po
-
No code on initializers should ever touch the database. During upgrades, that code will run when running migrations, i.e. while the database is still outdated.
-
Such memory consumption logging should be done on the processes processing requests, and not on the delayed job processes.
-
AI3286
-
Instead of create another hotspot that does the same thing, use the existing one. If the demand for separation appears in the future than we may do it.
-
When the content being displayed is from the user, we should not display the "publish on my profile" option. The same goes for the "publish on communities" option if the user has no communities or the "publish on portal community" option if the environment has no portal community. If none of this options is available the spread button is also not displayed.
09 Sep, 2014
10 commits
-
Fix support of custom layout in themes http://noosfero.org/Development/ActionItem3299 See merge request !315
-
The superclass methos alteady returns true anyway.
-
'def editable' was removed because it was overriding (of Block) and setting to false AI3298
-
shop-cart-form: displays form in colorbox https://noosfero.org/Development/ActionItem3288 See merge request !312
-
Fix path and init loading order to be as in noosfero-rails2 http://noosfero.org/Development/ActionItem3294 See merge request !311