strapi / nextjs-corporate-starter

Strapi Demo application for Corporate Websites using Next.js
MIT License
966 stars 287 forks source link

seed data has error #7

Closed ahmadjoya closed 1 year ago

ahmadjoya commented 1 year ago

While I am importing the yarn strapi import -f ../seed-data.tar.gz or yarn strapi import -f ../fixed-data.tar.gz

it shows this error:

[2023-04-20 09:33:12.880] error: [FATAL] Invalid schema changes detected during integrity checks (using the strict strategy). Please find a summary of the changes below:
- admin::permission:
  -  exists in destination schema but not in source schema
- admin::user:
  -  exists in destination schema but not in source schema
- admin::role:
  -  exists in destination schema but not in source schema
- admin::api-token:
  -  exists in destination schema but not in source schema
- admin::api-token-permission:
  -  exists in destination schema but not in source schema
- admin::transfer-token:
  -  exists in destination schema but not in source schema
- admin::transfer-token-permission:
  -  exists in destination schema but not in source schema
- plugin::upload.file:
  -  exists in destination schema but not in source schema
- plugin::upload.folder:
  -  exists in destination schema but not in source schema
- plugin::i18n.locale:
  -  exists in destination schema but not in source schema
- plugin::users-permissions.permission:
  -  exists in destination schema but not in source schema
- plugin::users-permissions.role:
  -  exists in destination schema but not in source schema
- plugin::users-permissions.user:
  -  exists in destination schema but not in source schema
- api::article.article:
  -  exists in destination schema but not in source schema
- api::author.author:
  -  exists in destination schema but not in source schema
- api::category.category:
  -  exists in destination schema but not in source schema
- api::global.global:
  -  exists in destination schema but not in source schema
- api::lead-form-submission.lead-form-submission:
  -  exists in destination schema but not in source schema
- api::page.page:
  -  exists in destination schema but not in source schema
- api::product-feature.product-feature:
  -  exists in destination schema but not in source schema
- elements.feature-column:
  -  exists in destination schema but not in source schema
- elements.feature-row:
  -  exists in destination schema but not in source schema
- elements.feature:
  -  exists in destination schema but not in source schema
- elements.footer-section:
  -  exists in destination schema but not in source schema
- elements.logos:
  -  exists in destination schema but not in source schema
- elements.notification-banner:
  -  exists in destination schema but not in source schema
- elements.plan:
  -  exists in destination schema but not in source schema
- elements.testimonial:
  -  exists in destination schema but not in source schema
- layout.footer:
  -  exists in destination schema but not in source schema
- layout.logo:
  -  exists in destination schema but not in source schema
- layout.navbar:
  -  exists in destination schema but not in source schema
- links.button-link:
  -  exists in destination schema but not in source schema
- links.button:
  -  exists in destination schema but not in source schema
- links.link:
  -  exists in destination schema but not in source schema
- links.social-link:
  -  exists in destination schema but not in source schema
- meta.metadata:
  -  exists in destination schema but not in source schema
- sections.bottom-actions:
  -  exists in destination schema but not in source schema
- sections.feature-columns-group:
  -  exists in destination schema but not in source schema
- sections.feature-rows-group:
  -  exists in destination schema but not in source schema
- sections.features:
  -  exists in destination schema but not in source schema
- sections.heading:
  -  exists in destination schema but not in source schema
- sections.hero:
  -  exists in destination schema but not in source schema
- sections.large-video:
  -  exists in destination schema but not in source schema
- sections.lead-form:
  -  exists in destination schema but not in source schema
- sections.pricing:
  -  exists in destination schema but not in source schema
- sections.rich-text:
  -  exists in destination schema but not in source schema
- sections.testimonials-group:
  -  exists in destination schema but not in source schema
- shared.media:
  -  exists in destination schema but not in source schema
- shared.quote:
  -  exists in destination schema but not in source schema
- shared.rich-text:
  -  exists in destination schema but not in source schema
- shared.seo:
  -  exists in destination schema but not in source schema
- shared.slider:
  -  exists in destination schema but not in source schema
- shared.video-embed:
  -  exists in destination schema but not in source schema
Import process failed.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
PaulBratslavsky commented 1 year ago

@ahmadjoya thank you for letting me know, I will double check. BTW did you run yarn build && yard develop before importing data?

ahmadjoya commented 1 year ago

yes I have run them. seems this issue is only for Windows users. because it works in Debian.

Boegie19 commented 1 year ago

@PaulBratslavsky If you update the strapi version you also need to regenerate the seeding file

PaulBratslavsky commented 1 year ago

@Boegie19 thank you for letting me know, I will give that a shot and generate a new seeding file.

PaulBratslavsky commented 1 year ago

I tested the seed file and it worked without issues on my mac m2 @Boegie19 is testing it on windows now.

PaulBratslavsky commented 1 year ago

We confirmed that it is an issue on windows only with DEITS this issue will be fixed in the next release. I will get you a pre-release you can checkout and see if it fixes it. @ahmadjoya

derrickmehaffy commented 1 year ago

Fixed in https://github.com/strapi/strapi/pull/16402 should be out ~monday/tuesday when we make the Strapi hotfix release.

In the meantime you can upgrade your app to this experimental version: 0.0.0-experimental.60006686738ddfbc5089e00904bbb243fb8dcf95