• Hi Ernest,

    I’m the guy who has translated your plugin into German. Unfortunately, I have noticed, that the Shortcode for multilingual strings does no longer work.

    For example:

    [:de]Was suchst Du?[:en]What are you looking for?

    was previously rendered as a clean string but is now rendered as above.

    So.. my question: Did you remove the interpretation for qTranslate-X strings ?

    If yes, why?

    qTranslate-X a free plugin and that’s very nice. I’d be a poor homeless guy in case I would have to pay for every plugin.

    In case WPML is only supported in the future, then that’s a reason for me to turn away from ajax search lite.

    Thanks, Best Regards

    Toby

    https://www.ads-software.com/plugins/ajax-search-lite/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author wpdreams

    (@wpdreams)

    Hi Toby!

    The Qtranslate X support was not removed, it should work.

    I can only think of one possible cause. If you have the custom ajax handler activated, try de-activating it on the Performance options panel: https://i.imgur.com/HXFW31w.png

    Thread Starter Clickadelic

    (@clickadelic)

    Hi Ernest,

    Thank you so much for your quick reply. I have just checked your hint and turned the custom ajax handler on/off.

    Unfortunately, there is no change in the behaviour:

    I’m still getting the unrendered strings in the search input field.
    [:de]Was suchst Du?[:en]What are you looking for?

    I’m getting this behaviour on two different, independent sites. Sorry for the subtile frustration in my first request yesterday.

    Again, thank you for all your hard work.

    I think the error occurred after a WP Update, so downgrading is not an option.

    I think I still need to fiddle around to find a solution. ??

    T

    Plugin Author wpdreams

    (@wpdreams)

    Let me try to re-create the issue on a test environment. If I’m able to re-create the problem, then I will certainly find the cause as well.

    I’m already working on a minor bug-fix release. If I could find and fix this, I will of course include it within that update.

    Plugin Author wpdreams

    (@wpdreams)

    I might have found the solution. So on my test envirnomnent I was getting similarly strange results, then I remembered that there is an option in qTranslatex that should be enabled by default.

    Go to the Settings->Languages menu, and navigate to the Integration panel. On the bottom there is a checkbox to enable Compatibility Functions. That did the trick for me: https://i.imgur.com/7DrhnMc.png

    I remember I had noted this as a possible issue to fix, but somehow it got lost and I of course forgotten it as I always do. I will look into a solution that does not require enabling the Compatibility Functions in qtranslatex.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Remove of support for qTranslate-X?’ is closed to new replies.