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.