TradeGear – AI Translation & Multilingual Customer Assistant

Changelog

0.13.4

• Installing or activating the plugin no longer changes any address on your site. Language addresses such as /es/ are handled only while translation is live, or in test mode for you and test-link visitors. Before, a fresh install answered every /es/ address with the untranslated page, which could take those addresses over from another translation plugin.
• Yoast SEO and Rank Math sitemaps list translated pages under their language again; 0.13.3 served them unchanged.
• SEO verification follows the redirect Yoast SEO and Rank Math put on WordPress’s sitemap, reads each language’s first sitemap of pages, and reports every address the site does not serve instead of leaving it out of the report. Each line is named after what it checks.
• TradeGear can ask the website to warm a language again: the plugin runs its usual warm-up and reports back when it is done.
• A Contact link on the settings page: info.tradegear@gmail.com.

0.13.3

• Requires WordPress 6.9 or later. Translated pages and the language switcher now go through WordPress’s own template output buffer instead of a buffer the plugin opened itself.
• WooCommerce cart fragments and notices are translated through WooCommerce’s own filters, and translated sitemaps through WordPress’s sitemap entry filters, instead of rewriting the finished response. A sitemap made by another plugin is served as it is under a language prefix.
• The debug overlay’s styles are an enqueued stylesheet instead of a style element written into the page.

0.13.2

• Switching Business knowledge off now withdraws what the assistant was given, as the privacy policy says, instead of only stopping updates: the assistant is asked to forget this website’s content once, and asked again until it confirms. A website that never shared anything sends nothing, and one that switched it off before this release has its content withdrawn after updating. The settings page says whether the content has been forgotten yet.

0.13.1

• A translation written back into structured data (JSON-LD) or another inline script now has its angle brackets escaped, so text containing “” can never close the script element early, whatever slash style the page’s own block uses.

0.13.0

• Every class, function, cookie, query parameter, cron interval and database table now carries the tradegear prefix (the WordPress.org directory requires a unique prefix). The translation tables are renamed in place on upgrade with every row kept; the sd_translate option and hook names are unchanged, so nothing needs re-pairing.
• Configuration constants are read by their TRADEGEAR_* names; the SD_TRANSLATE_* and SD_ASSISTANT_* names still work. The optional PHP overrides file in the uploads directory is no longer loaded — define the constants in wp-config.php or a must-use plugin instead.
• Deleting the plugin from the WordPress.org package no longer fails on a missing file.
• The language switcher’s style and script are enqueued as files instead of written into every page; every attribute the plugin writes into a page (language codes, canonical, hreflang and Open Graph URLs) is escaped at output; the language and test cookies are marked Secure on HTTPS sites.
• Table creation no longer runs on every admin request, only until the schema version is recorded.

0.12.1

• The whole-website translation keeps collecting while the translation service is still working through the pages, instead of stopping after 40 minutes. It gives up only when nothing has moved for 15 minutes; anything left then arrives with the regular five-minute check.

0.12.0

• Adding, clearing or restoring a language now translates the whole website in the background instead of waiting for each page’s first visitor, who used to read it in English. Each page is rendered once for every new language, and the plugin collects the translations as they are finished rather than waiting for its five-minute check.
• A translated page still waiting for part of its text is no longer stored by page caches (no-cache headers, DONOTCACHEPAGE, batcache and LiteSpeed Cache), so a cache cannot keep serving it half in English.

0.11.4

• Switching off both the catalogue and pages under Assistant knowledge now clears what the assistant knows about the website, instead of leaving it answering from content the shop has withdrawn. Content that disappears while a source is still switched on is still never pushed as an empty snapshot.
• A visitor asking in a language the assistant no longer answers in (one just removed in the TradeGear dashboard) is told so and pointed to the shop, instead of being told the assistant is temporarily unavailable and asked to try again.

0.11.3

• A product review, or any form, sent from a translated page now reaches WordPress: links and redirects to WordPress’s own scripts (wp-comments-post.php and the like) and folders never carry the language, whatever the saved link exclusions say.

0.11.2

• Translated pages no longer add the language to links into wp-content, such as a product image’s full-size view, which then failed to load.
• The mini-cart and other WooCommerce cart updates on a translated page now arrive in that page’s language instead of the website’s own, and a cart shown on one language’s pages is no longer replayed on another’s.
• The language menu and the test link keep a website’s port, so a shop served on a non-standard port stays on itself.
• When the shop’s plan no longer covers the assistant, visitors are told to contact the shop instead of being asked to try again.

0.11.1

• The settings page now says when TradeGear no longer accepts this website’s connection because it was disconnected or replaced in the dashboard, and tells you to connect again with a new code. A service outage is no longer reported the same way.
• If TradeGear still has the website paused after the plugin was switched back on, the next automatic refresh asks it to resume, instead of leaving the site paused until the plugin is switched off and on again.

0.11.0

• Switching the plugin off now tells TradeGear that this website has left: the service pauses the site and pauses subscription billing, so an invoice raised while it is paused is voided rather than charged. Activating the plugin again reports the website as back and resumes both on the same credentials, with no re-pairing.
• Deleting the plugin reports the same departure once more. Nothing is erased either way — settings, translation tables and remote knowledge are all retained.
• Correct this readme and the WordPress privacy-policy text, which both previously said deactivation did not affect a subscription.
• Rewrite the description and FAQ to explain what the plugin does, what the assistant uses, and the Free allowance and paid plans, and add a Screenshots section.

0.10.0

• Rename the plugin and canonical distribution to TradeGear while preserving existing settings and data.
• Add service disclosures, licence metadata, safer input handling and prepared database identifiers.
• Make the public credit link a local opt-in, off by default.
• Link Settings to the hosted dashboard and guide signup back to the WordPress connection form.
• Simplify setup around one connection code, hide manual credentials by default and report authenticated account-setting refreshes.
• Replace the settings page with one connection panel, three feature controls and collapsed advanced options; a page save can no longer set a credential.
• Check knowledge synchronization weekly instead of twice daily, and remove the manual synchronization control and its endpoint. Content changes still queue an earlier automatic update.
• Report the last synchronization, its document count and the next scheduled check on the settings page.
• Link the account page, privacy policy and service terms from the settings page, and correct the translation disclosure in this readme.