Limited-Time Offer

Get Extra 20% off on FullCharge Yearly Plan — available for first 10 users only. Don’t miss out! 🚀

TrackWP

Japanized for WooCommerce · Version history

Japanized for WooCommerce changelog and version history

Latest version
3.0.2
Nov 5, 2026 (5 days ago)
Releases
155
since 2019
In the last year
27
about one every 14 days
Tested up to
WordPress 7.1.4
PHP 8.3 or later

Releases each year

  • 201924 releases
  • 202010 releases
  • 202118 releases
  • 20227 releases
  • 202316 releases
  • 202411 releases
  • 202543 releases
  • 202626 releases

202626 releases

  1. Japanized for WooCommerce 3.0.2Latest

    • Added – Two hooks for the scheduled updates of Japanized for WooCommerce Pro and similar plugins: the filter jp4wc_security_check_updates_automatically lets a plugin that updates other plugins on its own schedule have them counted as updated automatically by the security check, and the action jp4wc…
    • Changed – The free security check by wc.artws.info asks for consent again under its revised terms of use and privacy policy (revised on 2026-10-29, in force from 2026-11-05): staff of 職人工房 合同会社 may look at the information sent and the reports of each registration to answer inquiries, investigate pr…
    • Fixed – Bundled Japanese translation: 19 strings had no translation (among them the settings of Cash on Delivery for Subscriptions and some Paidy error messages), and six strings of the COD fee settings on the settings screen showed in English on every Japanese site, because WordPress uses the bund…
    • Fixed – The security check no longer reports two items as passed while they are still open. The user list of the REST API is also checked at ?rest_route=/wp/v2/users, which WordPress answers whatever the permalinks, so a site that blocks only /wp-json/wp/v2/users now fails the check, and the item i…
    • Fixed – The free security check could send the revenue and order bands when the information shown before sending said they were not sent: when the checks above finished again while a check without the bands was running, the box for the bands could turn itself on while the list of the information se…
    • Fixed – The Security tab no longer says the vulnerability data has not been downloaded yet while downloading it fails. It shows when the last download failed and why (this server could not connect to wc.artws.info, wc.artws.info returned an error, the data was damaged, the PHP zlib extension is mis…
    • Security – The login attempt limiter counts an IPv6 address together with the rest of its /64 network, so a client cannot get past the per-address limit by taking a new address for every attempt; an IPv4 address, including one that reaches the site as an IPv4-mapped IPv6 address, is still counted o…

  2. Japanized for WooCommerce 3.0.1

    • Added – The report of the free security check starts with a comparison with the checks on the Security tab: what only the free check found, what only the checks on the tab found and which checks on the tab could not be confirmed, or that the result is the same. The comparison is not included when t…
    • Changed – The free security check opens from a “Get the free check” button: the information to be sent and the consent appear only when it is clicked, and nothing is sent until a store manager agrees and clicks “Agree and run the check”. Once the site has agreed, the box for the revenue and order b…

  3. Japanized for WooCommerce 3.0.0

    • Added – A security check for the site, on a new Security tab (WooCommerce → JP4WC Settings → Security). Once a day it downloads a list of known vulnerabilities from wc.artws.info (data from Wordfence Intelligence) and checks the installed plugins, themes and WordPress against it; only the versions…
    • Added – The security check also runs the other 16 of its 17 checks on the site’s own setup, such as HTTPS on the checkout and My account pages, two-factor authentication, a user named “admin”, file editing in the admin, and backups, database dumps or logs left in public directories, and scores each…
    • Added – The Security tab shows the total score (the lowest of the four requirements) and a card for each requirement, the items that need action with the fixed version and how to fix each one, a list of all checks, and “Re-check now”, which runs the check again in the background (WP-Cron) and shows…
    • Added – The Security tab links to the terms of use of wc.artws.info, which apply to the vulnerability data (#286)
    • Added – A login attempt limiter on the Security tab (off by default): failed logins are counted per IP address and per user name on the WordPress login page, the WooCommerce My account and checkout login forms and XML-RPC, and once the limit is reached further attempts for that address or name are…
    • Added – Two hardening options on the Security tab (off by default) for the items the security check finds open: hide the user list of the REST API (/wp-json/wp/v2/users) from visitors who are not logged in, and forbid file editing in the admin screens (DISALLOW_FILE_EDIT, unless wp-config.php alrea…
    • Added – XML-RPC on the Security tab: a record of the XML-RPC calls of the last 30 days, kept on the site whatever the setting (which methods were called, how often, by which client and whether their logins worked), and an option (off by default) that refuses every XML-RPC method except the ones you…
    • Added – A free security check by wc.artws.info on the Security tab, optional: nothing is sent until a store manager agrees to the terms of use and the privacy policy and clicks the button. It sends the site address, the versions of WordPress, WooCommerce, PHP and this plugin, the language, the inst…

  4. Japanized for WooCommerce 2.9.20

    • Added – Administrators now see a dialog on admin screens when the site’s PHP is older than the fix for the critical PHP2Shell vulnerabilities (CVE-2026-109618 / CVE-2026-109619): PHP 8.2.35, 8.3.36, 8.4.27 or 8.5.12, with no fixed release for PHP 8.1 and older. It links to an article on updating PH…

  5. Japanized for WooCommerce 2.9.19

    • Fixed – A request that was running while Japanized for WooCommerce was being updated could still stop with a fatal error (“Failed opening required …”) after the 2.9.18 fix (#266), because some files were read only later in the request: the Checkout block support of Paidy and of this plugin’s other…

  6. Japanized for WooCommerce 2.9.18

    • Fixed – In the Checkout block, a customer who came back from Paidy Checkout after Paidy declined the payment saw no message, because the notice was only added on the classic checkout; the Checkout block now shows it as an error notice, and the classic checkout no longer shows it twice (#248)
    • Fixed – The Paidy payment script was printed twice on the order-pay page and the Paidy settings were saved twice, because the Paidy webhook endpoint created its own copy of the Paidy gateway on every request; the endpoint now uses WooCommerce’s gateway, answers a webhook with HTTP 503 while Paidy i…
    • Fixed – Signed Paidy webhooks in sandbox mode were verified with the live secret key instead of the test secret key, so they could be rejected; the key is now chosen from the Paidy environment setting (#244)
    • Fixed – With Paidy debug mode on, the URL of the capture request was never written to the log, unlike the cancel and refund requests; it is now logged as well (#247)
    • Fixed – Since 2.9.14, the plugin package on WordPress.org also contained a copy of the release ZIP file, roughly doubling the download size; the package no longer includes it (#265)
    • Fixed – A request that was running while Japanized for WooCommerce was being updated could stop with a fatal error (“Failed opening required … config-jp4wc-framework.php”), most visibly from the shipment tracking and Yamato export features of Japanized for WooCommerce Pro; the framework’s strings a…

  7. Japanized for WooCommerce 2.9.17

    • Added – A “Morning” (午前中) option can be shown as the first delivery time zone: enable it under Delivery settings → Delivery time settings (off by default) and customise its label; it is offered on both the classic and the block checkout and works even when no hourly time zone is registered (which p…
    • Fixed – Paidy payments whose payment ID contains a hyphen (-) were rejected by the payment ID format check and never marked as paid, leaving the order pending until the stock hold cancelled it even though the customer had paid; the check now accepts the base64url alphabet Paidy actually uses (pay_[…
    • Fixed – In the Checkout block the Cash on Delivery fee could get out of step with the selected payment method on slower servers (a fee left behind after switching to another method, or missing after switching to COD); the fee is now calculated from WooCommerce’s own chosen_payment_method and from t…
    • Fixed – Saving any tab of the Japanized for WooCommerce settings screen wiped a Cash on Delivery fee that had been configured on the COD gateway’s own settings page; the settings screen now reports the values actually in force so they are preserved (#218)
    • Fixed – The delivery date, delivery time zone and shipping date entered on the classic checkout were stored HTML-encoded (&, ', "), so a time zone label containing &, ' or " was saved differently from the block checkout and showed up encoded in plain-text order emails; the values are…
    • Fixed – Paidy Checkout failed to open on the payment page (a JavaScript syntax error) for orders with a zero-discount coupon such as a free-shipping coupon, a line item whose product had been deleted, or a fee whose name contains a line break or backslash, so the customer could not pay with Paidy a…
    • Fixed – A connection error or timeout on a Paidy cancel, capture or refund request caused a fatal error (“Cannot use object of type WP_Error as array”), which for a refund left behind a WooCommerce refund that Paidy never made, and a refund answered without a status (for example a 502 error page) w…
    • Fixed – Applying for Paidy again through the onboarding wizard after a cancelled review or a plugin reinstall sent the application without the site hash that encrypts the delivered API keys and signs the key-delivery callback (and logged a PHP “Undefined variable” warning), so the API keys could no…
    • Fixed – Changing a Paidy order from Processing to Cancelled sent the cancel (close) request to Paidy up to three times, so the requests after the first one failed with HTTP 409 and left “cancellation not completed” order notes on an order that Paidy had in fact cancelled; a failed capture or refund…
    • Fixed – A second partial refund of a Paidy order failed (“An error occurred while attempting to create the refund using the payment gateway API.”), and changing a partly refunded Paidy order from Completed to Cancelled did not refund the rest, because only the first refund of an order was ever sent…
    • Security – A Checkout block draft order could be paid by Cash on Delivery through the Store API pay-for-order route or the classic order-pay page without the COD fee being applied; both paths now refuse COD/COD2 for draft orders and direct the customer to the checkout page
    • Security – The order’s transaction ID is now validated against the Paidy payment ID format and rawurlencode()-escaped before it is put into the cancel, capture and refund API URLs, as the payment lookup has been since 2.9.14; for an ID that does not match, no request is sent to Paidy and an order n…
    • Removed – The usage tracking feature has been removed in preparation for a new feature that will replace it; no usage data is sent from this version on, and its setting, scheduled event and stored options are cleaned up on update (#239)
    • Changed – The notification e-mail sent when a required delivery date or time zone is missing now goes only to the shop’s notification address (#239)
    • Changed – Tested up to WordPress 7.1 and WooCommerce 11.2.1

  8. Japanized for WooCommerce 2.9.16

    • Added – Paidy onboarding callbacks can now be authenticated via an HMAC-SHA256 signature shared at application time, in addition to the one-time state token; this restores automatic API key delivery for merchants whose token had already expired or was never issued
    • Added – A “Back to Paidy settings” link on the onboarding “under review” screen so merchants who received their Paidy API keys separately can enter them manually without waiting for automatic delivery
    • Security – Fixed a replay/idempotency gap where two concurrent Paidy onboarding callbacks authorized by the same state token (without an accompanying signature) could both be processed, duplicating the credential/status update
    • Security – Paidy onboarding callbacks are now authenticated strictly from the signed request body; a query-string parameter could previously override a value that was actually covered by the signature
    • Security – Paidy onboarding callbacks for an application that is no longer the current one on record are now rejected, preventing a delayed or resent callback from overwriting a newer application’s credentials
    • Security – The Cash on Delivery / COD2 surcharge configured for Block Checkout could be bypassed by sending an invalid payment gateway ID to the cart-update endpoint while still completing the order via COD; the gateway ID is now validated against the site’s registered gateways
    • Security – Decrypted Paidy API secret keys are no longer duplicated in plaintext in the diagnostic paidy_received_data option; they remain stored (as before) in the gateway’s own settings
    • Fixed – wizard=false now correctly shows the Paidy gateway’s manual configuration fields
    • Fixed – Uninstalling the plugin now also removes the signature- and event-claim option rows created by the onboarding receiver’s replay guards
    • Fixed – A wp_remote_post() failure during Paidy onboarding submission no longer also falls through to the HTTP-response-code error branch, avoiding duplicate log entries
    • Changed – The admin promotion notice and its “has recent orders” check are now cached for a short period instead of making an uncached remote request and database query on every wp-admin page load
    • Changed – Tested up to WordPress 7.1 and WooCommerce 11.1.0

  9. Japanized for WooCommerce 2.9.15

    • Added – COD fee feature for the “Cash on Delivery for Subscriptions” (COD2) gateway: fee name, amount, maximum cart amount, tax settings, and a PRO tiered-fee table can now be configured on the gateway settings page
    • Added – Toggleable debug logging for COD2 fee calculation; enable “Debug mode” on the gateway settings page to log calculation details (start values, max-amount check, filter results, applied fee) to WooCommerce → Status → Logs (source: jp4wc-cod2-fee)
    • Added – Tax label (e.g. (incl. tax)) after the COD fee amount in cart/checkout totals on the classic checkout, following the same display logic as WooCommerce core subtotal/shipping rows; applied only to the JP4WC gateway fee
    • Fixed – Deleting all rows of the COD2 tiered-fee table and saving restored the previous data; an empty table is now saved correctly (early return happens only on nonce failure)
    • Fixed – Duplicated place-order row (privacy text, terms checkbox, order button) accumulating on every classic-checkout update when the admin-edited Paidy description contained unbalanced HTML; the description is now balanced with force_balance_tags() on output and validated on save
    • Fixed – 403 paidy_invalid_state error on Paidy Instant Onboarding key delivery when the merchant review took longer than 2 days; the one-time state token is now stored as a non-autoloaded option with an application-level expiry instead of a transient, so it survives until the callback arrives
    • Fixed – Paidy settings wizard redirect no longer injects or rewrites the pk_test_ prefix into the saved test API public key; key management is left entirely to the user
    • Fixed – Yomigana (reading) fields duplicated on the My Account order details page (view-order); the duplicate additional-field rows are now suppressed there as well as on the order received page
    • Fixed – Yomigana displayed twice (and editable twice) on the admin order edit screen for orders placed via the block checkout; the Additional Checkout Fields API entries injected by WooCommerce core are now removed from the billing/shipping field lists since JP4WC already embeds yomigana in the for…

  10. Japanized for WooCommerce 2.9.14

    • Fixed – Paidy payment verification was always failing (HTTP 404) because the gateway incorrectly used POST for GET /payments/{id}; switched to wp_safe_remote_get() so payment status checks now succeed and order completion is unblocked
    • Security – payment_id parameter is now validated against the Paidy format (pay_[A-Za-z0-9_]+) and rawurlencode()-escaped before being interpolated into the API URL, preventing path/query injection from buyer-controllable transaction IDs
    • Fixed – Paidy payment_id regex was too strict (rejected underscores); updated to pay_[A-Za-z0-9_]+ to match actual Paidy IDs such as pay_aii8_kYAAEYA2BDW

  11. Japanized for WooCommerce 2.9.13

    • Security – Fixed Broken Access Control (CVSS 6.5) in Paidy payment gateway REST endpoints: paidy-receiver/v1/receive now enforces a one-time per-session state token (stored as a per-token transient keyed by the 32-char value itself so parallel sessions cannot clobber each other); paidy/v1/order and…
    • Security – State token parameter is validated for type and format (32-char alphanumeric) before use as a transient key suffix to prevent non-string or oversized inputs on the unauthenticated receiver endpoint
    • Security – State transient is consumed only after the handler completes successfully so transient DB / decryption failures do not permanently prevent retrying the onboarding callback; orphaned transients are cleaned up when wp_remote_post() fails
    • Fixed – WP_Error messages for base64 and AES-256-CBC decryption failures in the Paidy receiver are now translatable via __() / sprintf() with a %s field-name placeholder
    • Fixed – Missing Paidy API key fields (absent from the intermediary POST) are now merged into $filtered_params as empty strings so downstream code can access all four key fields unconditionally without undefined-index notices

  12. Japanized for WooCommerce 2.9.12

    • Fixed – Yomigana (reading) fields duplicated on My Account address edit form when block checkout is active; woocommerce_address_to_edit filter now removes _wc_{type}/jp4wc/yomigana_* duplicates when traditional {type}_yomigana_* fields are already present (classic checkout), and suppresses traditio…
    • Fixed – Yomigana rows duplicated on My Account Addresses view page (/my-account/?edit-address) for both classic and block checkout; WC Additional Fields API render_address_fields callback is now removed before it fires when JP4WC yomigana is enabled, eliminating the extra “Last Name ( Yomigana )” l…
    • Fixed – My Account Addresses view page did not display yomigana for block checkout users whose data is stored only in _wc_billing/jp4wc/yomigana_* meta keys; formatted_address() now reads both classic ({type}_yomigana_*) and block (_wc_{type}/jp4wc/yomigana_*) meta keys, selecting the set that matc…
    • Fixed – {last_name}, {first_name}, and {yomigana_*} placeholders appeared as literal text in the Block Checkout address summary; address format filter now correctly handles block checkout context
    • Changed – Removed unused PayPal Express Checkout (ppec_paypal) compatibility code that referenced a decommissioned gateway

  13. Japanized for WooCommerce 2.9.11

    • Fixed – Fatal error in jp4wc_delivery_check_data() on Classic Checkout with Square / Amazon Pay; woocommerce_payment_successful_result was registered with 1 argument so $result['order_id'] was undefined when gateways omit it — wc_get_order(null) returned false, causing a PHP Fatal Error on $order->…
    • Fixed – Yomigana (reading) fields no longer appeared in order emails after 2.9.10; restored accidentally removed woocommerce_localisation_address_formats filter registration that injects {yomigana_last_name} / {yomigana_first_name} placeholders into the JP address format template
    • Changed – “NOT registered” delivery log messages changed from log_info to log_debug (WP_DEBUG only) to stop a 2 MB/day log flood on sites with delivery date disabled
    • Changed – Removed unused display_admin_order_meta() method in JP4WC_Delivery that was never registered to any hook (dead code since introduction)

  14. Japanized for WooCommerce 2.9.10

    • Security – jp4wc_hide_notices() now requires manage_woocommerce capability before processing notice-dismissal requests
    • Fixed – Admin order edit page displayed 名|姓 instead of 姓|名; CSS overrides now swap float directions for first/last name fields to restore the correct Japanese display order
    • Fixed – Admin order address field CSS was not applied on HPOS screens; enqueue now covers all screen ID variants including admin_page_wc-orders and uses a $_GET['page'] fallback for early-init cases
    • Fixed – JP4WC admin CSS was overridden by WooCommerce’s cascade; inline styles are now attached directly after woocommerce_admin_styles at admin_enqueue_scripts priority 20 to guarantee the overrides take effect
    • Improved – Admin address field ordering rewritten with an order-list approach that preserves fields injected by third-party plugins and guards against yomigana field duplication
    • Improved – Admin settings panel: Classic Checkout settings (Company name, Zip auto-entry, Free shipping display) grouped under a dedicated section; added PRO notice for Block Checkout zip auto-entry
    • Changed – Removed unused woocommerce_billing_fields/woocommerce_shipping_fields filter and streamlined yomigana field handling in address replacements

  15. Japanized for WooCommerce 2.9.9

    • Fixed – COD fee not applied in Classic Checkout (Shortcode) or Block Checkout because jp4wc_calculate_order_totals read from woocommerce_cod_settings while the JP4WC admin UI saves to wc4jp-extra_charge_* options; settings are now merged at runtime with JP4WC values taking precedence
    • Fixed – extra_charge_calc_taxes mismatch: React admin UI stored yes/no but PHP expected no-tax/tax-excl/tax-incl; legacy values are now normalised on read and the admin UI updated to a 3-way select
    • Fixed – Stale jp4wc_gateway_id session value could cause COD fee to be silently skipped in Classic Checkout (double session-check removed; gateway ID resolved once and passed through the entire calculation)
    • Improved – Block Checkout fee script now uses exponential back-off retry (100 ms → 10 s) instead of fixed 1500 ms / 3000 ms timeouts to wait for wc/store/payment store readiness
    • Added – PRO-ready filter hooks for COD fee: jp4wc_cod_fee_settings, jp4wc_cod_fee_name, jp4wc_cod_fee_amount, jp4wc_cod_fee_is_applicable, jp4wc_cod_fee_tax_class (all @since 2.9.8)
    • Changed – Minimum required PHP version raised from 8.1 to 8.3

  16. Japanized for WooCommerce 2.9.8

  17. Japanized for WooCommerce 2.9.7

  18. Japanized for WooCommerce 2.9.6

    • Fixed – Paidy webhook permission check rejected all notifications from Paidy (no x-paidy-signature header) causing orders to remain “pending” and be auto-cancelled
    • Fixed – Paidy webhook signature verification used wrong option name secret_key (non-existent); corrected to api_secret_key / test_api_secret_key based on test mode
    • Fixed – Bank transfer (bankjp) account skip condition ! isset( $account_names[$i] ) was always false; replaced with empty( $bank_names[$i] ) && empty( $name ) to properly skip blank rows
    • Added – Deduplication of bank transfer account entries on save and load to prevent double display caused by corrupted option data
    • Fixed – Yomigana (読み仮名) fields not displayed in HTML emails when using Block Checkout; corrected meta key fallback from _wc_other/ to _wc_billing/ and _wc_shipping/ prefixes
    • Fixed – Yomigana displayed twice on order received (thank-you) page when using Block Checkout
    • Fixed – Yomigana appearing as a separate bold <strong> list below the formatted address in emails and thank-you page; now suppressed via show_in_order_confirmation: false and block render filter
    • Fixed – “(よみがなを確認するには「編集」をクリックしてください。)” message incorrectly appearing in new order emails
    • Fixed – Customer email salutation showing first name only instead of full name (姓名); email context detection now uses WC_Email::$sending flag for reliability with WC 10.7+ BlockEmailRenderer
    • Added – Country is hidden from formatted address in emails and thank-you page when the store sells to only one country

  19. Japanized for WooCommerce 2.9.5

    • Fixed – White screen on frontend caused by fatal error in Paidy blocks support when gateway is not registered
    • Fixed – WC_Gateway_Paidy not found fatal error on admin pages when WooCommerce is installed with a non-standard path (e.g. wp-env)
    • Fixed – jp4wc_has_orders_in_last_5_days undefined function error caused by is_woocommerce_active() returning false …

  20. Japanized for WooCommerce 2.9.4

  21. Japanized for WooCommerce 2.8.5

  22. Japanized for WooCommerce 2.8.4

  23. Japanized for WooCommerce 2.8.3

  24. Japanized for WooCommerce 2.8.2

  25. Japanized for WooCommerce 2.8.1

  26. Japanized for WooCommerce 2.8.0

202543 releases

  1. Japanized for WooCommerce 2.7.17

  2. Japanized for WooCommerce 2.7.16

  3. Japanized for WooCommerce 2.7.15

  4. Japanized for WooCommerce 2.7.14

  5. Japanized for WooCommerce 2.7.13

  6. Japanized for WooCommerce 2.7.12

  7. Japanized for WooCommerce 2.7.11

  8. Japanized for WooCommerce 2.7.10

  9. Japanized for WooCommerce 2.7.9

  10. Japanized for WooCommerce 2.7.8

  11. Japanized for WooCommerce 2.7.7

  12. Japanized for WooCommerce 2.7.6

  13. Japanized for WooCommerce 2.7.5

  14. Japanized for WooCommerce 2.7.4

  15. Japanized for WooCommerce 2.7.3

  16. Japanized for WooCommerce 2.7.2

  17. Japanized for WooCommerce 2.7.1

  18. Japanized for WooCommerce 2.7.0

  19. Japanized for WooCommerce 2.6.43

  20. Japanized for WooCommerce 2.6.42

  21. Japanized for WooCommerce 2.6.41

  22. Japanized for WooCommerce 2.6.40

  23. Japanized for WooCommerce 2.6.39

  24. Japanized for WooCommerce 2.6.38

  25. Japanized for WooCommerce 2.6.37

  26. Japanized for WooCommerce 2.6.36

  27. Japanized for WooCommerce 2.6.35

  28. Japanized for WooCommerce 2.6.34

  29. Japanized for WooCommerce 2.6.33

  30. Japanized for WooCommerce 2.6.32

  31. Japanized for WooCommerce 2.6.31

  32. Japanized for WooCommerce 2.6.30

  33. Japanized for WooCommerce 2.6.29

  34. Japanized for WooCommerce 2.6.28

  35. Japanized for WooCommerce 2.6.27

  36. Japanized for WooCommerce 2.6.26

  37. Japanized for WooCommerce 2.6.25

  38. Japanized for WooCommerce 2.6.24

  39. Japanized for WooCommerce 2.6.23

  40. Japanized for WooCommerce 2.6.22

  41. Japanized for WooCommerce 2.6.21

  42. Japanized for WooCommerce 2.6.20

  43. Japanized for WooCommerce 2.6.19

202411 releases

  1. Japanized for WooCommerce 2.6.17

  2. Japanized for WooCommerce 2.6.16

  3. Japanized for WooCommerce 2.6.15

  4. Japanized for WooCommerce 2.6.14

  5. Japanized for WooCommerce 2.6.13

  6. Japanized for WooCommerce 2.6.12

  7. Japanized for WooCommerce 2.6.11

  8. Japanized for WooCommerce 2.6.10

  9. Japanized for WooCommerce 2.6.9

  10. Japanized for WooCommerce 2.6.8

  11. Japanized for WooCommerce 2.6.7

202316 releases

  1. Japanized for WooCommerce 2.6.6

  2. Japanized for WooCommerce 2.6.5

  3. Japanized for WooCommerce 2.6.3

  4. Japanized for WooCommerce 2.6.2

  5. Japanized for WooCommerce 2.6.1

  6. Japanized for WooCommerce 2.6.0

  7. Japanized for WooCommerce 2.5.13

  8. Japanized for WooCommerce 2.5.12

  9. Japanized for WooCommerce 2.5.11

  10. Japanized for WooCommerce 2.5.10

  11. Japanized for WooCommerce 2.5.9

  12. Japanized for WooCommerce 2.5.8

  13. Japanized for WooCommerce 2.5.7

  14. Japanized for WooCommerce 2.5.6

  15. Japanized for WooCommerce 2.5.5

  16. Japanized for WooCommerce 2.5.4

20227 releases

  1. Japanized for WooCommerce 2.5.3

  2. Japanized for WooCommerce 2.5.2

  3. Japanized for WooCommerce 2.5.1

  4. Japanized for WooCommerce 2.5.0

  5. Japanized for WooCommerce 2.4.1

  6. Japanized for WooCommerce 2.4.0

  7. Japanized for WooCommerce 2.3.8

202118 releases

  1. Japanized for WooCommerce 2.3.7

  2. Japanized for WooCommerce 2.3.6

  3. Japanized for WooCommerce 2.3.5

  4. Japanized for WooCommerce 2.3.4

  5. Japanized for WooCommerce 2.3.3

  6. Japanized for WooCommerce 2.3.2

  7. Japanized for WooCommerce 2.3.1

  8. Japanized for WooCommerce 2.3.0

  9. Japanized for WooCommerce 2.2.21

  10. Japanized for WooCommerce 2.2.20

  11. Japanized for WooCommerce 2.2.19

  12. Japanized for WooCommerce 2.2.18

  13. Japanized for WooCommerce 2.2.17

  14. Japanized for WooCommerce 2.2.16

  15. Japanized for WooCommerce 2.2.15

  16. Japanized for WooCommerce 2.2.14

  17. Japanized for WooCommerce 2.2.13

  18. Japanized for WooCommerce 2.2.12

202010 releases

  1. Japanized for WooCommerce 2.2.11

  2. Japanized for WooCommerce 2.2.8

  3. Japanized for WooCommerce 2.2.7

  4. Japanized for WooCommerce 2.2.6

  5. Japanized for WooCommerce 2.2.5

  6. Japanized for WooCommerce 2.2.4

  7. Japanized for WooCommerce 2.2.3

  8. Japanized for WooCommerce 2.2.2

  9. Japanized for WooCommerce 2.2.1

  10. Japanized for WooCommerce 2.2.0

201924 releases

  1. Japanized for WooCommerce 2.1.16

  2. Japanized for WooCommerce 2.1.15

  3. Japanized for WooCommerce 2.1.14

  4. Japanized for WooCommerce 2.1.13

  5. Japanized for WooCommerce 2.1.12

  6. Japanized for WooCommerce 2.1.11

  7. Japanized for WooCommerce 2.1.10

  8. Japanized for WooCommerce 2.1.9

  9. Japanized for WooCommerce 2.1.8

  10. Japanized for WooCommerce 2.1.7

  11. Japanized for WooCommerce 2.1.6

  12. Japanized for WooCommerce 2.1.5

  13. Japanized for WooCommerce 2.1.4

  14. Japanized for WooCommerce 2.1.3

  15. Japanized for WooCommerce 2.1.2

  16. Japanized for WooCommerce 2.1.1

  17. Japanized for WooCommerce 2.1.0

  18. Japanized for WooCommerce 2.0.7

  19. Japanized for WooCommerce 2.0.6

  20. Japanized for WooCommerce 2.0.5

  21. Japanized for WooCommerce 2.0.4

  22. Japanized for WooCommerce 2.0.3

  23. Japanized for WooCommerce 2.0.2

  24. Japanized for WooCommerce 2.0.1

Questions about Japanized for WooCommerce’s releases

What is the latest version of Japanized for WooCommerce?

3.0.2, released on Nov 5, 2026 (5 days ago). It’s tested up to WordPress 7.1.4 and needs PHP 8.3 or later.

How often is Japanized for WooCommerce updated?

27 releases in the last year, about one every 14 days. Its first release on WordPress.org dates from August 2019.

Know when your rivals ship

Track your plugin and its rivals: TrackWP sees each new release in the nightly snapshot and alerts you, with what it did to their rank.

Start free

Release dates come from the day each version’s folder was made in Japanized for WooCommerce’s WordPress.org SVN repository; the notes from its readme’s changelog, as its authors wrote it.