-
Notifications
You must be signed in to change notification settings - Fork 798
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
Jetpack-mu-wpcom: Simplify the Help Center translations #38300
Conversation
Thank you for your PR! When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:
This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖 The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available. Once your PR is ready for review, check one last time that all required checks appearing at the bottom of this PR are passing or skipped. Wpcomsh plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. |
Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.
Interested in more tips and information?
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for looking into this!
remove_filter( 'pre_determine_locale', array( $this, 'determine_iso_639_locale' ) ); | ||
// Load translations directly from widgets.wp.com. | ||
wp_enqueue_script( | ||
'help-center-translations', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does ordering matter?
With the old code, the <script>
with the translations for the 'help-center' script would be output into the page first, then the wp_add_inline_script( 'help-center', ..., 'before' )
, then the <script>
for 'help-center' itself.
With this new code, I think there's no constraint on whether the 'help-center-translations' <script>
comes before or after 'help-center'. If the ordering matters, adding 'help-center-translations' to the dependencies array of 'help-center' should be enough to make 'help-center-translations' come first.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested and it does! Translations should be added first. I fixed that now.
// Load translations directly from widgets.wp.com. | ||
wp_enqueue_script( | ||
'help-center-translations', | ||
'https://widgets.wp.com/help-center/languages/' . self::determine_iso_639_locale() . '-v1.js', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like D155011-code accidentally reverted the the files you had added in D155004-code that you're trying to use here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What a catch, yes because I deployed my translations from a branch, not trunk, to make testing this easier. It shouldn't happen after Automattic/wp-calypso#92593 is merged.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll redeploy them to help test this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They're live now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change itself looks reasonable to me, and tests well.
Should this in the readme be updated too?
jetpack/projects/packages/jetpack-mu-wpcom/src/features/help-center/README.md
Lines 48 to 55 in ae4b08a
### Translations | |
Translation are download from `widgets.wp.com/help-center/languages` during `jetpack-mu-plugin` build process. Please cd into `projects/packages/jetpack-mu-wpcom` and run: | |
1. pnpm run build-production-js | |
2. jetpack rsync mu-wpcom-plugin | |
This will update the translations files. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested and translation were working great ✌️
Follow up on #38284
Proposed changes:
As @anomiex explained in #38284, including built translations files is cumbersome and forces us to 1) maintain them 2) redeploy again when they change 3) sync to Atomic to see their changes during dev.
This PR aims to load translations via HTTPS directly from the horse's mouth.
Other information:
Jetpack product discussion
Does this pull request change what data or activity we track or use?
No.
Testing instructions:
jetpack-mu-wpcom
to your sandbox.