v4.10.1

• Public votings assigned to user groups now also show the users that have not voted yet in the admin view.
• The voting result page now has a full screen mode and does not reload automatically anymore.
• Bugfix: Some constellations of whitespaces and line breaks at the end of list points could lead to problems with amendments.
• Bugfix: When saving binary files to the file system was enabled, copying / moving motions to other consultations broke uploaded images and PDFs.
• Bugfix: If users started to create a motion or amendment but did not confirm them, the draft was visible on the home page, but not accessible.

v4.10.0

• The user permission system was now replaced by user groups.
  • The access to a site is now configured on the standard "consultation settings" page.
  • The previous site access page is now exclusively used to configure users and user groups.
  • There are a few pre-configured user groups with special meanings (Site administrator, consultation administrator, proposed procedure editor, participant).
  • Arbitrary additional groups can be added.
  • Creating motions, amendments, comments and supporting them can be restricted to one or several of these groups.
• The voting functionality was improved in several ways:
  • Votings can now have simple questions that are not attached to any motion or amendment.
  • Votings have different answer options: besides "Yes/No/Abstention", it is now also possible to have simple "Yes/No"- and "Presence"-votings (Roll calls).
  • It is possible to restrict voting to specific user groups.
  • Voting results can be exported into a spreadsheet.
  • Users responding to a "Presence" (Roll call) vote can be assigned to a customer user group, to be eligible for further votings, creating motions/amendments etc.
  • If voting is restricted to one or more user groups, then a quorum can be set that needs to be reached for the voting to be valid.
• Antragsgrün now comes with a plugin to integrate the user administration with OpenSlides:
  • It allows to log in into Antragsgrün using the username/password of an OpenSlides page.
  • Using a separate proxy app, it allows to automatically synchronize users and user groups from OpenSlides to Antragsgrün.
  • It needs to be set up by a system administrator per site.
• The speaking list has a few improvements:
  • The speaking list now has a separate site for users in the menu.
  • Speaking lists supports setting a timer per speaker.
  • One speaking list per agenda item can be created.
• Amendments can now be further restricted to only affect one particular location within one paragraph.
• There are new motion statuses "Quorum reached" and "Quorum missed".
• The CAPTCHA system is reset for a user after a successful login. This solves issues when multiple users are behind the same IP address.
• The full-screen projector now also shows the initiator and status of a motion / amendment.
• The menu at the top of the page was reordered into a more logical order.
• A new e-mail-sending library (Symfony mailer) is used. Amazon SES can now be configured as mailer, too (by editing the config.json directly).
• Bugfix: The button to apply for a speaking list was shown, even if applying was not possible.
• Bugfix: More than 26 numbered list points were not supported for latin character based numbering

v4.9.1

• Bugfix: A modified amendment text as proposed procedure only got shown in the internal list after saving it a second time.
• Bugfix: If both an agenda and a proposed procedure is used, some motions could appear twice on the proposed procedure.
• Bugfix: If an image section was accidentally set as amendable and an amendment was created without changing the image, the PDF could not be rendered.
• Bugfix: Votings could break after a participant has deleted their account.
• Bugfix: If creating statute amendments was restricted to logged in users, the create link did not work properly.
• Compatibility with PHP 8.1

v4.9.0

• Online voting functionality was added. Admins can now define voting blocks, where users can vote on amendments and motions to be adopted or rejected. A documentation about this feature is located at https://sandbox.motion.tools/help#votings .
• Submitted amendments can now optionally have tags, too, if set up in the motion types.
• There now is a full-screen view of motions and amendments, to show them on projectors on live events. It can be activated on the title of the motion/amendment.
• Parts of motions' and in particular applications' motion types can be marked as "non-public", meaning that this information will be only visible for admins and the proposer itself.
• The accessibility was improved in some parts, especially drop-down selections, while reducing the page load time.
• A new amendment numbering scheme was introduced more appropriate for english environments: "M1 A1" (Motion number + Amendment number)
• It is now possible to copy a motion including all its amendments to a different consultation or agenda item without marking the original one as moved.
• To prevent brute force login attempts, a entering a CAPTCHA is now required after three failed login or account recovery attempts. Standalone hosted versions of Antragsgrün can optionally require it for every single login attempt, by adding the loginCaptcha flag to config.json.
• Statute amendments can now be created for an agenda item if the according motion type was set.
• Bugfix: If an amendment was assigned to an agenda item, the agenda item could not be deleted before the amendment was un-assigned first.
• Bugfix: Tabular data, like in applications, were not exported into spreadsheets.
• Bugfix: an empty "Supporting" section was shown in motions and amendments, if only the "liking" function was enabled.
• Bugfix: Some bugs in edge cases with LaTeX-based PDF rendering were solved.
• Bugfix: if fixed font width was specified but no line numbers, then line number placeholders where shown in the text.
• Support for Internet Explorer was dropped.
• PHP-Support: PHP 8.1 is not yet supported, please use PHP 8.0 until support will be added in the next minor version. This is the last version to support PHP 7.2.

