| Auszug |
|---|
|
Nuclos nuclet file version: transferVersion, compatibility, import failed, old installer, Docker Hub. |
Language: Deutsch · English
Nuclet file version
Which Nuclos version supports which nuclet file version – plus a path for too-old files.
| Status |
|---|
| colour | Blue |
|---|
| title | Administrator |
|---|
|
| Status |
|---|
| colour | Green |
|---|
| title | Stand: Jul 2026 |
|---|
|
| Status |
|---|
| colour | Grey |
|---|
| title | gilt fuer Nuclos 4.2026.x |
|---|
|
Why file versions?
A nuclet can only be imported if its file version is supported by the installed Nuclos version. The version is kept stable as long as possible but may be raised by data model migrations.
| Nuclet file version | Nuclos from | to |
|---|
| 1 | – | 3.7 |
| 2 | 3.8 | 3.15 |
| 3 | 4.0 | 4.11 |
| 4 | 4.12 | 4.17 |
| 5 | 4.18 | 4.18 |
| 6 | 4.19 | – |
Determine the file version
Rename the nuclet file to nuclet.zip, unpack it and open nuclet.xml – the version is at the top under transferVersion:
| Codeblock |
|---|
|
<root>
<transferVersion>5</transferVersion>
... |
An incompatible version produces:
| Codeblock |
|---|
|
Import of nuclet failed: Found file format version-{n}. This Nuclos supports only version-{n} |
Nuclet with a too-old file version
Obtain an installer of a compatible version (for version 4 e.g. 4.17 – always the highest Nuclos version of a file version). Install into an empty schema, import the nuclet, then update with a current installer; the schema is migrated on start. Afterwards re-export the nuclet – it now has the current file version.
| Tipp |
|---|
|
Old installers (e.g. 4.18) can often be found on Docker Hub. Copy the installer out of the image like this: |
| Codeblock |
|---|
|
docker create --name tmp-nuc-4.18 nuccess/nuclos:4.18.3
docker cp tmp-nuc-4.18:/opt/nuclos/update/backup/nuclos-4.18.3-installer-generic.jar nuclos-4.18.3-installer-generic.jar |
Related pages
