Support is provided only via e-mail. To contact us, please use the contact form in from our profile page:

http://codecanyon.net/user/surstudio

Proper way:

• Describe what’s happening, and what you expect to happen.
• Send a link/URL where the problem can be seen.
• If necessary, include a screenshot and/or steps on how to reproduce the issue.

Correct sample message:

I'm having an issue with the translator. On desktop it's displayed correctly, but when I access the site on a mobile device, it doesn't show up. Here's link where you can see it: http://www.mysite.com/ And just in case you need it, this is my Item Purchase Code: f4b3ae24-d23f-42a3-80a6-41c37ced6961

Bad sample message:

I'm having an issue with the translator. It doesn't work on mobile devices.

Proper support requests will have priority: the last correct support request will be replied before any other incomplete message.

First, make sure your support request complies with the items listed above. We promise to reply within two business days. In reality, we reply much faster than that. So most likely the replies are already in your SPAM folder.

There are 103 languages supported:

Afrikaans, Albanian, Amharic, Arabic, Armenian, Azerbaijani, Basque, Belarusian, Bengali, Bosnian, Bulgarian, Catalan, Cebuano, Chichewa, Chinese Simplified, Chinese Traditional, Corsican, Croatian, Czech, Danish, Dutch, English, Esperanto, Estonian, Filipino, Finnish, French, Frisian, Galician, Georgian, German, Greek, Haitian Creole, Hausa, Hawaiian, Hebrew, Hindi, Hmong, Hungarian, Icelandic, Igbo, Indonesian, Irish, Italian, Japanese, Javanese, Kannada, Kazakh, Khmer, Korean, Kurdish, Kyrgyz, Lao, Latin, Latvian, Lithuanian, Luxembourgish, Macedonian, Malagasy, Malay, Malayalam, Maltese, Maori, Marathi, Mongolian, Burmese, Nepali, Norwegian, Pashto, Persian, Polish, Portuguese, Punjabi, Romanian, Russian, Serbian, Sesotho, Sinhala, Slovak, Slovenian, Somali, Samoan, Scots Gaelic, Shona, Sindhi, Spanish, Sundanese, Swahili, Swedish, Tajik, Tamil, Telugu, Thai, Turkish, Ukrainian, Urdu, Uzbek, Vietnamese, Welsh, Xhosa, Yiddish, Yoruba, Zulu.

Yes, there's an admin panel dedicated to such matter. See the screenshots.

Simply select the URL you'd like to modify the translations for, select the language and make the changes. Also, if you'd like to make adjustments for many pages at the same time, you can import translations too. You may want to read this whole thread too:

https://codecanyon.net/item/ajax-translator-revolution-wordpress-plugin/1108823/comments?page=12#comment_7743045

No, this is an automatic translation plugin. The pages will be automatically translated when someone clicks on a language.

From version 2.0, the plugin can be updated from its admin panel with a single click. Prior to this version, is needed to uninstall the old version and then install the newer one in the traditional way.

Yes, it works fine with both. It also works fine with all the other visual builders, as well as all the other sliders.

Yes, it works on smartphones. It works on Anddroid, iOS and Windows Mobile.

Yes, it works with the Genesis framework.

This plugin has been improved over the years and it's safe to say that it'll work fine with every theme. In the exceptional case that it doesn't work, then we can arrange a refund with Envato Market.

Most likely the theme is hiding the selected area for mobile devices, you should place the translator in a location that's always visible.

The theme you're using has been carefully crafted, so it should include a placeholder or widget area to place a language switcher. If your theme doesn't have a placeholder for a language switcher, there are a few things you can try before requesting a customization:

- If you want to place the translator in a menu, you may try to use the following free plugin: https://wordpress.org/plugins/wp-widget-in-navigation/

- Contact your theme provider to create this placeholder in your desired location.

- If you know how to place a shortcode in your desired location, you can do something similar with the translator:

• Place an empty HTML container with a unique id, for instance:
  

  <div id="translator_desktop"></div>

• Then in:
  Advanced Settings > General > Location > Custom > Custom location (jQuery), use:
  

  #translator_desktop

• If the location for desktop and mobile are different, you should also place:
  

  <div id="translator_mobile"></div>

• Then in:
  Advanced Settings > General > Location > Custom > Custom location (jQuery), use:
  

  #translator_desktop:visible, #translator_mobile

- If you have a good knowledge of web languages, the translator can be placed anywhere using the advanced positioning settings:

Advanced Settings > General > Location > Custom

- If you're unable to do any of the above options, you can request a customization and we'll place the translator in your desired location. We'll ask you to take a screenshot(s) and visually explain us where would you like to place the translator. We're asking you this because some times is not too easy to come up with the procedure, and then it turns out that the solution isn't exactly what the client wanted.

Every operating system has a simple graphic editing tool, so basically you should:

• Take a screenshot of the site.
• Draw a rectangle or write a text in the desired area.
• Different themes behave in different ways when displaying their content in different resolutions and mobile devices. Make sure to provide additional screenshots for different locations. You may contact your theme provider if you're not sure how to check how the theme looks like in different resolutions and devices.
• Upload the screenshots to an online file hosting and keep the uploaded urls. You can use a free image file hosting, such as:
  https://imgur.com/
  https://postimages.org/
  https://www.ultraimg.com/
