v4.2.1

• Bugfix: logos whose filename had special characters were not displayed in the generated PDF.
• Bugfix: When uploading a PDF for an application as not-logged-in user, the PDF was not displayed correctly in the confirmation view.
• Bugfix: Tags containing an ampersand (&) were double-encoded. This bugfix only affects newly created tags.
• Bugfix: If comments were deleted by the user, this resulted in rather awkward entries in the activity log.
• Bugfix: The styling of the links in the sidebar when editing motions or amendments was inconsistent.
• The list of admin email addresses for notifications in the consultation settings can now be separated both by commas and semicolons.
• Multi-Site mode: it is now possible to activate plugins on a per-subdomain basis.
• Multi-Site mode: If no Reply-To is set in a consultation, the Admin's email address will be set as Reply-To for outgoing e-mails.

v4.2.0

• It is now possible to modify the layout of Antragsgrün, e.g. by choosing custom colors or uploading a background image. To create a custom theme, go to "Settings" -> "This consultation" -> "Custom theme".
• When logged in, users can now add private notes to each motion, amendment and motion paragraph.
• If a site is set to be accessible only for a closed list of users, there is now an option for users to apply for this list. The admin will receive an e-mail in this case and will be able to accept or reject this request.
• Administrators can now specifiy if only natural persons, only organizations or both can submit new motions and amendments. Default is both.
• Improvements regarding uploaded images:
  • Images uploaded at one consultation can now be used in other consultations of the same site as well.
  • Distorted images in content pages are now prevented.
  • Instead of only uploading new consultation logos, the logo can now also be chosen from the already uploaded images.
  • Bugfix: The logo of a consultation is now also shown on the login page, if the consultation is only accessible for logged-in users.
  • Bugfix: The uploaded logo of a consultation was not shown on some generated PDFs where it was actually intended to.
• Some internal libraries (Yii, Bootstrap) were updated.
• Bugfix: if an admin of a consultation was deleted without revoking the admin permissions first, the permission page could not be rendered anymore.
• Bugfix: In the PDF-collection containing all motions, the header page of a motion contained the status header of the previous motion, if the PHP-based PDF-renderer was used.
• Bugfix: Exporting the PDF-collection as ZIP file did not work for the PHP-based PDF-renderer.
• Bugfix: Merging amendments produced an error in some cases with many amendments.
• Bugfix: Amendments to motions with numbered lists (OLs) behaved incorrectly, especially when merging them into the motion.

v4.2.0rc1

• It is now possible to modify the layout of Antragsgrün, e.g. by choosing custom colors or uploading a background image. To create a custom theme, go to "Settings" -> "This consultation" -> "Custom theme".
• When logged in, users can now add private notes to each motion, amendment and motion paragraph.
• Improvements regarding uploaded images:
  • Images uploaded at one consultation can now be used in other consultations of the same site as well.
  • Distorted images in content pages are now prevented.
  • Instead of only uploading new consultation logos, the logo can now also be chosen from the already uploaded images.
• Bugfix: if an admin of a consultation was deleted without revoking the admin permissions first, the permission page could not be rendered anymore.
• Bugfix: In the PDF-collection containing all motions, the header page of a motion contained the status header of the previous motion, if the PHP-based PDF-renderer was used.
• Bugfix: Exporting the PDF-collection as ZIP file did not work for the PHP-based PDF-renderer.

v4.1.1

• In the list of consultations, the newest consultation now appears at the top.
• Clicking on changes in the public version of a merging draft now always opens a tooltip with the summary of the amendment, including the proposers of that amendment.
• The custom status string is now also shown in the admin motion list.
• When administering the list of users eligible to access a consultation, it is now possible to completely remove an user again.
• System administrators can now delete user accounts from the site-wide user list.
• Bugfix: the date of the last saved draft when merging motions was not set correctly on Safari.

v4.1.0

• Several improvements regarding applications, especially the generated PDFs:
  • Motion types can now force motion titles to have a certain beginning, like "Application: ".
  • A new PDF template is introduced specifically for applications, if the LaTeX-based PDF-renderer is used.
  • For each section of a motion type, it is now possible to specify if the title will be explicitly printed in the PDF of not.
  • If the uploaded image is way too big (bigger than 1000x2000px), it is resized to keep the size of the PDF at a reasonable size.
• Two new statuses are introduced: "Resoluton" and "Resolution (preliminary)". Motions of these states...
  • are shown on the consultation home page separately in a slightly different view (initiators are not mentioned anymore).
  • have a different header as regular motions in the web- and the PDF-view.
  • can neither have amendments nor comments.
• Several improvements regarding merging amendments into motions / creating the final motion version:
  • When editing the merged view with the amendments' change inlined into the text, this draft can be exported into a PDF to document the merging process.
  • After creating the final text, administrators can decide if the new version of this motion is a regular motion again, or a (preliminary) resolution.
  • Bugfix: If an amendment had certain statuses, it was selectable for merging, but was not actually merged then.
