WP Multilang

Descrição

WP Multilang is a multilingual plugin for WordPress.

Translations of post types, taxonomies, meta fields, options, text fields in miltimedia files, menus, titles and text fields in widgets.

Features of the plugin WP Multilang

  • 100% free.
  • Translation at PHP.
  • Compatible with REST.
  • Support configuration for translate multidimensional arrays in options, meta fields, post content.
  • Support multisite.
  • Support WordPress in sub-folder.
  • Separate menu items, posts, terms, widgets, comments per language.
  • Many filters for dynamic applying translation settings.
  • No duplicate posts, terms, menus, widgets.
  • No sub-domain for each language version.
  • No additional tables in database.
  • Possibility set many languages with one localization. For example, for localization in the region.
  • Possibility to set custom locale for html(If installed locale is en_US, you can set locale like: en, en-UK, en-AU etc. Without installation another localization)
  • Possibility for add new languages for any user with capability manage_options.
  • Exist the role “Translator” for editing posts, terms. It can not publish or delete.
  • No limits by languages or by possibilities.

WP Multilang compatible with plugins

  • ACF, ACF Pro
  • WooCommerce
  • WooCommerce Customizer
  • Gutenberg
  • Yoast SEO
  • Contact Form 7 (added mail tag [_language] for send user language in mail)
  • WPBakery Visual Composer
  • Page Builder by SiteOrigin
  • NextGEN Gallery
  • All in One SEO Pack
  • MailChimp for WordPress
  • Newsletter
  • Maps Builder
  • Max Mega Menu
  • MasterSlider
  • WP-PageNavi
  • BuddyPress
  • Meta Slider
  • TablePress
  • Download Monitor (Redefine templates for links in your theme and translate link texts)
  • Better Search

Manage translation settings via json.

Add in the root of your theme or plugin file wpm-config.json.

Sample configurations can be viewed in config files in folder ‘configs’ in root the plugin.

Configuration is updated after switching theme, enable or update any plugins.

The plugin has filters for dynamic application configuration for translate.

For turn off translation, set null into the desired configuration.
For example, you must turn off translation for a post type post.
There are two ways:

  1. In json.
    Create in root of a theme or a plugin file wpm-config.json with:
    {
    “post_types”: {
    “post”: null
    }
    }

  2. Through the filter.
    Add in functions.php
    add_filter( ‘wpm_post_post_config’, ‘__return_null’ );

To enable translation pass an empty array in php array() or empty object in json {}.

Supports translation multidimensional array of options, meta fields and post_content.
Supports the removal of established localizations.
Supports translation via GET parameter. Add in the GET parameter lang code desired language.
Supports clean database of translations when removing the plugin. Translations are only removed from the built-in tables.
Supports import term translations from qTranslate(by Soft79).
Supports automatically redirect to the user’s browser language, if he visits for the first time.

Ideal for developers.

For display language switcher in any place add the code to your template if ( function_exists ( 'wpm_language_switcher' ) ) wpm_language_switcher ();
Function accepts two parameters:
$type – ‘list’, ‘dropdown’, ‘select’. Default – ‘list’.
$show – ‘flag’, ‘name’, ‘both’. Default – ‘both’.

Or using the shortcode wpm_lang_switcher. It accept two not necessary parameters ‘type’ and ‘show’.

Available features for translation:
wpm_translate_url( $url, $language = ” ); – translate url
wpm_translate_string( $string, $language = ” ); – translate multilingual string
wpm_translate_value( $value, $language = ” ); – translate multidimensional array with multilingual strings

Update translation occurs at PHP. Therefore plugin has high adaptability, compatibility and easily integrates with other plugins. This is what distinguishes it among similar.

Available translation html tags by JS for strings what do not have WP filters before output.

Add your tags in config:

"admin_html_tags": {
    "admin_screen_id": {
      "attribute": [
        "selector"
      ]
    }
}

Where:
admin_screen_id – admin screen id.
attribute – attribute what need to translate. Available ‘text’ – for translate text node, ‘value’ – for translate form values. Or other tag attribute, like ‘title’, ‘alt’.
selector – css selector for search needed tag. Each selector is a new array item.

If You need to add translation for multidimentional array for repeated elements You can use custom tag ‘wpm_each’ for set config to each element in array.
Example, add config for each item ‘title’ in custom post field array:

"post_fields": {
    "custom_field": {
      "wpm_each": {
        "title": {}
      }
    }
}

For set translation uses the syntax:
[:en]Donec vitae orci sed dolor[:de]Cras risus ipsum faucibus ut[:]

Supports translating from syntax qTranslate, qTranslate-X, WPGlobus etc.

