Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[BUG] Export Function Exports Full Database Instead of Specific Collections or Single Types. #166

Open
VeckansE opened this issue Jan 12, 2024 · 2 comments · May be fixed by #171
Open

[BUG] Export Function Exports Full Database Instead of Specific Collections or Single Types. #166

VeckansE opened this issue Jan 12, 2024 · 2 comments · May be fixed by #171
Assignees
@Baboo7

Comments

@VeckansE
Copy link

The export function only exports the full database and not the specific collection-type or single-type

To Reproduce
Install strapi v4.17.0

  1. Go to a collection
  2. Click export
  3. Notice that the header says
image

This issue appears to stem from a change in the location pathname from.
admin/content-manager/collectionType/plugin::users-permissions.user
into
admin/content-manager/collection-types/plugin::users-permissions.user

and can be fixed by updating.

const matches = pathname.match(/content-manager\/(collectionType|singleType)\/([a-zA-Z0-9\-:_.]*)/);

into

const matches = pathname.match(/content-manager\/(collection-types|single-types)\/([a-zA-Z0-9\-:_.]*)/);

in useSlug

😃
@VeckansE VeckansE changed the title Export Function Exports Full Database Instead of Specific Collections or Single Types. [BUG] Export Function Exports Full Database Instead of Specific Collections or Single Types. Jan 12, 2024
@fmann
Copy link

fmann commented Jan 15, 2024

I was having CSV imports fail in Strapi 4.17.0 with an error in the browser:

"error": "Cannot read properties of undefined (reading 'kind')",

And in the console

error: Model custom:db not found

This fix also addresses that issue.

@rvdkooy rvdkooy linked a pull request Jan 23, 2024 that will close this issue
Open
@CodeDruid13 CodeDruid13 mentioned this issue Feb 20, 2024
Open
@robinpuga
Copy link

robinpuga commented May 22, 2024 •
edited
Loading

This fixed has worked for us with Strapi version 4.24.2... it would be great it this was added to the plugin code.

FYI. We needed to delete the .cache directory and run npm run build to get it to take effect.

romario333 added a commit to romario333/strapi-plugin-import-export-entries that referenced this issue Sep 20, 2024
@romario333
Patch to fix Baboo7#166
1e21ad5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Baboo7 Baboo7

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix: recognize latest strapi paths rvdkooy/strapi-plugin-import-export-entries
4 participants
@robinpuga @fmann @Baboo7 @VeckansE