strapi-plugin-translate
strapi-plugin-translate copied to clipboard
Fekide
[UPGRADE]: Strapi v5
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.
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. 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.
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. 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.
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.
:tada: This issue has been resolved in version 2.0.0-next.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
:tada: This issue has been resolved in version 1.3.0-next.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
:tada: This issue has been resolved in version 1.2.0-next.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
I user Strapi version 5.12.3 and executing
$ npm install strapi-plugin-translate
have this error:
npm error code ERESOLVE npm error ERESOLVE unable to resolve dependency tree npm error npm error While resolving: [email protected] npm error Found: @strapi/[email protected] npm error node_modules/@strapi/strapi npm error @strapi/strapi@"5.12.3" from the root project npm error npm error Could not resolve dependency: npm error peer @strapi/strapi@"^4.0.0" from @strapi/[email protected] npm error node_modules/@strapi/plugin-i18n npm error peer @strapi/plugin-i18n@"^4.1.4" from [email protected] npm error node_modules/strapi-plugin-translate npm error strapi-plugin-translate@"*" from the root project npm error npm error Fix the upstream dependency conflict, or retry npm error this command with --force or --legacy-peer-deps npm error to accept an incorrect (and potentially broken) dependency resolution.
@sargreal any solution or suggest for install on strapi v5 ?
I user Strapi version 5.12.3 and executing
$ npm install strapi-plugin-translatehave this error:
npm error code ERESOLVE npm error ERESOLVE unable to resolve dependency tree npm error npm error While resolving: [email protected] npm error Found: @strapi/[email protected] npm error node_modules/@strapi/strapi npm error @strapi/strapi@"5.12.3" from the root project npm error npm error Could not resolve dependency: npm error peer @strapi/strapi@"^4.0.0" from @strapi/[email protected] npm error node_modules/@strapi/plugin-i18n npm error peer @strapi/plugin-i18n@"^4.1.4" from [email protected] npm error node_modules/strapi-plugin-translate npm error strapi-plugin-translate@"*" from the root project npm error npm error Fix the upstream dependency conflict, or retry npm error this command with --force or --legacy-peer-deps npm error to accept an incorrect (and potentially broken) dependency resolution.
@sargreal any solution or suggest for install on strapi v5 ?
@gcastroacn I think you should install the @next version:
npm install strapi-plugin-translate@next
Hello, and thanks for this amazing plugin 💯 I was on strapi 5.12 an all was good, after update to strapi 5.16 (but i tried also 5.17) I get this error using your plugin.
App-GHNTN6HF.js?v=de4734f3:4197 Uncaught (in promise) TypeError: type.attributes.map is not a function
at formatTypeForRequest (App-GHNTN6HF.js?v=de4734f3:4197:33)
at App-GHNTN6HF.js?v=de4734f3:4125:41
at Array.map (
hero you can find my repo ⏬
web-project-cms-strapi-update.zip
Hi @sargreal! My team is eager for this release. This is currently our only blocker from moving our v4 site to v5.
Is there anything we can do to facilitate? Is more user testing or automated testing needed? Is anyone using strapi-plugin-translate@next in production?
Thank you for all the amazing work you've put into this. We appreciate how this plugin lets us use Strapi + Deepl.
P.S. @CDTdenisP, per the instructions above, you may want to open a new issue.
Hi @sargreal! My team is eager for this release. This is currently our only blocker from moving our v4 site to v5.
Is there anything we can do to facilitate? Is more user testing or automated testing needed? Is anyone using
strapi-plugin-translate@nextin production?Thank you for all the amazing work you've put into this. We appreciate how this plugin lets us use Strapi + Deepl.
P.S. @CDTdenisP, per the instructions above, you may want to open a new issue.
Hi @jsadoski-rockhall, thanks for the tip. I'm going to use strapi-plugin-translate@next in production, on a website with 9 languages, and also we are online with another website with 4 languages. From my experience the plugin works good on Strapi 5.12, after this version, I encountered the reported issue. The user interface should be improved, it looks better in Strapi 4.
Hey guys, Just found the cause of this error
App-GHNTN6HF.js?v=de4734f3:4197 Uncaught (in promise) TypeError: type.attributes.map is not a function
at formatTypeForRequest (App-GHNTN6HF.js?v=de4734f3:4197:33)
at App-GHNTN6HF.js?v=de4734f3:4125:41
at Array.map ()
at stateToRequestData (App-GHNTN6HF.js?v=de4734f3:4124:6)
at saveSchema (App-GHNTN6HF.js?v=de4734f3:4457:54)
at onClick (App-GHNTN6HF.js?v=de4734f3:3839:19)
at handleClick (chunk-WSB4GC7Y.js?v=de4734f3:3869:9)
at HTMLUnknownElement.callCallback2 (chunk-AWHRF5BE.js?v=de4734f3:3674:22)
at Object.invokeGuardedCallbackDev (chunk-AWHRF5BE.js?v=de4734f3:3699:24)
at invokeGuardedCallback (chunk-AWHRF5BE.js?v=de4734f3:3733:39)
It is this function addTranslationToFields (at plugin/admin/src/utils/mutateCTBContentTypeSchema.js). this function changes the datatype of attributes variable from array to object.
