-
-
Notifications
You must be signed in to change notification settings - Fork 9.2k
Closed
Closed
Copy link
Labels
issue: bugIssue reporting a bugIssue reporting a bugseverity: mediumIf it breaks the basic use of the product but can be worked aroundIf it breaks the basic use of the product but can be worked aroundsource: core:data-transferSource is core/data-transfer packageSource is core/data-transfer packagestatus: pending reproductionWaiting for free time to reproduce the issue, or more informationWaiting for free time to reproduce the issue, or more information
Description
System information
- Node.js version: 16.19.0
- NPM version: 9.3.1
- Strapi version: 4.6.0
- Database: SQLite
- Operating system: Windows 11 Home, 22H2 22621.1194
Describe the bug
When trying to use the new import future of Strapi 4.6.0 I get the error below. This is with barebone Strapi, and with a single content type and a few records, nothing else and no plugins.
error: [FATAL] Invalid schema changes detected during integrity checks (using the strict strategy). Please find a summary of the changes below:
- admin::permission:
- Removed ""
- admin::user:
- Removed ""
- admin::role:
- Removed ""
- admin::api-token:
- Removed ""
- admin::api-token-permission:
- Removed ""
- api::test.test:
- Removed ""
- plugin::upload.file:
- Removed ""
- plugin::upload.folder:
- Removed ""
- plugin::users-permissions.permission:
- Removed ""
- plugin::users-permissions.role:
- Removed ""
- plugin::users-permissions.user:
- Removed ""
- plugin::i18n.locale:
- Removed ""
Steps to reproduce the behavior
- Install a new instance of the latest Strapi version.
- Make a simple content type and some records.
- Export the data with
npm run strapi export -- --file test --no-encrypt. - Add a few records.
- Import the old data with
npm run strapi import -- -f test.tar.gz.
Expected behavior
The data should be successfully imported.
Additional context
I have the issue with Yarn also, and I have tried to import the data to an empty and new Strapi instance, but I have the same issue. I have also experienced the issue with a PostgreSQL database.
nicosh
Metadata
Metadata
Assignees
Labels
issue: bugIssue reporting a bugIssue reporting a bugseverity: mediumIf it breaks the basic use of the product but can be worked aroundIf it breaks the basic use of the product but can be worked aroundsource: core:data-transferSource is core/data-transfer packageSource is core/data-transfer packagestatus: pending reproductionWaiting for free time to reproduce the issue, or more informationWaiting for free time to reproduce the issue, or more information
Type
Projects
Status
Fixed/Shipped