Title: qTrad Author: Rafael Minuesa Published: 28 de octubre de 2026 Last modified: 28 de octubre de 2026 --- Buscar plugins ![](https://ps.w.org/qtrad/assets/banner-772x250.png?rev=3771325) ![](https://ps.w.org/qtrad/assets/icon.svg?rev=3771325) # qTrad Por [Rafael Minuesa](https://profiles.wordpress.org/rafaelminuesa/) [Descargar](https://downloads.wordpress.org/plugin/qtrad.1.13.2.zip) * [Detalles](https://es.wordpress.org/plugins/qtrad/#description) * [Valoraciones](https://es.wordpress.org/plugins/qtrad/#reviews) * [Instalación](https://es.wordpress.org/plugins/qtrad/#installation) * [Desarrollo](https://es.wordpress.org/plugins/qtrad/#developers) [Soporte](https://wordpress.org/support/plugin/qtrad/) ## Descripción qTrad is an independent continuation of qTranslate and qTranslate-X. Existing translations keep working as they are, and you gain modern editing, accessible language controls and multilingual SEO. #### Why qTrad I liked the way qTranslate worked. Every translation of a post lives in that same post, so there are no duplicate posts to keep in sync, and switching languages in the editor is one click. When qTranslate and later qTranslate-X were closed, I wanted that approach to stay available, so qTrad carries it on and reads the same data. qTrad keeps all translations of a post title, content and excerpt together in the same field. It reads the qTranslate comment markers, the qTranslate-X bracket markers and the swirly markers. * HelloHallo * [:en]Hello[:de]Hallo[:] * {:en}Hello{:de}Hallo{:} The classic and block editors show one language at a time. Saving preserves the other translations, including those of disabled languages. Public custom post types with a REST endpoint are supported. Raw mode shows the complete multilingual field for direct editing. Language controls use full names, keyboard-operable buttons, announced selection changes, visible focus, generous targets and right-to-left editing. Public switchers offer links, flags with accessible names, short codes, or a labelled dropdown with an explicit Go button. Dropdowns fall back to ordinary links without JavaScript. The qtranslate_* language, locale, flag, URL, term and fallback settings are reused as they are. Existing qTranslate and qTranslate-X widgets keep their place in the sidebar. Imported custom languages remain available in Settings Languages, where you can edit their names and locales and add new two- or three-letter language codes. qTrad offers content compatibility and a documented subset of the qtrans_* and qtranxf_* public functions. It does not include every feature of its predecessors or their third-party integration modules. #### Read and write compatibility The «Keep» format preserves whichever marker style each field already uses, and new translated post fields use comment markers. Choose comments if a site may need to return to the original qTranslate, which cannot read qTranslate-X closing brackets or swirly markers. The site title and tagline always use brackets because WordPress strips comments from those settings, so returning those two to the original qTranslate needs a deliberate conversion. Activation never rewrites posts. #### Date and time formats Each language can have its own date and time format under «Language names and locales» in Settings Languages, in the syntax of Settings General. Where a theme or plugin shows a date in the site’s format, the public site and emails use the format of the visitor’s language, with month and day names from that language’s WordPress translation. Formats stored by qTranslate-X or qTranslate-XT are used as they are, including their strftime style. wp-admin keeps the site formats. #### What still needs translating The post lists have a «Missing in …» filter that shows the items without text in a language, and the dashboard has a Translations box with the number of missing items per content type and language, each linked to the filtered list. #### Custom fields, user profiles and options List custom fields under «Custom fields» on the Advanced tab of Settings Languages to show them in the visitor’s language and to merge edits into the language you are editing. A checkbox below that list also shows every other custom field and user profile field that holds language markers in the visitor’s language. Under « Options» you can do the same for options, such as theme and widget settings, either all of them or a list of names. «Text filters» takes filter hooks of your theme or other plugins whose text should be shown in the current language. These three work on the public site only: wp-admin, the REST API and WP-CLI keep reading what is stored. If code on the public site writes a value back after reading it translated, qTrad keeps the stored translations of everything that did not change. #### Advanced Custom Fields With ACF or ACF PRO active, the field types «Text (per language)», «Text area (per language)», «URL (per language)», «WYSIWYG editor (per language)», «Image (per language)»,« File (per language)» and «Post object (per language)» show one input per language. They are the qtranslate_* field types of qTranslate-XT’s ACF module, stored in the same way, so existing field groups keep working. A standard text, text area, URL or WYSIWYG field can do the same with its «Translate» setting, and a standard field whose value already carries language markers is edited per language as well. get_field() returns the visitor’s language; a missing translation falls back to the default language without a prefix. A required field needs the default language, and ACF’s own checks, such as a valid URL or a character limit, apply to each language. #### WooCommerce Product names, short descriptions, purchase notes, attribute names and values, payment gateway titles and descriptions, shipping rate labels and email texts with language markers are shown in the visitor’s language: on shop and product pages, in the cart and checkout (also the cart and checkout blocks), in mini-cart fragments and in structured data. Attribute values keep their stored form, so variations match in every language. Each order records the customer’s language in _user_language, the field qTranslate-XT used; its items are stored in that language, the thank-you page opens in it and customer emails are sent in it, including WooCommerce’s own texts when its translation is installed. Emails to the shop use the site’s default language. Product fields are edited with language buttons like any post. Email subjects, headings and texts, payment method titles and descriptions on WooCommerce settings screens that use the classic forms, purchase notes and attribute labels get one input per language. The integration filter qtrad_admin_field_rules adds other screens. Translations of disabled languages are kept until you replace a complete field in raw mode or through a full programmatic update. Ordinary wp_update_post() calls replace the fields they supply. Pass qtrad_language to request an update of one language only. REST saves in language-button mode merge plain values into the language given by qtrad_language or lang, otherwise into the request language. Complete marker strings replace complete fields. #### URLs The URL modes are the same as in qTranslate-X: 1. Query parameter 2. Language path 3. Subdomain 4. One domain per language Sites with plain permalinks or /index.php/ permalinks use query URLs, since those work without server rewriting. Subdomains and separate domains need the matching DNS, certificates and server configuration. An explicit language URL always wins. Cookies and browser negotiation apply only to the bare homepage, and other bare URLs serve the default language when its prefix is hidden. REST endpoints, assets, admin URLs, feeds and XML sitemaps never receive language prefixes. Each language can have its own slug for a post, page, custom post type entry, category, tag or other term. Edit them in the «Translated slugs» box of the editor and on the term screens; an empty field uses the WordPress slug. Post types and taxonomies can also have a translated base, such as «kategorie» instead of «category», on the URLs tab of Settings Languages. Links, the language switcher, canonical and hreflang tags and sitemaps use the translated address, and the WordPress address under another language redirects to it. The WordPress admin and the REST API keep working with the WordPress slug. Slugs and bases are stored the way qTranslate-XT stores them, so a site that used its Slugs module keeps its addresses, and slugs left by the older qTranslate Slug plugin are read as well. #### SEO Alternate language links and multilingual sitemap entries use canonical URLs and only list languages a post is actually translated into. Category, tag, author and post type archives list a language only when at least one of their posts is translated into it. Adapters for WordPress core, Yoast SEO and Rank Math cover metadata, social sharing and schema output. Pages missing a translation keep the configured visitor fallback and receive noindex. The SEO translations panel takes optional per-language titles and descriptions. Full-page caches should bypass the personalized bare homepage or vary it by the language cookie and Accept-Language. Browser negotiation can be turned off for a stable homepage. #### Switchers Use the Language switcher block (in block themes, for example in the header), the shortcode [qtrad_switcher style=»both»] or the qTrad Language Chooser widget. Styles are text, image, both, short and dropdown. Prefer text or both so visitors can identify languages without interpreting flags. The qtrans_* and qtranxf_* chooser functions used in older themes keep working. Language menu items created with qTranslate-X or qTranslate-XT (custom links to # qtransLangSw) keep working in classic navigation menus, with their type, title, flags, names, colon and current options. To add one, create a custom link with the URL #qtransLangSw for a «Language» item with all languages below it, or #qtransLangSw? type=AL for a direct link to the other language. Custom links that point into the site follow the visitor’s language; add setlang=no to a link’s query string to keep it as written. ### Privacy qTrad sends no data anywhere and loads nothing from other sites. It stores the language a visitor chose in the cookie qtrans_front_language, and the language an administrator edits in, in the cookie qtrans_admin_language, under the names qTranslate used, so a site that switches plugins keeps them. ### Credits qTrad continues the work of qTranslate by Qian Qin and qTranslate-X by the qTranslate Team, both licensed GPLv2 or later. It is an independent project and is not endorsed by the original authors. The bundled flag images are unchanged SVGs from flag-icons 7.3.2 by Panayiotis Lipiridis, licensed MIT. The full notice is in flags/license-flag-icons.txt and the source of each file is recorded in flags/manifest.json. ## Capturas [⌊The block editor shows one language at a time. Language buttons switch between translations, and saving keeps every other translation.⌉⌊The block editor shows one language at a time. Language buttons switch between translations, and saving keeps every other translation.⌉[ The block editor shows one language at a time. Language buttons switch between translations, and saving keeps every other translation. [⌊Settings → Languages, the Languages tab with the language list.⌉⌊Settings → Languages, the Languages tab with the language list.⌉[ Settings Languages, the Languages tab with the language list. [⌊The accessible language chooser on the front end, with full language names.⌉⌊The accessible language chooser on the front end, with full language names.⌉[ The accessible language chooser on the front end, with full language names. [⌊After a switch from qTranslate-XT, administrators see what qTrad found and which settings it turned on.⌉⌊After a switch from qTranslate-XT, administrators see what qTrad found and which settings it turned on.⌉[ After a switch from qTranslate-XT, administrators see what qTrad found and which settings it turned on. [⌊The URLs tab with the qTranslate URL modes and the translated URL bases.⌉⌊The URLs tab with the qTranslate URL modes and the translated URL bases.⌉[ The URLs tab with the qTranslate URL modes and the translated URL bases. [⌊Native name, locale, and date and time formats of each language.⌉⌊Native name, locale, and date and time formats of each language.⌉[ Native name, locale, and date and time formats of each language. [⌊The Advanced tab: custom fields, options and text filters.⌉⌊The Advanced tab: custom fields, options and text filters.⌉[ The Advanced tab: custom fields, options and text filters. ## Bloques Este plugin proporciona 1 bloque. * Language switcher Links to the current page in each enabled language. ## Instalación 1. Back up the site and try the switch on a staging copy first. 2. Deactivate qTranslate, qTranslate-X or qTranslate-XT. qTrad will not start while one of them is active. 3. Install and activate qTrad, then open Settings Languages. 4. Check representative content, editor saves, language URLs and any site-specific integrations. Your posts and qtranslate_* settings need no conversion. Uninstalling qTrad keeps translations and settings in place. ## FAQ ### Is this a drop-in replacement for every extension? No. qTrad covers stored content, the shared settings and the commonly used public functions of qTranslate and qTranslate-X. Other integration modules, menu-language management and third-party custom editor controls need to be checked on your site. ### What if JavaScript is unavailable? Public switchers remain plain links. In the classic editor the full marker strings stay visible and the language buttons stay disabled, so edit complete fields carefully. The WordPress block editor itself requires JavaScript. ### I am moving from qTranslate-XT. What should I check? Posts, pages, titles, excerpts, term names, the site title and tagline, widgets with markers, language menu items and the shared qtranslate_* settings work as they are, including two- and three-letter language codes. Translated slugs and translated URL bases keep their addresses and can be edited in qTrad. Custom fields, user profile fields and options with language markers are shown in the visitor’s language: on the first visit to wp-admin qTrad looks for such data, turns the matching settings on and lists what it found. ACF fields, including qTranslate-XT’s own field types, and WooCommerce shops keep working. Per-language date formats and the commonly used qtranxf_* functions, the QTX_Translator object and its translate_* filters work as well. qTrad does not include XT’s other integration modules (Gravity Forms, Events Made Easy and others) and lists those. No content is changed or deleted, so reactivating qTranslate-XT shows that data again. ### How do I include a literal marker in content? Language markers are reserved syntax. To show an example such as [:en] in a post, encode it with HTML entities, for example [:en]. ## Reseñas No hay valoraciones para este plugin. ## Colaboradores y desarrolladores «qTrad» es un software de código abierto. Las siguientes personas han colaborado con este plugin. Colaboradores * [ Rafael Minuesa ](https://profiles.wordpress.org/rafaelminuesa/) [Traduce «qTrad» a tu idioma.](https://translate.wordpress.org/projects/wp-plugins/qtrad) ### ¿Interesado en el desarrollo? [Revisa el código](https://plugins.trac.wordpress.org/browser/qtrad/) , echa un vistazo al [repositorio SVN](https://plugins.svn.wordpress.org/qtrad/) o suscríbete al [registro de desarrollo](https://plugins.trac.wordpress.org/log/qtrad/) por [RSS](https://plugins.trac.wordpress.org/log/qtrad/?limit=100&mode=stop_on_copy&format=rss). ## Registro de cambios #### 1.13.2 * First public release on WordPress.org. * The dashboard Translations box and the archive language checks read the «last changed» stamp of the posts and terms cache groups through a plugin helper. * The Advanced Custom Fields integration files are named acf-integration.php and acf-integration-fields.php. #### 1.13.1 * The license files are named license.txt and flags/license-flag-icons.txt. #### 1.13.0 * Settings Languages is split into four tabs (Languages, URLs, Content, Advanced). One Save button still saves everything, a validation error opens the tab that holds the field, and without JavaScript all sections stay visible. #### 1.12.7 * Custom fields listed under «Custom fields» are read as stored in wp-admin, AJAX, REST, cron and WP-CLI, like every other translated value; only the public site reads them in the visitor’s language. #### 1.12.6 * Options that hold credentials (API keys, secrets, tokens, passwords, the WordPress connector settings) are never translated, whatever the Options setting lists. #### 1.12.5 * Sites with /index.php/ permalinks get query URLs for languages, since path URLs there need server rewriting. * Core paths are computed once per request without recursion when a URL filter calls home_url(), use the local path of directories served from another host ( a CDN), and follow a REST prefix changed after the plugins load when links are built. * Settings Languages says when Path mode uses query URLs because of the permalink settings. #### 1.12.4 * The notice shown while another qTranslate plugin is active appears only on the dashboard and the plugins screen. * With WordPress in a subdirectory, the admin path and the login page typed at the home root stay language neutral. #### 1.12.3 * Admin, content, plugin, includes and REST paths are taken from WordPress (admin_url(), content_url(), plugins_url(), includes_url(), rest_get_url_prefix() under the home URL), so moved directories and WordPress in a subdirectory stay language neutral. #### 1.12.2 * Posted settings, editor fields and ACF values are sanitized where they are read; ACF values are joined only after ACF’s own nonce checks out. * The migration notice shows on the dashboard, the plugins screen and Settings Languages. * Readme: privacy section. #### 1.12.1 * The migration notice names the qTranslate plugin the site used. #### 1.12.0 * Translation overview: a «Missing in …» filter on the post lists and a Translations box on the dashboard. * WooCommerce email texts, payment method titles, purchase notes and attribute labels get one input per language. #### 1.11.0 * Language switcher block for block themes and any block area. #### 1.10.2 * Archives list an alternate language, and appear in that language’s sitemap entries, only when one of their posts is translated into it; otherwise they are noindex in that language. #### 1.10.1 * Password-protected posts no longer expose their text in SEO descriptions. * Advanced Custom Fields: saving keeps translations of languages that are not enabled, fields detected by their language markers are stored as text, and other validators are no longer overridden. * Options that are not autoloaded are translated as well. #### 1.10.0 * Date and time formats per language, including the ones stored by qTranslate-X and qTranslate-XT. * qTranslate-XT’s helper functions qtranxf_use_language, qtranxf_translate_deep, qtranxf_translate_post, qtranxf_get_url_for_language and others, its QTX_Translator object and the translate_text, translate_term and translate_url filters. #### 1.9.0 * WooCommerce: product, attribute, gateway, shipping and email texts in the visitor’s language, also in the cart and checkout blocks and the mini-cart. * WooCommerce orders keep the customer’s language: the thank-you page and customer emails use it. * Excerpts shown by block themes are translated. #### 1.8.0 * Advanced Custom Fields: qTranslate-XT’s qtranslate_* field types work, with one input per language, and standard text, text area, URL and WYSIWYG fields can be translated with a «Translate» setting. * get_field() returns the visitor’s language; validation runs per language. #### 1.7.0 * Custom fields and user profile fields that contain language markers can be shown in the visitor’s language without listing each one. * Options that contain language markers, such as theme and widget settings, can be translated on the public site, all of them or a list of names. * Text filters: filter hooks of a theme or another plugin whose text is shown in the current language. * Code on the public site that writes back a value it read translated keeps the other languages. * After a switch from qTranslate-X or qTranslate-XT, these settings are turned on where such data is found. #### 1.6.0 * Translated slugs can be edited: a «Translated slugs» box in the editor and fields on the term screens, one slug per language. * Post types and taxonomies can have a translated URL base per language, under Settings Languages. Bases stored by qTranslate-XT are used as they are. * Addresses from before a base was translated redirect to the new address. #### 1.5.0 * Translated slugs stored by qTranslate-XT or the qTranslate Slug plugin are served: posts, pages, custom post types and terms open under the slug of each language. * Links, the language switcher, canonical and hreflang tags and sitemaps use the translated slug, and the stored slug under another language redirects to it. * The migration notice reports translated URL bases, which are not used yet. #### 1.4.0 * Language menu items created with qTranslate-X or qTranslate-XT (custom links to #qtransLangSw) work in classic navigation menus. * Custom menu links that point into the site follow the visitor’s language. * The Plugins screen links to the settings page as «Settings». #### 1.3.0 * Prepared for WordPress.org: qtrad_ prefix for qTrad’s own names, two- and three- letter language codes, translated multi-page posts, the migration notice for sites coming from qTranslate-XT. ## Meta * Versión **1.13.2** * Última actualización **hace 2 días** * Instalaciones activas **Menos de 10** * Versión de WordPress ** 5.8 o superior ** * Probado hasta **7.1.4** * Versión de PHP ** 7.4 o superior ** * Idioma * [English (US)](https://wordpress.org/plugins/qtrad/) * Etiquetas: * [bilingual](https://es.wordpress.org/plugins/tags/bilingual/)[i18n](https://es.wordpress.org/plugins/tags/i18n/) [language](https://es.wordpress.org/plugins/tags/language/)[multilingual](https://es.wordpress.org/plugins/tags/multilingual/) [translation](https://es.wordpress.org/plugins/tags/translation/) * [Vista avanzada](https://es.wordpress.org/plugins/qtrad/advanced/) ## Valoraciones Aún no se han enviado valoraciones. [Tu valoración](https://wordpress.org/support/plugin/qtrad/reviews/#new-post) [Ver todas las reseñas](https://wordpress.org/support/plugin/qtrad/reviews/) ## Colaboradores * [ Rafael Minuesa ](https://profiles.wordpress.org/rafaelminuesa/) ## Soporte ¿Tienes algo que decir? ¿Necesitas ayuda? [Ver el foro de soporte](https://wordpress.org/support/plugin/qtrad/)