Forum
Welcome, Guest
Please Login to access forum.
Re:GPTranslate Changelog (0 viewing) 
Go to bottom
TOPIC: Re:GPTranslate Changelog
#8323
John Dagelmore
Admin
Posts: 3877
User Offline
Re:GPTranslate Changelog Karma: 84  
GPTranslate 2.34.5 WP/J6/J6 - 2026/09/07

  • Added: The AI Agent Crawler now automatically pauses the crawl and shows an explanatory message if translation keeps failing on several pages in a row (e.g. due to a rate limit, quota, or API key issue), instead of continuing to process the remaining pages ineffectively

  • Added: New "Request mode" option to choose whether translation requests are made client-side (default, best performance) or server-side (routed through your own server)

  • Improved: Default "Crawler timeout" increased from 30 to 60 seconds, reducing false-positive stops caused by slower AI responses

  • Fixed: In rare cases, if the translation engine returned no usable result for a URL slug segment, the translated alias could end up missing that segment entirely, collapsing to just the language root instead of a proper localized URL. The original segment is now used as a safe fallback instead



CLEAN THE BROWSER CACHE AFTER THE UPDATE
 
Logged Logged  
  The administrator has disabled public write access.
#8327
John Dagelmore
Admin
Posts: 3877
User Offline
Re:GPTranslate Changelog Karma: 84  
GPTranslate 2.34.7 WP/J6/J3 - 2026/09/13


  • Security: Enhanced security system for the AI provider API key — translation requests for every engine (ChatGPT, Claude, Gemini, Grok, DeepSeek, DeepL, Google Cloud Translation) are now always routed through server


  • Fixed: with some newer Claude models, translation requests could silently fall back to Google Translate instead of using Claude. Extended thinking is now explicitly disabled for translation requests and the response is parsed correctly regardless of its position in the reply


  • Added support for Grok 4.6 model


  • Added support for Gemini 3.8 Flash model


  • Fixed: the "og:url" meta tag (used by social media and some SEO plugins) kept pointing to the original-language URL on translated pages instead of the translated one. It's now corrected to the translated canonical URL, both server-side and client-side



CLEAN THE BROWSER CACHE AFTER THE UPDATE
 
Logged Logged  
  The administrator has disabled public write access.
Go to top