Developed by: qTranslate Team Contributors: johnclause, michelweimerskirch Tags: multilingual, language, bilingual, i18n, l10n, multilanguage, translation, WooCommerce Requires at least: 4.0 Tested up to: 4.1.1 Stable tag: 1.1 License: GPLv3 or later Donate link: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=QEXEK3HX8AR6U License URI: http://www.gnu.org/licenses/gpl-3.0.html
Enables multilingual framework for plugin "WooCommerce - excelling eCommerce".
This plugin enables qTranslate-X multilingual framework (version 3.1 or later) for WordPress plugin WooCommerce - excelling eCommerce (version 2.3.5 or later).
After the activation, depending on your theme, you may need to do the following additional step to finalize the configuration:
- In all customizable template files, replace calls to
bloginfo('xxx')withbloginfo('xxx','display'), if you have any. You do not have to do this, if title of your blog appears correctly everywhere you can see it (especially in emails sent), or if you do not localize the name of your blog.
This plugin is not supported by the authors on the WordPress forum due to its simplicity. If you find a field which is not translatable, follow the pattern how it is done in the code for other fields and make it translatable. Then submit a pull request at GitHub to enable your changes for everyone else.
Standard, as any other normal plugin hosted at WordPress.
After the activation, depending on your theme, you may need to do the following additional step to finalize the configuration:
- In all customizable template files, replace calls to
bloginfo('xxx')withbloginfo('xxx','display'), if you have any. You do not have to do this, if title of your blog appears correctly everywhere you can see it (especially in emails sent), or if you do not localize the name of your blog.
Plugin does not have any configuration options, and no screenshots needed.
Plugin does not have any configuration options, simply activate it and it will enable the translation of relevant fields for WooCommerce back- and front-end.
This plugin is not supported by the authors on the WordPress forum due to its simplicity. If you find a field which is not translatable, follow the pattern how it is done in the code for other fields, and make it translatable. Then submit a pull request at GitHub to enable your changes for everyone else.
No need for Upgrade Notice.
- Admin e-mails sent by pressing one of the buttons in column 'Actions' on order list page,
/wp-admin/edit.php?post_type=shop_order, go in the original customer language used to submit the order. However, same e-mails sent using the "Resend order emails" option in order editor page,/wp-admin/post.php?post=nnn&action=edit, go in the mixed language of admin and customer. As a workaround, you can switch the admin language to the customer language before resending an e-mail (which shouldn't happen too often). - Two buttons, "Add New XXX" and "Search XXX", on attribute editor page,
/wp-admin/edit-tags.php?taxonomy=xxx&post_type=product, are displayed with raw multilingual text. This should be fixed with a later qTranslate-X version. - HTML header title on admin page
/wp-admin/edit-tags.php?taxonomy=xxx&post_type=productdisplays raw multilingual values.
- Improvement: Gateway names are translated on page
/wp-admin/admin.php?page=wc-settings&tab=checkout. - Improvement: page /wp-admin/admin.php?page=wc-settings&tab=email§ion=wc_email_customer_refunded_order Pull Request #17.
- Improvement: during an order, the language currently used by the customer is stored along with the order meta data
- Improvement: complete order e-mails on admin side are now sent with the order's original language (only for orders made after this update). [Issue #3]
- Improvement: display of fields of class 'attribute_name' in
post.phppage. - Improvement: added filter 'woocommerce_format_content', subject to approval from Woocommerce - was already approved, wait for next release after 2.3.5 - done by now.
- Fix: problem with custom attributes: Issue #2.
- Initial release