39d8d6ffb5
There are 2.2.0 and 2.2.1 tags but no built releases and they don't show up in the changelog for 2.2.2 either. Thats fine we can ignore them and upgrade to latest (2.2.4) instead. The changelog for 2.2.4 can be found here: https://github.com/ether/etherpad-lite/blob/v2.2.4/CHANGELOG.md Notable this changes how plugins are loaded into the js shipped to the browser. We should confirm that our plugins are working as expected as part of this update. On the config management side of things there are some small updates to the Dockerfile to sync up with upstream changes to how etherpad is built. We also update the settings json file to configure log type. Note this change was only made to the normal settings file and not the docker settings file upstream so we match that in this change as well. Finally we also update our mod_rewrite rules in apache to prevent new javascript loading locations from being redirected to /p/ inappropriately. Previously we were redirecting foo.min.js to /p/foo.min.js which caused the server to return html instead of js which led to syntax errors. This then resulted in js errors from the ep_headings plugin. It appears this plugin is ancient and no longer maintained and seems to rely on require() functionality that was removed from etherpad in 2.2.2. We switch to the ep_headings2 plugin instead. This will allow us to file bugs against maintained software should problems persist. Fungi tested ep_headings2 against our production db content and things seem to work despite this issue existing [0]. We should upgrade carefully but it seems like things will likely be functional. We should also check if these redirect rules affect meetpad as well. But this can likely be done after the upgrade. [0] https://github.com/ether/ep_headings2/issues/4 Change-Id: I4a907b5170d3612f4525153a0a07c291d6481a92 |
||
---|---|---|
.. | ||
main.yaml |