Known issues when updating i-doit

This article documents known issues that may occur when updating to or from specific i-doit versions, along with their solutions.

Before updating

The following points should be checked before every update:

• Create a backup — fully back up the database and file system
• Check system requirements — verify PHP, MariaDB, and Apache versions against the target version compatibility matrix
• Check add-on compatibility — many add-ons have minimum version requirements per i-doit release
• Ensure write permissions — the web server user (e.g. www-data) needs write access to the i-doit directory

Updating to version 38

Add-on minimum versions

When updating to v38, numerous add-ons must be updated to minimum versions beforehand:

Add-on ZIP files are available for download in the customer portal. Installation is done via the Admin Center under Add-ons > Install/update module.

Gateway Timeout during migration

Symptom: The update aborts with a "Gateway Timeout", especially on large installations.

Cause: Large logbook tables significantly slow down the database migration.

Solution: Timeout errors during logbook migrations can generally be ignored — they are not critical for operation. Run the update again. If the problem persists:

• Increase Apache/Nginx timeout values
• Run the update via Console (bypasses browser timeouts):

sudo -u www-data php console.php update \
    -u admin -p admin \
    -z /path/to/idoit-38-update.zip \
    --v 38

Add-on & Subscription Center does not load

Solution: The server must be able to reach the following addresses:

• crm-gateway.i-doit.com
• lizenzen.i-doit.com
• center.i-doit.com

Adjust firewall rules accordingly.

Updating to version 35 (from version 34)

Crypto hash migration fails

Error message:

Fatal error: Uncaught ArgumentCountError: 4 arguments are required, 2 given
in migrate-system-crypto-hash-to-tenant.php:28

Solution: Install the hotfix i-doit_34_ID-11978_migration-of-crypto-hashes.zip on version 34 before updating to version 35. The hotfix is available in the Knowledge Base hotfix archive.

Updating to version 34

HTTP 500 after update (SM-View add-on)

Error message in web server log:

PHP Fatal error: Declaration of
Symfony\Component\HttpFoundation\ResponseHeaderBag::all(?string $key = null)
must be compatible with
Symfony\Component\HttpFoundation\HeaderBag::all(?string $key = null): array

Cause: SM-View 2024.3.0.2708 is not compatible with i-doit 34.

Solution: Deactivate the SM-View add-on in the Admin Center until a compatible version is available.

Updating to version 33

Functions disappear after update

Symptom: After the update, functions such as the update function itself or the LDAP configuration are missing.

Cause: Placeholder variables in the configuration file were not correctly replaced with values during the update.

Solution: Check and correct the following values in the file .../i-doit/src/config.inc.php:

Correct:

$g_enable_gui_update = '1';
$g_is_cloud = '0';
$g_active_features = [''];

Incorrect (placeholders not resolved):

$g_enable_gui_update = '%config.admin.enable_gui_update%';
$g_is_cloud = '%config.cloud.active%';
$g_active_features = ['%config.active_features.list%'];

Updating from version 28

"Next" button does not work after hotfix

Symptom: After installing hotfix i-doit_28_hotfix_ID-10745.zip, the new version is displayed but clicking "Next" does nothing.

Error in browser console (F12):

Uncaught ReferenceError: open29NoticeHandler is not defined

Solution:

1. Run the update to version 28 again using the updater
2. Download the version 29 update ZIP from the customer portal
3. Extract the ZIP in the i-doit directory
4. Run the update to version 29 using the updater

Updating from version 25-28

Updater shows incorrect target version

Symptom: The updater shows v30 as the next version, when v29 would be correct.

Solution: Manually download the v29 update package from the customer portal and extract it in the i-doit directory.

General issue: "A problem occurred during update" during File-Update

Cause: Missing write permissions on the file system.

Solution by operating system:

Debian/Ubuntu:

cd /var/www/html/
sudo chown www-data:www-data -R .
sudo find . -type d -exec chmod 775 {} \;
sudo find . -type f -exec chmod 664 {} \;

Red Hat Enterprise Linux:

cd /var/www/html/
sudo chown apache:apache -R .
sudo find . -type d -exec chmod 775 {} \;
sudo find . -type f -exec chmod 664 {} \;

SUSE Linux Enterprise Server:

cd /var/www/html/
sudo chown wwwrun:www -R .
sudo find . -type d -exec chmod 775 {} \;
sudo find . -type f -exec chmod 664 {} \;

After the update

• Clear cache: Browser cache (Ctrl+Shift+R) and i-doit cache (Administration > System Tools > Cache)
• Update reports: Administration > System Tools > Cache / Database > Update reports
• Rebuild search index:

sudo -u www-data php console.php search-index -u admin -p admin

Detailed documentation: Installing an update | Known update problems