[UPGRADE]: Strapi v5 #404
Comments
|
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! |
|
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! |
|
Hi @SimianPrimus, The most part of the migration is done already. 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. |
|
Hello, any updates on this? Is there a way one could help with getting this to ship? |
|
Hi @Matb85 I have just added some more changes, since there was a larger issue with updating entities. Mostly we would be very happy to have some help in the testing of the plugin, once it is available as preview. |
|
Hello, is there any update? |
👍 |
migrate plugin to typescript migrate plugin tests to typescript migrate design-system changes reimplement untranslated service update plugin routes BREAKING CHANGE: drops support for strapi v4 BREAKING CHANGE: plugin is now typescript BREAKING CHANGE: plugin routes have been changed fixes #404 fixes #412
|
Hi all! Thank you for your patience. We have now released this plugin for strapi v5 on the next channel as a prerelease. Please test this out and be free to open any issues you encounter. |
# strapi-plugin-translate [2.0.0-next.1](https://github.com/fekide/strapi-plugin-translate/compare/[email protected]@2.0.0-next.1) (2025-02-02) ### Bug Fixes * **admin:** cannot use useStrapi outside of StrapiApp ([498f14a](498f14a)) * **admin:** migrate direct translation to a header action ([dfc0723](dfc0723)) * **admin:** select default locale by default in translation ([1200472](1200472)) * **admin:** show alert on translation error again ([d295583](d295583)) * batch translation stopping directly after setup ([ee34052](ee34052)) * **batch-update:** tables and hooks ([25e1754](25e1754)) * **batchUpdate:** correctly handle updating in batch ([8bd01d0](8bd01d0)) * export types from shared ([bb2b185](bb2b185)) * populate rule ([3b8e1e8](3b8e1e8)) * **populate-all:** break early if attributeSchema is empty ([5303220](5303220)) * route for deleting updated entries ([31789d5](31789d5)) * **translate:** cleaning data ([8996eef](8996eef)) * **translateEntity:** creating and updating of entities ([855fd82](855fd82)) * update config.get usage ([f1f9c18](f1f9c18)) * updated entry subscription ([86215b3](86215b3)) * **utils:** incorrect populate-all rule for dynamiczone and components ([519370d](519370d)) ### Features * create translateEntity service ([c8df746](c8df746)) * **plugin:** migrate plugin to strapi v5 ([76f3455](76f3455)), closes [#404](#404) [#412](#412) * **provider:** migrate providers to typescript ([a921e19](a921e19)) ### BREAKING CHANGES * **plugin:** drops support for strapi v4 * **plugin:** plugin is now typescript * **plugin:** plugin routes have been changed
|
🎉 This issue has been resolved in version 2.0.0-next.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
🎉 This issue has been resolved in version 1.3.0-next.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
🎉 This issue has been resolved in version 1.2.0-next.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
The text was updated successfully, but these errors were encountered: