Finetuned dutch translation
update_data() should *not* swallow exceptions

in our infrastructure in particular (psql) this will only
lead to hard to debug errors like the below (in the next statement).
better to raise the error when it happens.

update_data() is only called in the chart_update() command anyway,
so no further consequences are predicted.

django.db.utils.DatabaseError: current transaction is aborted, commands ignored until end of transaction block
main_index() is login_required
Added additional CMS Content placeholders
Modified group management column headers for consistency
Modified group management show history/change name links
Added confirmation dialog before deleting users on group management
Update of client-side epidb scripts.
Merge remote branch 'origin/master'
Contest up & until dec (not nov) 15th
Removed doubled messages

this appears to be a weird artifact of using if statements combined with the
context variable messages
Added check on 'intake' on 'mark as healthy' button
Revert "Added new case definitions to the translation files"

This reverts commit 298e5cf5351e4f726d1bdc1c59a884e8330644da.
Because that commit simply copied already-existing information
leading to compilation errors

Conflicts (solved):
	locale/nl/LC_MESSAGES/django.po
Compiled translations
Adapted case definitions for multiple choice

Question Q11 has become a multiple choice question
Rss shows only published news items
Update locale/pt/LC_MESSAGES/django.po
reverting the changes in the survery_run_clean template for mobile
Revert "Adapted case definitions for multiple choice"

This reverts commit 9abbd6f73a9fe91f113f4f1dd139a308aaa37cc9.
Counter shows only this year's intake