Skip to content

v1.37 A release coincidental with AoIR 2023

Compare
Choose a tag to compare
@stijn-uva stijn-uva released this 25 Oct 14:27
· 430 commits to master since this release
0de7baf

⚠️ Please follow these instructions for upgrading if you have trouble upgrading to the latest version of 4CAT. ⚠️
We also recommend reading the instructions above if you are running 4CAT via Docker and have in any way deviated from the default set-up.

Otherwise, you can upgrade 4CAT via the 'Restart or upgrade' button in the Control Panel. This release of 4CAT incorporates the following features and fixes:

Processors

  • Added a 'top hashtags' processor for datasets that contain hashtags (this is a preset for the 'count values' processor)
  • Added more configuration options for the image wall processors to limit how large datasets can be
  • Fixed a bug that made the co-link processor crash when used with particularly small datasets
  • Fixed various issues with processing data via the DMI Service Manager

Data sources

  • Data parsers for data imported from Zeeschuimer have been updated to allow data captured from the current version of the supported platforms.
  • Added a data source that allows importing datasets from other 4CAT servers (#352, #375). This is not enabled by default but can be enabled in the Control Panel.
  • Fixed an issue where CSV files would erroneously be detected as having no header rows upon importing them (#392)
  • Fixed a number of issues with Telegram data parsing (#368, #371)

Deployment and configuration

  • 4CAT will now update Python libraries to their latest compatible version when running migrate.py or upgrading via the control panel.
  • Docker images are now published for both ARM and x64 processor architectures (#392)
  • Added a button to the 'Restart or upgrade' control panel page to restart only the front-end
  • Added the option to migrate to a development branch of 4CAT via the control panel's "Upgrade" page. This requires enabling the 'Can upgrade to development branch' privilege in user settings before it is available.
  • Fixed bugs with restarting the 4CAT front-end via the control panel when running via Apache, gunicorn or uwsgi
  • Fixed a bug where generated URLs could have the wrong scheme when running 4CAT behind a reverse proxy
  • Fixed a race condition that could cause the front-end container to crash on start-up when using 4CAT via Docker (#378)
  • Fixed a potential issue when installing 4CAT via Docker with the latest version of the Postgres image (#382)

Interface

  • Added a panel to the control panel which shows the active user tags for the currently logged in user
  • Added a page to the control panel that allows creating many users at once by uploading a CSV file with user data
  • Added a 'User Interface' category to the Settings panel to configure 4CAT's interface, for example to show in-line dataset previews and what to use as the 4CAT 'home page' (#380)
  • Added the option for users to now receive an e-mail alert when their dataset is completed, which can be enabled via the control panel through the 'Show email when complete option' option in the 'User interface' settings (#329, #385)
  • Added an indication of the precise place in the queue for queued datasets (#239)
  • Added the option to force a particular configuration tag by passing a specific HTTP header. This can be used to serve a different configuration of 4CAT depending on e.g. the used domain name, or other factors as determined by the reverse proxy serving 4CAT (#380)
  • Fixed an issue with the manipulation of user tags via the control panel (#383, #384)
  • Fixed an issue with changing the ownership for many datasets at once via the 'Bulk dataset management' page
  • Fixed an issue that allowed the 'About' page to appear twice in the site navigation