v4.8.1

• Bugfix: The consultation page did was not shown when a statute amendment was withdrawn.
• Bugfix: After saving a proposed procedure of an amendment or motion, the selected voting block was not shown.
• Bugfix: If an amendment was assigned to an agenda item explicitly, it still showed up for a second time at the motion in the agenda.
• Bugfix: The REST API didn't work correctly with statute amendments
• Bugfix: To prevent motions that cannot be saved in the backend due to special characters in the motion slug, all slugs are now strictly transliterated to latin characters.

v4.8.0

• Statute amendments are now explicitly supported. They have the following characteristics:
  • Admins can create the base statutes that can be amended. This base text will not be visible regularily.
  • Statute amendments are displayed and created like normal motions. That is, they will be shown like normal motions on the home page and receive a regular prefix like "S1". Their content is using the diff view of amendments, though.
• If PDFs are uploaded as an image in applications, they will be converted to a PNG. Until now, this did not work at all. This only works if ImageMagick is set up on the server.
• When selecting an image for uploading in applications, only supported file types are selectable now.
• Admins can now explicitly assign amendments (including statute amendments) to agenda items, also to agenda items different from their base motion. In this case, they appear like regular motions on the home page.
• Admins can now see an activity log for each motion and amendment, chronologically listing all relevant events for it (supports, comments, proposed procedure changes etc.).
• Admins can now assign motions and amendments to user accounts, e.g. when the motion was created by an admin or an anonymous user before creating an account.
• For amendments, instead of only the condensed change view, it is now also possible to show the changes in the context of the whole motion text, by clicking on the settings icon next to each section headline.
• Motions can now be downloaded as a PDF with all screened amendments embedded inline into the motion text.
• When merging amendments into a motion:
  • Text entered by the admins can now optionally receive a blue color, to distinguish admin-entered text from the base motion or changes made by the amendments.
  • When merging multiple amendments affecting the same passage of a motion, the merging algorithm now tries more aggressively to merge them into the text, relying on the editing person to resolve the conflicts. Previously, it just refused to merge the second amendment and repeated the colliding amendment below the paragraph.
  • Indications about line numbers of the original motion are now shown at the side.
  • Text could be striked through, but that formatting was not saved. It now is.
• As long as the maintenance mode is activated, admins now get an alert on the page about it being active, including a link to the page where they can deactivate it.
• If admins create a motion or amendment in behalf of an user, no confirmation mails about the submission is sent to the user anymore (if confirmation mails are activated in the first place).
• When official supports are collected for a motion or amendments, it is now optionally possible to support them "non-publically". That is, only logged in users can see the names of those supports.
• In the proposed procedure, admins can set internal tags to motions and amendments in order to filter them more efficiently later on in the motion list.
• Export to OpenSlides is now an advanced feature than can be activated in the motion list under "Functionality".
• When notifying an user about a proposed procedure of her motion or amendment, and an editor was set as responsible in the backend and has a Reply-To-E-Mail-address set, then this address will be taken, instead of the address of the editor actually triggering the notification.
• Improvements for consultations with more than a thousand motions / amendments:
  • An internal consultation setting "adminListFilerByMotion" can now be set in the database to separate the admin list into one list per motion.
  • The caching of motion views was improved so that it does not need to be recalculated as often anymore
  • An optional file-based view cache was introduced, configurable by setting "viewCacheFilePath" in the config.json. Its purpose is not to overload Redis with binary data.
• For motion types, it is now possible to deactivate entering a name as proposer altogether, by selecting "No proposer" in the "From"-dropdown of the motion type settings.
• Bugfix: for PDF-only applications, the collective PDF merging all applications could not be generated.
• Bugfix: Uploaded GIFs could not be rendered into application PDFs if LaTeX-based PDF-rendering is used.
• Bugfix: the "reset to original motion text" button when editing an amendment text as admin did not work.
• Bugfix: a rare bug when sending e-mails through sendmail was fixed that could lead to broken links in the mail.
• Bugfix: when editing an amendment that changed a headline, the change to the headline was not marked as edited text

v4.7.1

