Title: Axial Text Post Translation Author: Axial Global LLC Published: November 8, 2026 Last modified: November 8, 2026 --- Search plugins ![](https://ps.w.org/axial-text-post-translation/assets/banner-772x250.png?rev=3791520) ![](https://ps.w.org/axial-text-post-translation/assets/icon-256x256.png?rev=3791520) # Axial Text Post Translation By [Axial Global LLC](https://profiles.wordpress.org/axialar/) [Download](https://downloads.wordpress.org/plugin/axial-text-post-translation.1.3.11.zip) * [Details](https://wordpress.org/plugins/axial-text-post-translation/#description) * [Reviews](https://wordpress.org/plugins/axial-text-post-translation/#reviews) * [Installation](https://wordpress.org/plugins/axial-text-post-translation/#installation) * [Development](https://wordpress.org/plugins/axial-text-post-translation/#developers) [Support](https://wordpress.org/support/plugin/axial-text-post-translation/) ## Description Axial Text Post Translation enables WordPress editors to request translations of individual WordPress posts through the external AXIAL translation service. Each completed translation is stored as a separate WordPress post and published automatically. Visitors can switch between existing published translations, but cannot request or pay for new translations. Main features: * Independent translation API configuration; the audio narration plugin is optional. * Available languages come directly from the configured AXIAL API profile. * Separate post and permalink for each translated language. * Language buttons with names and flags, and hreflang links for published translations. * Optional placement alongside AXIAL Audio Post Narration when compatible. * Asynchronous translation jobs collected through WP-Cron. * Axial Components administration menu shared with other installed AXIAL plugins. #### External service, data sharing and credits Generating translations requires a separately configured AXIAL translation API account, which may have paid credit usage. The plugin makes outbound HTTPS requests to the configured endpoint (default: https://axial.ar/apis/v1/translation-management). It sends the configured account email and API credential for authentication, post title, post content, optional excerpt, language identifiers and job identifiers. It receives available language profiles, job status, translated content and available account credit balance when provided. These requests occur when an authorized editor tests a connection, accesses the API-dependent administration features or requests and retrieves translations. Visitors never trigger paid translation requests. For information about the service, pricing and data processing, see https://axial. ar/ and https://axial.ar/ayuda-preguntas-frecuentes/. The AXIAL privacy policy is at https://axial.ar/es/politica-de-privacidad/. Contact: info@axial.ar. You must have the rights to submit any content for translation. Plugin code is GPLv2-or-later; the external translation service is separate. #### Editorial workflow An editor with permission to edit the source and publish posts selects a language available from the configured API and starts a translation. When the translation finishes, a separate published post is created or updated only if the requesting editor still has appropriate permissions. Older queued jobs without a recorded editor are not published automatically. Review translations and consider your publication’s editorial standards before requesting automatic publication. Complex builder content, custom HTML and shortcodes require verification. The translation job polling process requires a working WP-Cron setup. A site administrator should verify scheduled tasks after upgrading. When the original changes, existing translations may require editor- initiated updates. ### Privacy Only a site administrator can configure the account and external HTTPS API connection. When an authorized WordPress editor requests a translation, the original post title, content and optional excerpt are sent to AXIAL along with language profile IDs, the account email and bearer token. Polling sends the translation job ID. Testing the connection sends account credentials. The external API may bill credits per request. The WordPress plugin does not contact AXIAL for public visitors and does not download executable code from the service. See https://axial.ar/es/politica- de-privacidad/ for the external service privacy policy. The site administrator should disclose this processing to contributors and avoid sending content without authorization. ## Screenshots [[ [[ [[ [[ [[ [[ [[ [[ [[ [[ [[ [[ [[ ## Installation 1. Install the ZIP via Plugins > Add New > Upload Plugin, then activate it. 2. Go to Axial Components > Post Translator. 3. Confirm the preconfigured HTTPS endpoint or edit it if AXIAL has provided a different one. 4. Enter the AXIAL translation API account email and key and save. 5. Click Test Translation API to check the connection and available languages. 6. Edit a WordPress post and request a translation in an available target language. 7. Once the job completes, review the newly published translated post and the public language selector. Step-by-step guide: https://axial.ar/articulos-de-ayuda/guia-axial-post-translator- wordpress/ ## FAQ ### Can visitors initiate a translation? No. Only authorized WordPress editors can request translations. Visitors can navigate published translations. ### Can I use the plugin without Post Narration? Yes. Post Narration is optional and independently configured. ### Where do I select available languages? Configure languages in the AXIAL API profile. The plugin displays only the languages returned by that API. ### Are completed translations published automatically? Yes. Completed jobs create or update published WordPress posts. The editor must have permission to publish posts and initiates each translation request. ### Can I change the AXIAL API endpoint? Yes. The endpoint defaults to https://axial.ar/apis/v1/translation-management and remains editable in plugin settings. ### Where can I find help? Setup guide: https://axial.ar/articulos-de-ayuda/guia-axial-post-translator-wordpress/ Platform FAQ: https://axial.ar/ayuda-preguntas-frecuentes/ ### Source code and build process The complete, original, human-readable source for all of the plugin’s own JavaScript and CSS is included in this ZIP: * assets/js/admin.js – administrator API test and editor translation actions. * assets/js/frontend.js – optional unified toolbar with AXIAL Audio Post Narration. * assets/css/frontend.css – language selector and toolbar styles. These are source files, not generated/minified copies. No npm, Webpack, Composer, bundler, external library, or build process is required. The files are loaded directly by the WordPress enqueue APIs. The PHP source code is included as well. A public GitHub repository is not required to inspect or build this plugin. The plugin package never embeds a private API credential or downloads executable code from AXIAL. A configured API account is needed only to request translations from the service. Updating this plugin retains existing WordPress settings, credentials, translated posts, relationships, and outstanding jobs. Uninstalling removes the translator’s API settings and credentials but retains existing translated posts and their relationships, as well as account-level balances used by other AXIAL components. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “Axial Text Post Translation” is open source software. The following people have contributed to this plugin. Contributors * [ Axial Global LLC ](https://profiles.wordpress.org/axialar/) [Translate “Axial Text Post Translation” into your language.](https://translate.wordpress.org/projects/wp-plugins/axial-text-post-translation) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/axial-text-post-translation/), check out the [SVN repository](https://plugins.svn.wordpress.org/axial-text-post-translation/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/axial-text-post-translation/) by [RSS](https://plugins.trac.wordpress.org/log/axial-text-post-translation/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.3.11 * Escape administrator connection-status translations at their HTML output location. * Verify a request-level nonce before reading submitted translation form fields, and continue verifying the specific post-and-language nonce before starting work. * Preserve existing editor capabilities, asynchronous translation workflow, language selector, existing posts and AXIAL Audio Post Narration integration. #### 1.3.10 * Sanitize the post ID and requested language directly at the raw POST input boundary. * Fix translation controls in the editor by using WordPress AJAX rather than nested HTML forms. * Enforce post editing and publishing capabilities both when requesting a job and when an asynchronous job completes. * Keep legacy pending jobs from publishing automatically without verified editor permissions. * Internationalize the translation controls, API messages and important interface strings. * Remove translation API credentials on uninstall while preserving existing translated posts and shared AXIAL component settings. #### 1.3.9 * Ship complete, unminified and documented JavaScript and CSS source files, with no build step. * Fix the administrator settings-screen hook, so the API connection test loads properly. * Improve input validation, response handling and PHP code readability without changing saved options or post metadata. * Retain AXIAL API request behavior, translation job processing and optional audio integration. #### 1.3.8 * Load administrator scripts only on the registered settings screen using its WordPress hook suffix. * Load frontend and admin JavaScript and styles through the WordPress enqueue APIs. * Align the contributor username with the plugin owner. #### 1.3.6 * Prepare the approved unified audio and language toolbar integration for plugin review. * Preserve the official WordPress.org plugin identity and editorial translation workflow. #### 1.3.5 * Maintain the official plugin identity and installation paths; compatibility release with no changes to translation behavior. #### 1.3.4 * Keep audio controls and languages in distinct sibling zones of a single toolbar. #### 1.3.3 * Place language flags to the right of the compact narrator in one shared row, keeping playback controls uninterrupted. #### 1.3.2 * Prefixed the post metadata hook variable to comply with WordPress coding standards. #### 1.3.1 * Replaced slow postmeta queries with a cached WordPress API relationship index. * Invalidate the index when post relations, job state or post status changes. * Kept existing translation links, publishing and AXIAL API integration. #### 1.3.0 * First WordPress.org submission. * Editorial post translations through the AXIAL API. * Shared Axial Components administration and credit balance display. * Published translation language selector with flags and optional audio bar integration. ## Meta * Version **1.3.11** * Last updated **1 day ago** * Active installations **Fewer than 10** * WordPress version ** 6.0 or higher ** * Tested up to **7.1.4** * PHP version ** 7.4 or higher ** * Tags * [AI](https://wordpress.org/plugins/tags/ai/)[multilingual](https://wordpress.org/plugins/tags/multilingual/) [news](https://wordpress.org/plugins/tags/news/)[posts](https://wordpress.org/plugins/tags/posts/) [translation](https://wordpress.org/plugins/tags/translation/) * [Advanced View](https://wordpress.org/plugins/axial-text-post-translation/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/axial-text-post-translation/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/axial-text-post-translation/reviews/) ## Contributors * [ Axial Global LLC ](https://profiles.wordpress.org/axialar/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/axial-text-post-translation/)