Forum Replies Created

Viewing 15 replies - 1 through 15 (of 83 total)
  • Hi @kubopraca ,

    Just a quick follow-up — since we haven’t received a reply, we’ll temporarily close this thread.

    If you still need help, you’re always welcome to reopen it or start a new one, and we’ll gladly assist.

    — UAPP Support Team

    Plugin Support Vitalii

    (@uappsk)

    Hi @naryano ,

    Just checking in to see if you had a chance to look into this again or if there’s anything we can help you with. If you’re open to it, feel free to open a support ticket and let us know what you were trying to achieve — we’ll be happy to assist.

    — The UAPP Support Team

    Hello @kubopraca,

    Thank you for your patience. We’ve now picked up your request and started reviewing the issue.

    Unfortunately, the two links you previously shared are no longer accessible, so we’re unable to review the affected content directly.

    To help us investigate why some posts have translated titles but untranslated content, could you please provide updated links (or recreate the examples) and share a few additional details?

    Specifically, it would help if you could let us know:

    1. Whether the translations were created via Auto Translator or manually through Polylang
    2. The source and target languages used
    3. Plugin versions (Auto Translator for Polylang, Polylang, WordPress)
    4. Whether the issue still occurs on newly translated posts

    Once we have this information, we’ll continue the investigation.

    Best regards,
    UAPP Team

    Vitalii

    (@uappsk)

    Hello @kubopraca,

    Just to confirm — it looks like both issues have now been resolved on your side, correct?
    Could you please clarify your current request so we can assist you properly?

    Thank you,
    UAPP Team

    Vitalii

    (@uappsk)

    Hello @markbarna,

    Please let us know if there is anything else we can assit you or we can close this thread.

    Vitalii

    (@uappsk)

    Thank you for the update. The message “API key expired. Please renew the API key” usually appears when Google Cloud rejects the key during validation. Since you already rotated the key, please verify the following three Google Cloud settings — these are the most common causes:

    1. Make sure the API key belongs to the correct Google Cloud project

    The key must be created inside the same project where Cloud Translation API is enabled.

    Please check: Google Cloud → APIs & Services → Credentials And confirm that the project name (top-left) is the same project where Translation API is active.

    If the key was created in a different project, Google will always return that it is expired/invalid.

    2. Confirm that “Cloud Translation API” is enabled

    Go to: Google Cloud → APIs & Services → Enabled APIs & Services

    Search for:

    Cloud Translation API

    If it is disabled → the API key will always fail.

    3. Check the API key restrictions

    When Google rotates a key, it often re-applies old restrictions, and these restrictions may block Translation API.

    Please open your API key settings and check:

    API restrictions:

    – Allowed: Cloud Translation API or “Don’t restrict the key”

    Application restrictions:

    Select “None”

    4. Quick test (no WordPress needed)

    You can immediately test your key by opening this link in a browser:

    https://translation.googleapis.com/language/translate/v2?key=YOUR_API_KEY&q=Hello&target=uk

    If the key is valid, you will see JSON like:

    { “data”: { “translations”: [ { “translatedText”: “Привіт” } ] } }

    If it still fails, please send us the exact error message shown on that test URL (do NOT send your actual key), and we’ll help you further.

    Vitalii

    (@uappsk)

    Hello @markbarna,

    We understand — the official Google documentation can be quite technical.
    While we don’t currently have our own tutorial with screenshots, there is a very clear step-by-step guide you can follow here:

    👉 https://dev-opencart.com/kak-poluch-t-klyuch-ot-google-translate-api-za-5-m-nut

    Best regards,
    UAPP Team

    Vitalii

    (@uappsk)

    Hello @kubopraca,

    Thank you for sharing the details of the issue. We’ve identified the cause and applied a fix.
    Please update the plugin to the latest version and let us know if everything works correctly on your side.

    Best regards,
    UAPP Team

    Hi @kubopraca ,

    We reviewed the plugin but couldn’t reproduce the issue yet. Could you please share step-by-step instructions so we can replicate it on our side?

    To speed things up, please include:

    1. Source/target languages (e.g., Czech → Slovak)
    2. Links or IDs of the affected post(s)
    3. Exact steps you take in Auto Translator/Polylang to trigger the problem
    4. Screenshots of:
      • Polylang settings (Languages, Synchronization)
      • Auto Translator settings (showing the duplicated entries you mentioned)
    5. Plugin versions:
      • Auto Translator for Polylang
      • Polylang (and Polylang Pro if used)
      • WordPress core version
    6. Whether any caching or translation plugins are active (and which ones)

    Once we have these details, we’ll investigate immediately and follow up with a fix or workaround.

    Kind regards,
    UAPP Team

    Hi @kubopraca ,

    Thank you for reporting this issue.
    We’ve reviewed your message and have taken the case into our work scope for investigation. Our team will check the duplication behavior and the untranslated content in the Auto Translator settings and get back to you once it’s resolved.

    We appreciate your patience and for bringing this to our attention.

    Kind regards,
    Auto Translator for Polylang Support

    Plugin Support Vitalii

    (@uappsk)

    Hi @naryano,

    We’re truly sorry to hear about your experience, but we’d like to clarify a few things. All the features and designs shown in our plugin description and screenshots are included in the free plugin and are fully functional. Nothing in the screenshots is “locked” or used as marketing for another plugin — everything you see is available right after installation.

    It seems there may have been some confusion about how to access or customize the styles. Our plugin provides a wide range of settings and tools, and we’re always happy to guide users step-by-step through the process. In fact, we offer free support right here on ww.wp.xz.cn, and our team replies promptly to any questions. Unfortunately, we didn’t receive any support request from you before this review.

    We’re proud that over 100,000 active users find the plugin reliable, easy to use, and exactly as described. If you’d like, we’d be more than happy to assist you in achieving the same results as shown in the screenshots.

    Please feel free to open a support ticket so we can help you directly.

    We hope you’ll reconsider your review once you’ve had the chance to try the plugin with our assistance.

    — The UAPP Team

    Hi @mathiasmadsen

    Please let me know if it helped or any further assistance is needed.

    Thank you

    Hi @mathiasmadsen ,

    We’ve reviewed the issue you encountered while translating a post using the plugin, and the error message from Google Translate API —
    “Requests from referrer <empty> are blocked” — indicates that the API key in use is restricted to requests from specific websites (HTTP referrers), but the translation request is coming from the server and has no referrer (which is expected for server-side requests).

     How to Fix It→This needs to be corrected in your Google Cloud Console:

    1. Log into your Google Cloud Console:
      https://console.cloud.google.com/
    2. Go to: APIs & ServicesCredentials
    3. Find the API key used for the plugin and click to edit it.
    4. Under “Application restrictions”, change:
      • From: HTTP referrers (websites)
      • To: None(or “IP addresses” if you want to restrict it to your server)
    5. Under “API restrictions”, make sure only the Cloud Translation API is enabled for this key.
    6. Save changes.

    Once this is updated, the plugin should be able to successfully send translation requests again.

    Please feel free to reach out if you need further assistance, and don’t forget to leave us a rating and feedback.

    Best regards,
    UAPP Support Team

    Plugin Support Vitalii

    (@uappsk)

    Hi @efishinsea ,

    Thanks again for reporting the issue with the missing file reference in Responsive Tabs v10.0.0 — and for taking the time to investigate and suggest a workaround.

    We’ve now addressed this in the latest release: v10.1.0.
    The erroneous references to the unfinished hover-image-reveal-tabs widget have been safely removed to prevent any further PHP errors.

    You can now update the plugin to version 10.1.0 from your WordPress dashboard.

    We really appreciate your input — it helped us get this resolved quickly.
    Feel free to reach out if you notice anything else or have questions.

    Best regards,

    UAPP Support Team

    Vitalii

    (@uappsk)

    Good afternoon @garfildalex6 ,

    Thank you so much for your contribution and for sharing the updated version of the plugin with the added functionality to translate the fields of the All in SEO plugin. We really appreciate the time and effort you put into this!

    We’re happy to let you know that we’ve just released a new version of the plugin that includes the requested functionality. This means you can safely update the plugin without losing your changes.

    Thanks again for your support and collaboration! Don’t forget to leave us the feedback and rate, so we know we are on the right track.

    Best regards,
    UAPP Support Team

Viewing 15 replies - 1 through 15 (of 83 total)