• Several changes regarding the proposed procedures:
  • Proposed procedures are now an optional functionality per motion type. They are disabled by default.
  • When exporting the proposed procedure list into ODS, there is now an option to also include the comments or to only include public visible proposed procedures.
  • When sending a notification to users regarding a proposed procedure, the content of the mail can now be modified by the person sending the notification.
  • If an amendment is obsoleted by another amendment with a proposed modification, this modification is also shown in the context of the (proposed) obsoleted amendment.
  • Admins can set a proposal as being accepted by the user. (This is getting logged)
  • Bugfix: It was not possible to delete admin comments in the proposed procedure.
  • Buffix: Prevent a bug when creating a proposed procedure that collides with another amendment.
• When creating a motion, the confirmation page now shows a preview of the generated PDF.
• In the initiator form, the resolution date for organizations submitting a motion is now optional. An additional optional field to add one's gender was added.
• The admin interface for adding/removing supporters of a motion/amendment now has a function to copy the full list of supporters to the clipboard in a format suitable to paste it into the full-text field later on (to easily transfer the supporter list from one motion to a new one).
• The diff view in amendments now usually show the whole affected line, instead of cutting off the line after the last changed word, giving some more context to the change.
• Add an option to enforce a confirmation checkbox on registration.
• The performance of the admin motion list was improved for large installations (> 1000 amendments), by reducing the number of database queries.
• Bugfix: When a motion type was created from the scratch and motion sections positioned right were added, the layout didn't switch to two-column mode.
• Bugfix: When an optional image was not uploaded, the LaTeX-based PDF export did not work.
• Bugfix: Prevent broken sites when too long consultation titles are entered.
• Bugfix: Under some circumstances, a motion assigned to an agenda item did not appear to be assigned correctly in the consultation home page.
• Internal: translatable strings can now include a comment / description which will be displayed in the translation page.

v4.0.4

• Bugfix: Creating the proposed procedure list could fail.
• Bugfix: A ODS-list could not be exported if a motion had no initiators.
• Bugfix: Another bug regarding nested list items and line numbers in PDF generation was fixed.
• If no proposed procedure is set, the amendment merging page now preselects all amendments for merging (except for global alternatives).

v4.0.3

• Bugfix: in nested lists in the PHP-based PDF renderer, the line numbers were not aligned correctly to the lines.
• Bugfix: added extra safeguards to prevent stale popovers when merging amendments into motions.

v4.1.0b1

• Several improvements regarding applications, especially the generated PDFs:
  • Motion types can now force motion titles to have a certain beginning, like "Application: ".
  • A new PDF template is introduced specifically for applications, if the LaTeX-based PDF-renderer is used.
  • For each section of a motion type, it is now possible to specify if the title will be explicitly printed in the PDF of not.
  • If the uploaded image is way too big (bigger than 1000x2000px), it is resized to keep the size of the PDF at a reasonable size.
• Two new statuses are introduced: "Resoluton" and "Resolution (preliminary)". Motions of these states...
  • are shown on the consultation home page separately in a slightly different view (initiators are not mentioned anymore).
  • have a different header as regular motions in the web- and the PDF-view.
  • can neither have amendments nor comments.
• Several improvements regarding merging amendments into motions / creating the final motion version:
  • When editing the merged view with the amendments' change inlined into the text, this draft can be exported into a PDF to document the merging process.
  • After creating the final text, administrators can decide if the new version of this motion is a regular motion again, or a (preliminary) resolution.
• When creating a motion, the confirmation page now shows a preview of the generated PDF.
• In the initiator form, the resolution date for organizations submitting a motion is now optional. An additional optional field to add one's gender was added.
• When exporting the proposed procedure list into ODS, there is now an option to also include the comments.
• Bugfix: When a motion type was created from the scratch and motion sections positioned right were added, the layout didn't switch to two-column mode.
• Bugfix: When an optional image was not uploaded, the LaTeX-based PDF export did not work.
• Internal: translatable strings can now include a comment / description which will be displayed in the translation page.

v4.0.2

• Bugfix: The PDF export of applications failed if a tabular data section was added in the motion, but no data rows were set.
• Bugfix: Underlined text was not rendered as such in the PHP-based PDF renderer.
• The WYSIWYG-editor CKEDITOR was updated, including some bug fixes.
• Temporary files for PDF and ODS generation are not stored in /tmp/ anymore, as there are hosters that block access to this directory. Instead, runtime/tmp is used.
• In the installation, host names including ports (like localhost:3306) are now supported for the database connection.

v4.0.1

• Bugfix: Motion comment tables were not created correctly when MySQL tables names are case-sensitive.