Compatible with REST-API.
Supports transfer the required translation through option lang in the GET request to REST.
Has the ability to keep recording the target language through the transmission parameter lang in the request.

Migration from qTranslate-X

  1. Before installing/uninstalling, make database backup.
  2. Deactivate qTranslate-X.
  3. Install and activate WP Multilang.
  4. Create in root of your theme file ‘wpm-config.json’.
  5. Add all needed post types, taxonomies, options, fields to ‘wpm-config.json’. Setting from qTranslate-X not importing.
  6. Import term names from qTranslate.
  7. Check that everything is okay.
  8. If everything is okay, remove qTranslate-X. If not, make screenshots of errors, restore database from backup and add support issue with your screenshots and description of errors.

Warning

Do not support different slug for each language(Yet).

Not compatible with:
– WP Maintenance

Known issues

Function ‘get_page_by_title’ not working, because in title field are stored titles for all languages. Use function ‘wpm_get_page_by_title( $title )’ as solution.

NOTE: Because plugins have different ways of storing data, WP Multilang is not compatible with every single plugin out-of-the-box (mostly page builders). This may result in texts not being translatable or translations not being saved. Most of these issues can be resolved using the integration options (wpm-config.json or filters) of WP Multilang.

Please try WP Multilang in a test-environment before activating it on an existing production site and always make a backup before activating!

Ecrãs

  • Página de opções
  • Post list page
  • Taxonomy list page
  • Taxonomy edit page
  • Post edit page

Instalação

  1. Upload the plugin files to the /wp-content/plugins/wp-multilang directory, or install the plugin through the WordPress plugins screen directly.
  2. Activate the plugin through the ‘Plugins’ screen in WordPress.
  3. Adjust languages on WP Multilang Settings page.

Perguntas frequentes

Installation Instructions
  1. Upload the plugin files to the /wp-content/plugins/wp-multilang directory, or install the plugin through the WordPress plugins screen directly.
  2. Activate the plugin through the ‘Plugins’ screen in WordPress.
  3. Adjust languages on WP Multilang Settings page.
I add new translation, but it rewrite another translation on different language.

If you have opened several browser tabs for editing this post in different languages, translation will be saved for the language that you opened last.

Avaliações

DO NOT TOUCH!

if I could give this 0 stars, I would
full of bugs, messes up everything, inserts [en:] tags all over the places and they are left behind (!!!!) when deactivating the plugin
+, the [en:] bits are added absolutely chaotically, not all posts or pages get them

the plugin is a mess

Custom Post from Jetpack

Hi,

using module testimonials from jetpack is not working? How to enable languages like when editing post or page ?

Fantastic thing!

I am very pleased with this plugin. Very simple and intuitive to use. Suites me very well. Highly recommended. Thanks a lot to the author!

can’t make it work for home page

can’t make it work for home page , tried all possible way to make it work in home page (means would need 2 home pages actually,but it is an issue in menu while selecting the language menu )

Ler todas as 40 avaliações

Contribuidores e programadores

“WP Multilang” é software de código aberto. As seguintes pessoas contribuíram para este plugin:

Contribuidores

“WP Multilang” foi traduzido para 5 locales. Obrigado aos tradutores pelas suas contribuições.

Traduza o “WP Multilang” para o seu idioma.

Interessado no desenvolvimento?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Registo de alterações

2.2.6

  • added donate link to readme.txt
  • fix display language name
  • fix SiteOrigin Builder compatibility
  • fix fatal error when a plugin is disabled
  • fix translate REST requests in admin

2.2.5

  • fixed Gutenberg compatibility
  • fixed translation WC coupons

2.2.4

  • added “no-cache” header in admin on language change
  • added WC coupon for translating
  • fixed compatibility with SiteOrigin
  • fixed http to https redirect error
  • fixed styles

2.2.3

  • fix translate menu
  • fix translating
  • fix saving metabox
  • fix set home url in subfolder

2.2.2

  • added shortcode for display language switcher
  • add filters for set json config files for integration
  • fixed checking for ml strings
  • fixed compatibility with Gutenberg
  • fixed checking for JSON strings
  • fixed regex for ml strings

2.2.1

  • fixed escaping text. Have error on some sites.
  • fixed ACF PRO menu integration. Have error on ACFv4.

2.2.0

  • added alternate locale for opengraph in YOAST SEO
  • added setting default translation
  • fixed PHP notice in YOAST sitemap
  • fixed compatibility with Gutenberg
  • fixed compatibility with Buddypress
  • fixed translate ‘attr_escape’
  • fixed adding custom fields to menu items

All changelog available on GitHub.