Known Update Issues
This article lists all known problems when updating from or to a specific i-doit version.
Version 34#
SM-View 2024.3.0.2708 is not compatible with i-doit 34. After the update, an HTTP 500 server error is thrown. Deactivate the add-on in the Admin Center to continue working. The error message in the web server log looks like this:
1 | |
When updating to version 35, if the following error message is logged:
1 | |
Use this hotfix on version 34 to be able to update to version 35.
i-doit_34_ID-11978_migration-of-crypto-hashes.zip
Version 33#
After the update, some functions may disappear, e.g., the update function or the LDAP function. Set the value $g_is_cloud = '0' in the file .../i-doit/src/config.inc.php.
Also check the following variables:
1 2 3 | |
1 2 3 | |
Version 28#
If you have installed the hotfix i-doit_28_hotfix_ID-10745.zip, the new version is displayed. However, clicking Next has no effect. The following error message appears in the browser's developer console (F12):
1 2 3 4 | |
Follow these steps:
- Run the update to version 28 again using the updater.
- Download the update ZIP for version 29 from the Customer Portal.
- Extract the ZIP in the i-doit folder, as described here.
- Run the update to version 29 using the updater.
Version 25 - 28#
The updater incorrectly shows v30 as the next version. Fix the problem using one of the following methods:
- Manually extract the v29 update package into the i-doit folder.
- Use the appropriate hotfix from the Hotfix Archive.
Files cannot be copied#
If the message A problem occurred during update: appears at 4. File-Update, write permissions on the file system are often missing.
Set the file permissions according to your operating system and web server user. The following commands assume a standard installation as described under installation.
1 2 3 4 | |
1 2 3 4 | |
1 2 3 4 | |
Specific file and directory permissions typically do not need to be set.