hotfix-4820, 2022-01-31 3am.tar

Only apply these hotfixes if you absolutely need them and cannot wait until the next release of Composr (releases are more reliable and strictly tested). We provide no guarantee that hotfixes will work; they may even break your site especially if a hotfix depends on another hotfix. Always make a site backup if you attempt to apply a hotfix.

As of Composr version 11, the recommended way to apply a hotfix is by following the same steps as an upgrade:

1. Download the hotfix into the data_custom folder of your Composr installation directory
2. Back up your site
3. Go to yourbaseurl/upgrader.php
4. When you get to the 'Transfer across new/updated files' step, use the hotfix that you downloaded.
5. The upgrader will automatically apply hotfix files, skipping any files belonging to addons that you do not have installed, and also skipping hotfix files that are older than the files on disk
6. Run a database upgrade if prompted
7. You may wish to run a file integrity scan and resolve issues.

For Composr version 10, manually extract the files (e.g., using 7-Zip) and overwrite files in your Composr installation that are older than the ones in the hotfix (check the file modification date/time). Skip hotfix files that do not exist in your installation.

Fixed MANTIS-4820 (error_occurred notifications triggering issue on dev-mode) (d4e4b33c) · Commits · Composr ecosystem / Composr · GitLab