This repository has been archived by the owner on Mar 17, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 66
Getting Started
Jonathan Moore edited this page Jun 5, 2017
·
9 revisions
- Before you start using WordPress you probably should already fix your base site language and permalink structure
- after activating WooCommerce you should run through the initial setup
- after Polylang you should add the languages you need and set the permalinks
- after activating woo-poly-integration, set the configuration to match your use case
- before translating a set of products, create and translate the Product Categories and Tags and Product Attributes which these products will use
- First, make sure you have done in the initial setup including basic configuration of Wordpress, WooCommerce and Polylang.
- At this point you should know what languages you are going to use and what your urls look like (eg lang2.mysite.com or mysite.com/lang2 etc) and you should have translated some site pages, now you can activate woo-poly-integration
Before you start translating, you should:
- Check the WooCommerce-Polylang Integration Features and Metas since these settings apply site-wide for all products.
- See the rest of this wiki for additional discussion for example on Stock and Pricing.
For each new language, first there are several steps to do in Polylang and Wordpress:
- Add new language to Polylang
- Add translation pages for the standard WooCommerce pages Shop, Basket, Checkout, My Account
- Add menu for the new language to Wordpress The site won't be usable in the new language without these steps! Next:
- Translate global WooCommerce options which this plugin adds to Polylang Strings Translations
- Translate the Product Categories, Product Tags and Product Attributes, the same as setting up a new Product Category below.
Before adding your products, please create and translate the Categories, Tags and Attributes which you are going to use for these products:
- Product Categories and Tags
- Product Attributes Note: after create a new Product attribute, remember to both translate the name in Polylang Strings Translations, and if you also want to translate the Attribute Terms (the values), go to Polylang settings page Languages, Settings, Custom post types and Taxonomies /wp-admin/admin.php?page=mlang_settings and enable translation for the new attribute - see Product Attributes The plugin does have the capability to fill in missing translations for Categories, Tags and Attributes to avoid errors when you create a product translation. It does this by copying the source language value of the attribute. Any slugs created will be source language slug with language suffix, for example English "color" automatic fill-in translation in Spanish will be created as Name "color" and slug "color-es".
After creating the products it's a good idea to go back to Products, Tags and Products Attributes to review any new Tags and attribute Terms which may have been created during the editing process.