@CatoTH CatoTH released this Dec 9, 2018 · 39 commits to master since this release

Assets 4
  • 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.

@CatoTH CatoTH released this Nov 17, 2018 · 53 commits to master since this release

Assets 4
  • 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.

@CatoTH CatoTH released this Oct 16, 2018 · 109 commits to master since this release

Assets 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).

@CatoTH CatoTH released this Oct 14, 2018 · 111 commits to master since this release

Assets 4
  • 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.
Pre-release
Pre-release

@CatoTH CatoTH released this Oct 3, 2018 · 134 commits to master since this release

Assets 4
  • 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.

@CatoTH CatoTH released this Sep 15, 2018 · 205 commits to master since this release

Assets 4
  • 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.
Sep 8, 2018
Bugfix font size

@CatoTH CatoTH released this Sep 2, 2018 · 217 commits to master since this release

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

@CatoTH CatoTH released this Sep 1, 2018 · 226 commits to master since this release

Assets 4

Version 4.0.0 (2018-09-01)

  • Antragsgrün now includes an update mechanism to install new versions from the web interface.
  • The comment system was improved:
    • It is now possible to reply to comments. The replies will be displayed indented below the main comment.
    • The layout of comments is more compact and less visually cluttered.
    • Now it is easier and more flexible to get e-mail-notifications about comments to motions/amendments: when writing comments, it is possible to opt-in to e-mail-notifications about new comments, either for comments to the same motion, for direct replies, and for all comments to the same consultation.
  • The system for editorial texts (like the legal pages or the welcome message) has been overhauled. New features include:
    • It is now possible to upload images using drag&drop when editing editorial texts.
    • It is now possible to create new editorial content pages, optionally linked to from the main menu.
    • It is now possible to add a login message, that appears above the login screen.
  • Instead of only setting the deadline for motions and amendments, there is now an alternative complex phase system with time ranges for motions, amendments, comments and merging amendments into motions, including a debugging tool for admins.
  • The RSS-feeds are now embedded in the header of the consultation page, making them auto-discoverable.
  • If the "amendment merging" mode of a motion is used just to create a new version of the motion, and no amendments actually exist, the process is now greatly simplified.
  • There now can be more than only one "pink create-motion button" in the sidebar. This can be configured on a per-motion-type basis.
  • There are first beginnings of a plugin system based on Yii2's module concept. It's still subject to major changes, though.
  • On the user account page, there now is a tool to export all user data in JSON-format.
  • It is easier to create PDF-based application motion types, as there now is a template for that when creating a new motion type.
  • Selecting the site layout and PDF layout is now done using thumbnails of the layouts, not by their rather cryptic names.
  • The PDF-introduction of a motion can now be set on a per-motion-type basis.
  • The sender name and reply-to of sent emails can now be set on a per-consultation-base (it was on a per-site-base before).
  • The logo of a consultation can (and has to be) uploaded now in the consultation settings. This enables using it as PDF-logo, and prevents mixed secure content warnings.
  • It is now possible to specify the visibility of the page in search engines / set the noindex-tag. By default, only the home page is indexable. Alternatively, everything or nothing can be set to indexable.
  • In the regular motion view, it is now possible to go to a specific line by simply typing in the line number and pressing enter.
  • Add a way to include the commercial FPDI-PDF-plugin.
  • It is now possible to restrict the access to one consultation to specific users, while leaving other consultations open for all.
  • In installations that use SAML/Grünes Netz for authentication, it is now possible to restrict the login to a specified list of users.
  • Improve compatibility with reverse proxies.
  • The default consultation path is not "std12345678" (random number) anymore, bust simply "std".
  • When creating a motion and it is not clear what agenda item it should belong to, the agenda item can now be set from the motion creation form.
  • Image and PDF upload fields in motions / applications now show the maximum file size.
  • When creating a motion, optional fields are now marked as such.
  • Bugfix: Improved compatibility with servers that do not support URL rewriting ("pretty" URLs).
  • Bugfix: When creating a new version of a motion and changing the motion type of this new motion afterwards, the changes between the two versions could not be displayed.
  • Bugfix: When Latex was not activated, new consultations were created with no PDF after saving the motion type the first time.
  • Bugfix: The list of tags to select when creating a motion is now sorted in the same way as in the consultation setting page.
  • Bugfix: When a section was completely empty in a motion and a amendment was created inserting something to this section, the original motion could not be displayed anymore.
  • Bugfix: When a motion type's create setting was set to "nobody", editing already created motions as an admin was impossible.
  • Bugfix: When creating a new version of a motion, it was not possible to merge none of the amendments.
  • Bugfix: After changing the line length, the old line was still in the cache for LaTeX-based PDF rendering.
  • Bugfix: When submitting an application containing a photo and the admin enabled submission confirmations by e-mail, the confirmation e-mail did not corretly link to the image.
  • Obsolete: The old, non-fuctional OpenID-based Wurzelwerk-login was removed.
  • Obsolete: The facebook image feature was removed, as nobody used it and was rather tricky to use anyway.
Pre-release
Pre-release

@CatoTH CatoTH released this Aug 18, 2018 · 241 commits to master since this release

Assets 4
  • When creating a motion and it is not clear what agenda item it should belong to, the agenda item can now be set from the motion creation form.
  • Bugfix: Improved compatibility with servers that do not support URL rewriting ("pretty" URLs).