barnux

Yeah, as I said, that is working now.

Just for reference, I tried to replicate what I did before in Polylang with WPML and it works as expected: every change done when in All languages is automatically saved in every single language, overwriting those options.

I’m not sure I get what you are asking for, could you elaborate?

When I make some changes in the Avada options and I save them, I see the changes on the frontend, that works fine, but only for the default language set in the Polylang preferences. But, according to what the devs say, if I have 2 or more enabled languages and I change something when in All languages, that change should be saved in all the languages in one shot, instead of manually change that thing 2 or more times. This is what is not working.

Another example I just tried now: I have English and Italian as activated languages in Polylang. The default language in the Polylang settings is Italian. If I’m in the All languages page of the Avada options and I change the site width from 940px to 1000px, for instance, I expect the width in the frontend to be changed in both the Italian and the English version of the website (that’s because I’m modifying the All languages options, right?), but instead the site width is modified in the Italian site only, and I guess that’s because Italian is my default language in Polylang. When I change the default language to English and try to do the same, the width only changes for English but not for Italian, and again this is not the expected behaviour if I have understood correctly what the Avada developers said it should be.

So my point is, the Avada options for the single languages work and they are saved just fine. It is the All languages page that is not saved site-wide and does not overwrite the options for all the single languages.

As I said in my last post, I asked the Avada developers how the options are supposed to work when multiple languages are active in Polylang. Their answer (https://goo.gl/8GkVPw) was basically what I expected:

If you make changes on the “All languages” theme options panel ALL theme options will be written to ALL languages, so you will end up with all options being the same on all 3 langs. So if you only want to change one specific opion, yu will have to do it on per language basis.

So, to keep the example I used in the Avada forums: when I’m in the Avada options panel and I change the number of footer columns when in Show all languages, the columns should change in all the active languages, but from what I tested, it only changes for the main language that is set in the Polylang settings, every other language is not affected by the change (I tested this with every cache plugin and also the browser cache deactivated, of course).

I don’t know if this is an issue to be fixed on the Polylang or the Avada side, but it’s definitely something to check.

(using Polylang v1.6.1.6)

The issue seems to be solved now, thanks.

The search works fine on my website, the languages are set from the directory name.

From what I understand, every language has its own options that are independent from those of the other languages, so modifying something when the topbar shows “All languages” is useless, but I asked confirmation in the Avada forums.

I’m using Avada 3.7 with Polylang 1.6.1.5.

Same here, I’m following the thread on Theme Fusion’s forum. This is a serious issue and I hope it gets resolved ASAP, I already know what Chouby thinks (Avada is a commercial theme, not free) but it’s probably the best-selling theme ever, if Polylang plays nice with it, it would all work to the plugin advantage, right now it is maybe the only serious contender to the expensive WPML.

An update from the Calendarize It developers:

just remove these three lines from the file rrecur-parser.js in the calendarize-it/js folder (lines number 27, 28 and 29):

var r = jQuery.inArray(test_var,this);
return (r!=undefined && (r != -1)) ;
//-- orginal:

That should do the job, at least until they issue the next update of their plugin.

Nevermind, now it’s working.