Title: matically's Replies | WordPress.org

---

# matically

  [  ](https://wordpress.org/support/users/matically/)

 *   [Profile](https://wordpress.org/support/users/matically/)
 *   [Topics Started](https://wordpress.org/support/users/matically/topics/)
 *   [Replies Created](https://wordpress.org/support/users/matically/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/matically/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/matically/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/matically/engagements/)
 *   [Favorites](https://wordpress.org/support/users/matically/favorites/)

 Search replies:

## Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[YITH WooCommerce Wishlist] Wishlist page frontend strings stay in English despite a correct and complete tr](https://wordpress.org/support/topic/wishlist-page-frontend-strings-stay-in-english-despite-a-correct-and-complete-tr/)
 *  [matically](https://wordpress.org/support/users/matically/)
 * (@matically)
 * [2 hours, 21 minutes ago](https://wordpress.org/support/topic/wishlist-page-frontend-strings-stay-in-english-despite-a-correct-and-complete-tr/#post-18994604)
 * Hi [@anitaleu](https://wordpress.org/support/users/anitaleu/),
   This is a common
   issue with plugins that render frontend strings via JavaScript rather than traditional
   PHP templates.Here’s what’s happening:**Why your PO/MO translation doesn’t work
   for these strings:**The strings you listed (“Product name”, “Unit price”, “Stock
   status”, etc.) are likely rendered client-side via JavaScript. WordPress’s traditional
   PO/MO translation only works for strings output by PHP on the server side. When
   a plugin uses JavaScript to render UI, it needs a separate JSON translation file(
   the `{textdomain}-{locale}-{hash}.json` format introduced in WordPress 5.0+).
   Standard PO/MO translation tools generate PO/MO files, but typically do not generate
   the JSON translation files needed for JS-rendered strings. That’s why your translation
   is “correct and complete” in the .po file but never shows up on the frontend.**
   Additionally — the WordPress 6.5+ early loading issue:**WordPress 6.5 introduced“
   performant translations” which changed how and when translation files are loaded.
   Custom translation files placed in non-standard locations can be silently ignored
   because the plugin’s text domain gets loaded before your custom translations 
   are registered.**Possible solutions:**1. **Ask YITH to fix it on their end** —
   The plugin should either render these strings server-side (so PO/MO works), or
   properly enqueue their scripts with `wp_set_script_translations()` so that JSON
   translation files are loaded correctly.2. **Use a translation approach that generates
   JSON translation files** in addition to PO/MO, and handles the early-loading 
   timing correctly.Unfortunately this is fundamentally a plugin architecture issue
   on YITH’s side. The “Labels” tab works because those strings go through a different
   code path (PHP/options), while the table headers are handled in JS.Hope this 
   clarifies the root cause.
    -  This reply was modified 14 minutes ago by [Steven Stern (sterndata)](https://wordpress.org/support/users/sterndata/).
      Reason: format
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Font Awesome] Script translations not loading on the admin settings page](https://wordpress.org/support/topic/script-translations-not-loading-on-the-admin-settings-page/)
 *  Thread Starter [matically](https://wordpress.org/support/users/matically/)
 * (@matically)
 * [2 weeks ago](https://wordpress.org/support/topic/script-translations-not-loading-on-the-admin-settings-page/#post-18981105)
 * ![](https://i0.wp.com/wpait.matically.jp/storage/plugin-pages/font-awesome/LDFfCct8MWT5SBKdSsnusLcapGwCY49Ld8G14yRt.
   png?ssl=1)
 * ![](https://i0.wp.com/wpait.matically.jp/storage/plugin-pages/font-awesome/owndh4bEkDq9UKQxmXUsHJgLkZNnIZTexHXc5JPw.
   png?ssl=1)
 * [@mlwilkerson](https://wordpress.org/support/users/mlwilkerson/)
 * Thank you for the quick fix! I’ve verified on version 5.2.1 and can confirm that
   translations are now loading correctly on the admin settings page — see the attached
   screenshot.
 * One minor note: there are a few strings in the UI that appear to be hardcoded
   in English rather than wrapped in translation functions (e.g., __() or _e()),
   so those remain untranslated. Not a blocker at all, but worth noting for a future
   pass if you’re interested.
 * Thanks again for the fast turnaround — really appreciated!

Viewing 2 replies - 1 through 2 (of 2 total)