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.

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

[UPGRADE]: Strapi v5 #404

Open
etngeru opened this issue May 29, 2024 · 7 comments · May be fixed by #411
Open

[UPGRADE]: Strapi v5 #404

etngeru opened this issue May 29, 2024 · 7 comments · May be fixed by #411
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@etngeru
Copy link

etngeru commented May 29, 2024

Timeline for Upgrading to Strapi v5

Hello,

I am currently using Strapi v5 beta and would like to integrate strapi-plugin-translate. Could you please provide an estimated timeline for when the plugin will be compatible with Strapi v5? Additionally, any insights into the planned changes or improvements would be greatly appreciated.
Thank you for your support and hard work.

Regards,
Etngeru.

@etngeru etngeru added the enhancement New feature or request label May 29, 2024
@sargreal sargreal changed the title [UPGRADE]: [UPGRADE]: Strapi v5 Aug 22, 2024
@sargreal
Copy link
Member

Dear @HyndmanEthan

Thank you for your request. We are definitely considering to upgrade this plugin to work with Strapi v5. However, as this plugin is in some points deeply connected to the Strapi v4 database architecture (As that was the only possibility to get it working as it is now), it will take some time.

Additionally, with the upgrade to strapi v5 we want to migrate this repository to typescript. This means that even more code has to change, but in the long run this plugin will then be easier to maintain and use.

Due to the extensive changes we cannot give you an estimated timeline. However the current features in testing #109 and development #401 will land before the strapi v5 migration is done. Afterwards, we may include more of the features we already have on the roadmap.

If you want to see any of those features earlier, please open a pull request and try yourself at it!

@sargreal sargreal self-assigned this Aug 22, 2024
@sargreal sargreal moved this from Investigate to In Progress in Translate Strapi Plugin Aug 22, 2024
@sargreal sargreal added this to the v2.0 milestone Aug 22, 2024
@sargreal sargreal linked a pull request Aug 22, 2024 that will close this issue
9 tasks
@SimianPrimus
Copy link

Hello @sargreal,

I hope you're doing well. I just wanted to follow up on this issue and kindly ask if there's any update on a loose timeline for Strapi v5 support for the plugin. We're looking to make some decisions on our project direction, and any additional insight would be greatly appreciated.

Thank you again for your hard work!

@sargreal
Copy link
Member

Hi @SimianPrimus,

The most part of the migration is done already.
There are only some small issues remaining before we can do prerelease versions on the “next” channel.

However I cannot give you a concrete timeline on this. I think it will be during the next few weeks, but I cannot say for sure.

@Matb85
Copy link

Matb85 commented Nov 19, 2024

Hello, any updates on this? Is there a way one could help with getting this to ship?

@sargreal
Copy link
Member

Hi @Matb85

I have just added some more changes, since there was a larger issue with updating entities.
As this is now resolved, there are mostly cleanup tasks remaining before we can launch the preview version.

Mostly we would be very happy to have some help in the testing of the plugin, once it is available as preview.

@sargreal sargreal linked a pull request Nov 19, 2024 that will close this issue
9 tasks
@sargreal sargreal pinned this issue Dec 13, 2024
@DoudouDoudouk
Copy link

Hello, is there any update?

@beebop1032
Copy link

Hello, is there any update?

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

6 participants