• Bugfix: If a woman quota was set up in the support collection phase, the notification e-mail to the initiator about the minimum number of supporters did not take into account this quota.
• Bugfix: A motion creation bug was fixed that happened if an organization list drop-down was set up and the "Wurzelwerk / Grünes Netz"-login was used.
• Bugfix: When using LaTeX-based PDF-rendering for applications, the tabular data to the right part of the page looked strange when having multiple lines
• Bugfix: If an amendment changed big parts of an intermediate headline in a motion text, the change was not correctly indicated using the red and green text colors.
• Bugfix: Selecting multiple topics / tags for motions did not work.
• Bugfix: When allowing multiple topics / tags, removing all tags through the admin backend did not work.
• Bugfix: The REST API did not work if the consultation path had a dash in it, followed by a number.
• Bugfix: A (broken) link to a resolution PDF was shown on the home page, even if no PDF was activated for this motion type.
• Bugfix: The supporting section of motions / amendments was partially shown to admins even if it was activated for nobody.

v4.7.0

• WARNING: if you are using a PHP 7.1 or older, then update to PHP 7.3 or newer first before installing this update!
• Speaking lists for live events can now be administered.
  Participants of the event can put themselves on and remove themselves from the speaking list, and the admin can choose and indicate who to speak next on a separate administration page.
  • This is implemented as a "live" feature, which means, no reloading is necessary for either the admin or the users.
  • Speaking lists can either be linear, or use a quota system, e.g. to enable alternating between women and other/open speaking lists.
  • Users can see the current speaker and the waiting list both on the home page (more detailed) and on motion/amendment pages (as a more subtle footer).
  • Admins can add people to the waiting list themselves, and reorder the waiting lists using drag&drop
  • Admins can choose if a qualified login is necessary for users to add themselves on the speaking lists or not.
  • The speaking lists can also be used as a stand-alone-feature, without the need of having motions, amendments or an agenda.
• The wizard for creating new sites and consultations now also offers to create PDF/Text-based applications and speaking lists.
• A new motion section type is implemented: Video Embeds. Using it, users can add links to Videos, for example to support their candidature. If it's a video hosted on Vimeo, Youtube or Facebook, it will be embedded into the application, otherwise a link is shown.
• The pink deadline circle on the consultation is now also shown if multiple motion types with the same deadline exist.
• First, small beginnings of a REST API are implemented, currently with read-only access. It can be enabled in the site component settings. The documentation can be found at docs/openapi.yaml
• Tabular data sections now skip empty fields when displaying them.
• Some texts can now be changed per motion type, to change the wording depending on context. For example, in the "Create a motion" form, instead of the default "Motion or amendment?" text, there can be different explanations for different motion or application types.
• Applications / Candidatures are now only shown in two-column mode until the first embedded PDF or Video appears. It then switches into single-column-layout to make the PDF/video better readable/watchable.
• The URL slug of a motion can now be changed on the admin page.
• Applications (or other motion types with images) now receive a og:image tag for better image detection when sharing the applications.
• Bugfix: If e-mail-notifcations about published motions for the initiating users are set up, but the submission form does not explicitly ask for an e-mail-address, no e-mail was sent. Now, it is sent to the e-mail-address of the user account.
• Bugfix: If an user has previously put her e-mail-address on the e-mail-blocklist, then saving the account settings lead to an error message.
• Bugfix: if the link to a proposed procedure was forwarded, only the proposed status and the accept button was shown, not the modified text of an amendment.
• Internal: the login system now supports plugins for retrieving user accounts from external sources, e.g. CMS systems with an existing user database. As an example, a integration into Drupal/CiviCRM can be found in the plugins/drupal_civicrm-folder.
• Internal: Plugins can now provide custom amendment numberings and add extra settings and data fields for amendments and motions.

v4.6.3 [PHP8]

• Compatibility with PHP 8 / Composer 2.
• Warning: This will be the last release compatible with PHP 7.1. Future releases will require at least PHP 7.2
• Bugfix: Merging amendments into a motion failed if previously an amendment for that motion was deleted that had a modified version.
• Bugfix: When deleting an amendment after adding it to a proposed procedure's voting block, it remained visible within the proposed procedure.
• Resuming a previously saved draft when merging amendments into an motion could fail if in the meantime an amendment has been hadded.

v4.6.2

• Motion types that do not have a text part, for example PDF-uploaded applications or financial reports, can now also have comments, if the permission is set accordingly in the motion type settings.
• SVG images can now be uploaded as logo.
• Some browser warnings regarding cookie settings are resolved.
• TLS-encryption can be set for sending e-mails through SMTP
• Bugfix: LaTeX-based PDF rendering sometime failed or gave wrong line numbering in nested lists.
• Motions embedded into an agenda are now shown, even if they are replaced by a resolution above.
• Bugfix: if a resolution was replaced by a new version of that resolution, but that new version was deleted, the original resolution was still not shown on the home page anymore.
• Bugfix: The box shadow could not be deactivated when customising the layout.
• Updates to core libraries.