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