acub

As far as I know, the guys @ iCanLocalize are quite open and helpful for any theme author wanting to WPML-ize.

As of now Customizr is not wpml compatible and Nikeo (the theme author) is the only one who can give you an estimation in this matter.

Well, yes.

The conditional on the filters in the current version is:

if ( current_theme_supports( 'qtranslate' ) && is_plugin_active('qtranslate/qtranslate.php') ) {
// filters here...
}

and… qtranslate/qtranslate.php is not an active plugin when it is replaced by mqtranslate. With the right conditional it works flawlessly.

Interesting. You didn’t even bother testing it. Well, I guess you’re right and I was wrong…

…to do it.

My bad. Won’t happen again.

Here. Working pagination.

Just pulled and committed mqtranslate support to Customizr github.

This basically means the code above will be unnecessary starting with next theme release, as it would double filter the slider texts.

I believe you used his second solution, not the first one. The first one should have problems with posts pagination. That was the “query switching solution”.

That’s what query_posts() does. It replaces (switches) the main query.

And now I just noticed he said it’s good only if you don’t need pagination. Initially I only looked at the code and I thought he didn’t know this.

I don’t see any artefact in IE11, on W7 Ultimate, fully updated. I thought you’re referring to the fact that the image margins are uncovered upon hover and it looks cut. But I don’t see any artefact in IE11.

And yes, you could use it with rdell’s solution, in the sense that you could place his code inside the media query from mine, for disabling it on screens narrower than 980px.

For the IE10 links problem, here‘s a snippet.

The theme supports qtranslate and polylang translations out of the box. If you use mqtranslate, you need to add this to your child theme’s functions.php:

if ( is_plugin_active('mqtranslate/mqtranslate.php') ) {
	add_filter( 'tc_slide_link_url' , 'tc_url_lang' );
	add_filter( 'tc_logo_link_url' , 'tc_url_lang');
	add_filter( 'tc_fp_link_url' , 'tc_url_lang');
	add_filter( 'tc_slide_title', 'tc_apply_qtranslate' );
	add_filter( 'tc_slide_text', 'tc_apply_qtranslate' );
	add_filter( 'tc_slide_button_text', 'tc_apply_qtranslate' );
	add_filter( 'tc_slide_background_alt', 'tc_apply_qtranslate' );
	add_filter( 'tc_fp_text', 'tc_apply_qtranslate' );
	add_filter( 'tc_fp_button_text', 'tc_apply_qtranslate' );
	add_filter( 'tc_slide_title_length'  , 'tc_remove_char_limit');
	add_filter( 'tc_slide_text_length'   , 'tc_remove_char_limit');
	add_filter( 'tc_slide_button_length' , 'tc_remove_char_limit');
	add_filter( 'tc_fp_text_length' , 'tc_remove_char_limit');
}

Now you can add syntaxes like

[:en]English text here[:de]Deutsch text hier[:fr]Texte français ici

in your slider titles, descriptions and buttons and also (most importantly) they do not have a char limit anymore).

You only need the above code for mqtranslate (a newer fork of qtranslate). If you use qtranslate you don’t need those filters, they’re on by default, the moment you activate qtranslate.

As for polylang, I don’t know the details, I just know it works with Customirz. If you use it, hopefully someone will share some insight if you can’t make it all work.

Note for @nikeo: I switched most of my Customizr websites from qtranslate to mqtranslate and I believe more and more people are making this switch everyday, as qtranslate is no longer maintained and needs a few manual tweaks on every WP update. So I guess adding an || is_plugin_active(‘mqtranslate/mqtranslate.php’) to the qtranslate conditional for the filters above would be a very welcome addition in some future Customizr update. Thank you.

You most probably have a virus on the device that displays those nasty ads. They are not due to the theme. They are most probably added by your device after the page has been rendered by the server.