• Resolved jstneti

    (@jstneti)


    I initially reported some issue that I later realized was from leftover gTranslate test, even though the plugin was deactivated.

    So, the only thing that isn’t working and I can’t get it to work is the “Chrome Built-in AI”. I can’t install the languages. The content is in Slovenian and needs to be translated to English (UK) and Italian. I installed the language packs from the link in admin but it didn’t help. Checking in console I can see that none of the langauges were installed.

    How to fix that?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Aniket Dogra

    (@aniketji)

    Hi @jstneti ,

    Thanks for sharing the detailed feedback.

    It looks like you’re using another translation plugin (possibly GTranslate) alongside Polylang and our plugin. The “Error 402: Payment Required” message you’re seeing is not generated by our plugin — it’s coming from GTranslate, which requires a paid plan for full functionality.

    Please try deactivating any other translation plugins (like GTranslate) and check again. Our plugin is fully compatible with Polylang (free), but conflicts can happen when multiple translation systems are active.

    Regarding the translation button being grayed out:

    • Our plugin does not limit you to translating only one post. However, the free version allows up to 500,000 characters total.
    • Could you please share a screenshot of where the translate button is disabled?
    • Also, try clicking on the grayed-out button to see if any popup or message appears. That could help us understand what’s blocking it.

    About the 301 redirect issue on the English version – that’s quite unusual. We haven’t encountered this problem in standard setups. If possible, please let us know:

    • The original page title
    • Which language is assigned to that post
      So we can try to replicate and verify the issue on our end.

    Lastly, we are aware of the issue with Chrome’s built-in AI translation and are working on a smoother activation flow for supported languages. We’ll provide updates on that soon.

    You can also try testing our plugin on a staging environment with only Polylang + our plugin active, to rule out any conflicts.

    Let us know how it goes – we’re here to help!

    Best regards,
    Aniket Dogra

    Plugin Support Aniket Dogra

    (@aniketji)

    Hi @jstneti ,

    Thanks again for your feedback!

    We wanted to let you know that we’ve fixed the issue related to Chrome’s built-in AI translation not working. 🎉 This has been resolved in our latest release — version 1.4.4.

    Please update to the latest version of our plugin, and the Chrome Local AI Translator should now work as expected.

    Also, could you please confirm if your previously reported issue (related to the grayed-out translate button and 301 redirect) has been resolved? If you’re still facing any difficulties, feel free to share more details — we’re happy to help further.

    Looking forward to your update!

    Best regards,
    Aniket Dogra

    Thread Starter jstneti

    (@jstneti)

    Thanks for the update.

    I was sure I replied but I guess not. I confirm that the grayed-out button and 301 redirects were from another plugin even though the plugin was deactivated during testing. Only after uninstalling that plugin, the issues went away.

    Plugin Support Aniket Dogra

    (@aniketji)

    Hi @jstneti ,

    Thank you for the update and for confirming that the grayed-out button and 301 redirect issues were caused by another plugin. We’re glad to hear that uninstalling it resolved the problem!

    Also, now that the Chrome AI translation issue has been fixed in version 1.4.4, everything should be working as expected.

    As your original issue has been resolved, we’ll go ahead and mark this thread as closed.
    If you have any new questions or suggestions, feel free to create a new support ticket — we’re always happy to help!

    Thanks again for your support and for using our plugin.

    Best regards,
    Aniket Dogra

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘EDIT: Chrome built-in AI not working’ is closed to new replies.