Closed SalahAdDin closed 2 months ago
For strapi team members see the internal slack conversation: https://strapihq.slack.com/archives/C060CRLUX0V/p1719515676773379?thread_ts=1719515676.773379&cid=C060CRLUX0V
For strapi team members see the internal slack conversation: https://strapihq.slack.com/archives/C060CRLUX0V/p1719515676773379?thread_ts=1719515676.773379&cid=C060CRLUX0V
I can't :v
I can't :v
Yes @SalahAdDin because this is our internal Slack instance (= only for Strapi employees).
Thanks for reporting this.
i18n now being part of core is actually already listed in the breaking changes (see screenshot for where to find on the breaking changes index page), and here's the direct link to the page: https://docs-next.strapi.io/dev-docs/migration/v4-to-v5/breaking-changes/i18n-content-manager-locale
I adjusted the page introduction a bit this morning to give a bit more instructions about the package itself: https://github.com/strapi/documentation/commit/1098cfe00daf122c948bcd4710f3e906582a4fa8
Also, feel free to use the new AI bot as much as you want, it would probably be helpful for such questions (see example response as a screenshot 🤓)
Link to the documentation page or resource
https://docs-next.strapi.io/dev-docs/migration/v4-to-v5/breaking-changes#plugins-providers-and-admin-panel-customization
Describe the bug
It seems that
i18n
becoming a core package was not listed on the break changes, and from that, people like me are getting issues by not uninstalling the old plugin.Additional context
We are testing first the beta releases and then the release candidate, one of the bugs became after the 5 beta; now, after talking to @derrickmehaffy we realized the plugin was deprecated and the issue was fixed.
Suggested improvements or fixes
It would be nice to include this change both in the documentation and articles.
Related issue(s)/PR(s)
This is the related issue.