• Make sure the Online Backups tab is enabled in the plugin's admin panel.
• Send all the information by going to:
  https://codecanyon.net/item/ajax-translator-revolution-dropdown-wp-plugin/3400269/support/contact
  
  1. Provide a temporary WordPress admin access:
     Login URL:
     Username:
     Password:
     Double check the user has proper access before sending it.
  2. Provide the links to the uploaded screenshots. Make sure to check the screenshots are accurate and correct.
  3. Specify whether you'd like to make the payment using PayPal or Bitcoin or Ethereum.
• How to calculate the cost:
  Each provided screenshot represents a different location. Each location costs 9 EURO, plus a 1 EURO flat fee. For instance, if you're sending 2 screenshots, the cost of the customization will be: (2 x 9 EURO) + 1 EURO = 19 EURO
• If later on you decide to add 1 new location/screenshot, it'll be a new customization, so the cost will be: (1 x 9 EURO) + 1 EURO = 10 EURO

Each site requires one license, after the development site is ready to be deployed, you can use the same license on the live site. There's no need to buy a second license.

Most likely you have enabled the test mode:

Advanced settings > General > Test mode

Disable it and it should work fine.

It's possible to fire the translation to a language, but the content will always load in its original language, then after a couple of seconds, it'll get translated.

a) Advanced Settings > General > Javascript callbacks > On before initialize callback, use (replacing the current content):

function(translator, options) {

	var get_url_parameter = function(_name) {
		return decodeURIComponent((new RegExp('[?|&]' + _name + '=' + '([^&;]+?)(&|#|;|$)').exec(location.search)||[,""])[1].replace(/\+/g, '%20')) || null;
	};

	var is_empty = function(_string) {
		var extra = arguments[1] || null;
		if (!extra) {
			return _string == null || _string.length == 0;
		}
		else {
			return _string == extra;
		}
	};

	var lang_parameter = "lang";
	var to = get_url_parameter(lang_parameter);

	translator._force_translate_to = is_empty(to) ? null : to;
	
	if (translator._force_translate_to == options.from) {
		translator._clear_cookie();
		translator._force_translate_to = null;
	}
	
}

b) Advanced > General > Javascript callbacks > On initialize callback, use (replacing the current content):

function(translator, options) {

	setTimeout(function() {

		if (translator._force_translate_to == null) {
			return;
		}

		var language = translator._container.find("." + translator._options.languageSelectorClass + translator._force_translate_to);

		if (language.length > 0) {
			language.eq(0).click();
		}

	}, 200);
}

c) You should be able to use this code by adding a language parameter to any link, for instance:

http://www.site.com/?lang=es

There's no way to place a php line of code nor a shortcode, but there's something that works in a similar way:

You should place an empty HTML container with a unique id, for instance:

<div id="translator"></div>

Then in:

Advanced Settings > General > Location > Custom > Custom location (jQuery):

Use:

#translator

The plugin only translates text, it doesn't perform any kind of CSS alignment when translated to a RTL language. However, it's possible to assign a class style attribute (to any HTML element) with the current selected language, for instance:

You should go to:

Advanced > General > Javascript callbacks > On complete callback

Replace the content of the field with:

function(filtered_elements, translation, source, from, to, options, restore) {
	var body = document.getElementsByTagName("body")[0];
	var style = "translated-to-";
	var regex = new RegExp("\b" + style + "([a-zA-Z\-]{2,6})\b");
	body.className = body.className.replace(regex, "");
	if (!restore) {
		body.className += " " + style + to;
	}
}

This will add a class style attribute to the body element, in the form of:

translated-to-{{ language code }}

Now, when you translate to, lets say, Arabic, the body element will be like this:

<body class="home other-styles translated-to-ar">

The styles have to be applied under the translated-to-ar style class, for instance:

You should go to:

Advanced > General > Custom CSS

To change to RTL, use:

body.translated-to-ar {
	direction: rtl;
	unicode-bidi: embed;
}

To change the font, use:

body.translated-to-ar {
	font-family: "Open Sans",Arial,sans-serif;
	font-size: 14px;
}

If it doesn't work as you expect and/or if you don't understand how it works, then you can contact the author of your theme to help you do this, as how the text is displayed is within the theme scope.

First, make sure to watch the installation video.

If you have a cache/minifier plugin, make sure to clear its cache.

If still doesn't show up, add a text widget (with a test text) in the same widget area you chose to place the language switcher. And see if the test text shows up. If it doesn't show up, then that widget area isn't being rendered by the theme, so you should contact your theme provider.

If the test text does show up, but the translator doesn't, then please contact support by following the instructions given in (make sure to provide the test text too):

https://codecanyon.net/item/ajax-translator-revolution-dropdown-wp-plugin/3400269/support/contact

You can automatically fire the translation when the page loads. You should go to the plugin's admin page and then to:

Advanced settings > General > Javascript callbacks > On initialize callback

Copy/paste the following code (replacing the current content):

function(translator, options) {
	if (jQuery.cookie("translator-dropdown-" + options.id + "-to") != undefined) {
		return;
	}
	setTimeout(function() {
		var lang = "es";
		translator._links.filter("." + options.languageSelectorClass + lang).click();
	}, 200);
}

This code will fire the translation to Spanish. For other languages, please follow this link.