Skip to content

fix: fully translatable LaunchPad#113

Merged
Baldinof merged 2 commits into
mainfrom
feature/add-more-fr-localisation
Feb 20, 2026
Merged

fix: fully translatable LaunchPad#113
Baldinof merged 2 commits into
mainfrom
feature/add-more-fr-localisation

Conversation

@alex-strapi
Copy link
Copy Markdown
Collaborator

What does it do?

Made the frontend fully translatable, fixing a localisation undefined issue and also fixed some defensive coding around blog description

Why is it needed?

Main issue was it was only partially translated to french

How to test it?

Simply make sure the whole Strapi application doesn't crash and the connected Next.js application is fully working.

Some additional things to check:

  • Strapi project uuid is "LAUNCHPAD". strapi/packages.json.
  • Strapi version is the latest possible.
  • If the Strapi version has been changed, make sure that the strapi/scripts/prefillLoginFields.js works.
  • If you updated content, make sure to create a new export in the strapi/data folder and update the strapi/packages.json seed command if necessary.

Related issue(s)/PR(s)

#87
#112
#53

@vercel
Copy link
Copy Markdown

vercel Bot commented Feb 20, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
launch-pad Ready Ready Preview, Comment Feb 20, 2026 9:50am
launch-pad-mzzo Ready Ready Preview, Comment Feb 20, 2026 9:50am

Request Review

@PaulBratslavsky
Copy link
Copy Markdown
Collaborator

Issue

When running the yarn seed command, the following error occurs:

? The import will delete your existing data! Are you sure you want to proceed? Yes
[2026-02-19 20:35:42.726] error: [FATAL] File './data/export_20250116105447.tar.gz' is not a valid Strapi data file.
Import process failed.

Root Cause

The seed and export scripts in the root package.json reference a hardcoded filename with a timestamp:

"seed": "cd strapi && yarn strapi import -f ./data/export_20250116105447.tar.gz --force",
"export": "cd strapi && yarn strapi export --no-encrypt -f ./data/export_20250116105447"

However, when you run a new export, Strapi generates a file with a new timestamp (e.g., export_20260220001139.tar.gz). This creates a mismatch — the seed command still looks for the old filename, which either no longer exists or has been overwritten.

Fix

Use a consistent, non-timestamped name for the seed file. Update the scripts in package.json to:

"seed": "cd strapi && yarn strapi import -f ./data/seed-data.tar.gz --force",
"export": "cd strapi && yarn strapi export --no-encrypt -f ./data/seed-data"

This ensures the export always overwrites the same file and the seed command always finds it, eliminating the filename mismatch entirely.

@alex-strapi
Copy link
Copy Markdown
Collaborator Author

@PaulBratslavsky fixed 😛

@Baldinof Baldinof merged commit 2b7a7ad into main Feb 20, 2026
3 checks passed
@Baldinof Baldinof deleted the feature/add-more-fr-localisation branch February 20, 2026 11:02
jadenblack pushed a commit to indigo-services/strapi-launchpad that referenced this pull request May 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants