NewTXT Translate installs a WordPress-native integration for NewTXT. It injects the hosted widget loader, verifies and self-repairs plugin-owned database tables, stores local source and translation hashes, uses the WordPress Object Cache API, serves ready translated path URLs, and exposes a signed callback endpoint for controlled cache and sync operations.<\/p>\n\n
The public loader follows the current NewTXT appearance and placement settings automatically. Fixed positions need no theme changes. For inline placement, add a WordPress Shortcode block containing The plugin connects with one dashboard-issued API key. NewTXT verifies the registered domain before the plugin stores the remaining server-side credentials and synchronizes account settings. Only the public key is rendered into the widget script tag; API keys, private keys, and callback secrets remain in the plugin-owned settings table with a non-autoloaded WordPress compatibility backup.<\/p>\n\n This plugin depends on the NewTXT hosted translation service. Installing the plugin alone does not transmit site content. Data is transmitted after a site administrator connects the plugin or when the connected widget and translation features are used.<\/p>\n\n The plugin sends authenticated server-to-server requests to the NewTXT API at https:\/\/api-v1.newtxt.io. Connection sends the current WordPress site URL and the dashboard-issued API key so NewTXT can verify the registered domain and issue domain-bound credentials. Later requests may send the public page path, requested language, URL mode, bounded public-page SEO metadata, cache instructions, usage requests, and allow-listed language or widget settings. These requests are required to synchronize the account, render or retrieve translations, manage translated-page caches, and run administrator-requested tools.<\/p>\n\n Public pages download the hosted widget loader and configuration from https:\/\/cdn.newtxt.io. When client-side translation is required, the loader may send visible translatable public-page text, public page context, and eligible public image references to NewTXT translation endpoints. The loader is executable JavaScript provided as part of the documented NewTXT service. It must not be enabled on private, account, checkout, or other personalized pages.<\/p>\n\n NewTXT service use is governed by the following policies:<\/p>\n\n The plugin stores domain-bound credentials, settings, translation artifacts, public-page hashes, callback audit records, and optional public HTML snapshots in plugin-owned WordPress tables and upload storage. Full source HTML storage is disabled by default. Source capture skips logged-in visitors, password-protected content, query-string requests, and responses marked private or non-cacheable. Deactivation preserves this data. Administrators can opt in to deleting plugin-owned data during uninstall.<\/p>\n\n\n No. The plugin uses WordPress hooks, plugin-owned tables, options, and upload storage.<\/p><\/dd>\n No. Only the public key is emitted in the widget script tag.<\/p><\/dd>\n After an administrator connects the plugin, authenticated requests may include the registered site URL, public page paths, requested languages, URL mode, bounded public-page SEO metadata, cache instructions, and allow-listed project settings. The hosted widget may send visible translatable public-page text and eligible public image references when client-side translation is required. See the External services section and NewTXT Privacy Policy for details.<\/p><\/dd>\n The translated URL fails closed with Yes. Register the complete local origin, including its port, and connect the issued keys in WordPress. Localhost uses client-side path translation and preserves the current loopback host and port. Remote crawling and SEO publication require a publicly reachable test URL.<\/p><\/dd>\n\n<\/dl>\n\n\n Replaced the plugin-owned response buffer with the WordPress template enhancement output buffer available in WordPress 6.9 and later, preventing an unclosed buffer from remaining on the shared output-buffer stack.<\/p>\n\n Packaged the completed WordPress.org compliance and security improvements as a new plugin release, including privacy-aware source capture, idempotent signed callbacks, WordPress Filesystem API writes, administrator JavaScript localization, external-service disclosures, and verified WordPress 7.1 compatibility.<\/p>\n\n Completed the WordPress.org compliance pass with strict callback request validation and replay protection, privacy-aware source capture, cached plugin-owned reads, prepared custom-table identifiers, WordPress Filesystem API writes, administrator JavaScript localization, privacy-policy guidance, a comprehensive WordPress Coding Standards gate, and runtime smoke coverage. Verified the distribution archive with WordPress Plugin Check, WordPress 7.1, desktop and mobile layout checks, and a published NewTXT Privacy Policy.<\/p>\n\n Reduced text, select, language picker, search, and color control height and spacing across the plugin while preserving larger touch targets on narrow screens. Replaced the technical callback Dashboard metric with the active account plan and added used-versus-remaining language and monthly word capacity. Added WordPress.org external-service and privacy disclosures, reduced source-capture database writes, excluded personalized responses, hardened callback replay protection, completed administrator JavaScript internationalization, and adopted the WordPress Filesystem API for activation storage files.<\/p>\n\n Rebuilt the connected WordPress experience around the NewTXT service console: compact product navigation, live integration signals, service-style page headings, six-column operational metrics, quieter working panels, and responsive dashboard, settings, language, appearance, onboarding, and widget preview surfaces.<\/p>\n\n Made the appearance preview render through the same hosted runtime used on public pages, added searchable single- and multi-language selectors, added an explicit reversible widget disable action, and surfaced monthly translation usage with an exhausted-limit warning.<\/p>\n\n Split the NewTXT administration into dedicated Dashboard, Connection, Languages, Widget appearance, Local storage, Signed callback, Tools, and Settings pages. Added signed server synchronization for source and target languages, routing, widget availability, and visual settings with server-side validation and a responsive live appearance preview.<\/p>\n\n Added a required first-run connection wizard, server-verified token step, post-connection welcome screen, and separate Settings page for token replacement and NewTXT plan management. Existing credentials remain active unless a replacement token passes format and registered-domain verification.<\/p>\n\n Protected the fixed NewTXT API route, CDN loader, integration identity, signing credentials, callback security, and account-managed language and routing values from WordPress settings changes. Replaced technical inputs with read-only synchronization status while keeping local storage, delivery, callback enablement, uninstall, and tool controls available.<\/p>\n\n Added domain-bound one-key onboarding, automatic credential and account-setting synchronization, a WordPress option in the NewTXT onboarding wizard, and a focused quick connection interface with advanced technical fields kept available for troubleshooting.<\/p>\n\n Aligned dashboard action icons and labels, normalized WordPress button geometry, and improved long callback URL and storage path presentation with copy-friendly data controls.<\/p>\n\n Redesigned the WordPress dashboard to match the NewTXT service visual system, added launch progress and responsive status surfaces, improved settings focus and save feedback, and made tool fields adapt to the selected operation.<\/p>\n\n Added a reproducible WordPress distribution archive build, verified compatibility with WordPress 7.1, moved uninstall cleanup to the WordPress filesystem API, and kept admin notices readable inside the custom dashboard header.<\/p>\n\n Added bounded source SEO metadata capture for title, description, Open Graph, and Twitter fields, passed stored metadata into translated render requests, and exposed account-aware image capture and replacement checks.<\/p>\n\n Added a WordPress-native admin dashboard with status summaries, section navigation, responsive styling, and a tool for pulling account-managed settings from NewTXT.<\/p>\n\n Initial development version with activation schema, settings, widget loader, signed callbacks, local hashes, rendered page snapshots, source hash capture, and WP-CLI commands.<\/p>","raw_excerpt":"Connect WordPress sites to NewTXT translation widgets, local hashes, server-side rendering, and signed callbacks.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/sq.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/361440","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sq.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/sq.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/sq.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=361440"}],"author":[{"embeddable":true,"href":"https:\/\/sq.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/galdarturin"}],"wp:attachment":[{"href":"https:\/\/sq.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=361440"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/sq.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=361440"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/sq.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=361440"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/sq.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=361440"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/sq.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=361440"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/sq.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=361440"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}[newtxt_widget]<\/code>, add data-newtxt-widget-slot<\/code> to an existing page-builder element, or use an HTML anchor matching the configured container ID.<\/p>\n\nExternal services<\/h3>\n\n
\n
\n
newtxt-translate.zip<\/code>.<\/li>\n\n
Does this plugin modify my theme?<\/h3><\/dt>\n
Does the browser receive private keys?<\/h3><\/dt>\n
What data is sent to NewTXT?<\/h3><\/dt>\n
What happens when translated HTML is incomplete?<\/h3><\/dt>\n
noindex<\/code> headers and is not treated as ready.<\/p><\/dd>\nCan I test the widget on localhost?<\/h3><\/dt>\n
0.9.4<\/h4>\n\n
0.9.3<\/h4>\n\n
0.9.2<\/h4>\n\n
0.9.1<\/h4>\n\n
0.9.0<\/h4>\n\n
0.8.0<\/h4>\n\n
0.7.0<\/h4>\n\n
0.6.0<\/h4>\n\n
0.5.1<\/h4>\n\n
0.5.0<\/h4>\n\n
0.4.1<\/h4>\n\n
0.4.0<\/h4>\n\n
0.3.1<\/h4>\n\n
0.3.0<\/h4>\n\n
0.2.0<\/h4>\n\n
0.1.0<\/h4>\n\n