The 4CAT Capture and Analysis Toolkit provides modular data capture & analysis for a variety of social media platforms.
⚠️ 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.
When updating a Docker-based 4CAT, the front-end interface may fail to restart properly, marked by an error message like 'Error upgrading front-end container' in the restart log. In this case please run an upgrade via Docker Desktop or the command line as indicated on this page.
Otherwise, you can upgrade 4CAT via the 'Restart or upgrade' button in the Control Panel. This release of 4CAT incorporates the following fixes and improvements:
⚠️ 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, or if you encounter issues when upgrading via the web UI.
Otherwise, you can upgrade 4CAT via the 'Restart or upgrade' button in the Control Panel. This release of 4CAT incorporates the following fixes and improvements:
user:
tag would delete all user:
tags (9b4981d8c7358f31ed65d9f161d556e578389801)Full Changelog: https://github.com/digitalmethodsinitiative/4cat/compare/v1.40...v1.41
⚠️ 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.
When updating a Docker-based 4CAT, upgrading to this version may fail or appear to not have made any changes the first time. This is due to a bug fixed in this version. If this happens to you, follow the 'Docker - how to upgrade with command' instructions via the link above.
Otherwise, you can upgrade 4CAT via the 'Restart or upgrade' button in the Control Panel. This release of 4CAT incorporates the following fixes and improvements:
⚠️ 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 fixes and improvements:
9gag
)jobid
column of the jobs table to BIGINT to avoid issues with long-running 4CAT servers (3414a964ebc19949897317c1af7600abdce26da6)⚠️ 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 fix for a bug introduced in the previous release, v1.37:
:warning: Please follow these instructions for upgrading if you have trouble upgrading to the latest version of 4CAT. :warning: 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:
migrate.py
or upgrading via the control panel.⚠️ 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 fixes for bugs introduced in the previous release, v1.35:
Additionally, this release incorporates the following features and fixes:
This release of 4CAT fixes the following bugs that were introduced in the previous release, v1.34:
NULL
or an empty string; it should now always be an empty stringThis release changes the way dataset expiration works, to avoid situations where it is ambiguous whether a dataset should 'expire' and be deleted automatically. Expiration can now only be configured per data source, not globally. To make this easier controls have been added to the control panel to set expiration time for multiple data sources at once, and to 'keep' or 'expire' datasets in bulk.
⚠️ If you are upgrading 4CAT and had datasets or data sources set to expire, 4CAT will automatically disable all expiration ⚠️ to avoid datasets expiring inadvertently. Please inspect the relevant settings and adjust as needed after upgrading. You can find the controls at the 'Data sources' tab in the 4CAT settings and the 'Dataset bulk management' page, both in the control panel.
Additionally, this release of 4CAT incorporates the following new features and fixes:
link_url
to the CSV export of LinkedIn datasets containing the link embedded in a postis_withheld
to the CSV export of Twitter datasets imported with Zeeschuimer indicating if a tweet was withheld (withheld tweets could previously crash data exports)⚠️ Docker 4CAT releases v1.30 to v1.33 have a bug where upgrading 4CAT would never complete due to issues fetching the latest version. Please follow these instructions for upgrading if you are running one of these versions. You can find your 4CAT version by going to the Control Panel and clicking the 'Restart or Upgrade' button. ⚠️
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 new features and fixes:
--branch
command line argument to migrate.py to allow migrating to a specific git repository branchThis hotfix release fixes the following bug in the previously released v1.32:
Instructions for upgrading can be found on the wiki.