VaLeXaR

Hi Hendrik Lersch.
Fixed in new version. Update please.

Resolved

Resolved

Hi laincubadora.
It fixed in new version.

Hi, l1va.
You need use one menu for each language.
First, You need translate pages which in menu. Then menu items if translations not applied automaticaly from pages. Custom menu items or post archives You need translate manually.

Hi.
Sweden country code by ISO is SE https://take.ms/cyYfF. Flag is right.

The letter is sent to an administrator in a language on which a site is now. WordPress has built-in locale setting for each user. But when sending the letter it is not taken into account. This is done by WooCommerce developers.

Regards,
Valentyn

To apply the new configuration, you must enable / disable any module or switching theme. The plugin looks for the configuration only after the action. Maybe I will change this for an active topic in the future.

• This reply was modified 7 years, 5 months ago by VaLeXaR.

So far, there are technical issues that prevent the integration of WP Maintenance with WP Multilang. I will correct them in the next release.
Here is a quick version of the configuration for this plugin. Maybe he’s not full. You need to see which variables are contained in the’ wp_maintenance_settings’ option to customize precisely for you.

{
  "options": {
    "wp_maintenance_settings": {
      "titre_maintenance": {},
      "text_maintenance": {},
      "text_bt_maintenance": {},
      "title_newletter": {}
    }
  },
  "admin_pages": [
    "toplevel_page_wp-maintenance"
  ]
}

Yes, you need to customize language switcher via css.
Perhaps you added a language switcher in functions.php? It is wrong. You need add a language switcher to file which is part of template(header.php, footer.php) in needed place or set it in widget or menu.

Hi. Do You have a screenshot with problem?

You need create wpm-config.json file in your active theme.
Next, you need add setting for fost types or taxonomies what you needds.
Example:

{
  "post_types": {
    "portfilio": {},
    "portfolio2" {}
  },
  "taxonomies": {
    "portfolio_tag": {}
  },
  "post_fields": {
    "custom_field1": {},
    "custom_field2": {}
  },
  "term_fields": {
    "custom_field1": {},
    "custom_field2": {}
  }
}

You can see the name of any type of record or taxonomy in the address bar. https://take.ms/1AQCv, https://take.ms/n3GmK
You can see the name of the fields that you want to translate in the wp_postmeta tables, wp_termmeta, wp_usermeta, wp_commentmeta https://take.ms/r1CTb
The settings is done this way, because you can not predict what custom fields will be called before.

Hi.
For translating custom post types or taxonomies You need add this to the config file wpm-config.json in your active theme.
For translating custom fields You need also add needs fields to config file.

An example of configurations can be found at the root in the config folder of the plugin.

Best regards,
Valentyn.

Hi. My plugin do not use different posts or taxonomies for different language. I use multilingual string for translating. One post or term for each language.

Hi.
WP Multilang not use prefix for language by default.
I see that format of url https://mydomain.com/en://mydomain.com/2017/09/01/article-02/ firs time. Can You write me on my email [redacted]? And I try to help You.

Best regards, Valentyn.

• This reply was modified 7 years, 6 months ago by Marius L. J.. Reason: Removed email

Report me about bugs. If You find it.

• This reply was modified 7 years, 6 months ago by VaLeXaR.