qTrad 1.13.1

The license files are now plain text files: the GPL text is license.txt and the flag-icons MIT notice is flags/license-flag-icons.txt. No code change from 1.13.0.

sha256 of qtrad-1.13.1.zip: 05e1be4489d255f476467447d7d34c7cba9d9e3057afce635dc3bbf8130ab7f8

v1.13.0

The build resubmitted to wordpress.org after the first review round, as the first public release.

• 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, the chosen tab survives a save and a reload, arrow keys move between tabs, and without JavaScript every section stays visible.
• 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.7).
• Options that hold credentials (API keys, secrets, tokens, passwords, the WordPress connector settings) are never translated, whatever the Options setting lists (1.12.6).

All 12 compatibility cells passed: https://github.com/ProWoos-Devs/qtrad/actions/runs/39165652683

sha256 of qtrad-1.13.0.zip: bec6073416db4d3e7514f1d4f59460a1a697357abb5f068d5056a8e83985e61d

Superseded by 1.13.1 before approval.

v1.12.7

Superseded by v1.13.0 before the upload to wordpress.org, which adds the tabbed settings page.

• 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.
• Options that hold credentials (API keys, secrets, tokens, passwords, the WordPress connector settings) are never translated, whatever the Options setting lists (1.12.6).

All 12 compatibility cells passed: https://github.com/ProWoos-Devs/qtrad/actions/runs/39160679806

sha256 of qtrad-1.12.7.zip: e0792811f51801e7a83e484b9ffbf2cf1141466fd536caa0fdd3cdc29226d9e6

v1.12.6

Superseded by v1.12.7 before the upload to wordpress.org: custom fields listed under "Custom fields" were still read in the current language in REST and WP-CLI.

• Options that hold credentials (API keys, secrets, tokens, passwords, the WordPress connector settings) are never translated, whatever the Options setting lists.

All 12 compatibility cells passed: https://github.com/ProWoos-Devs/qtrad/actions/runs/39146509505

sha256 of qtrad-1.12.6.zip: 6183330357f49c2e66be9e683cbbaca3235859431d0d27828d056997ba7a87be

v1.12.5

The build submitted to wordpress.org as the first public release. The plugin is now named just qTrad.

• 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.
• The notice shown while another qTranslate plugin is active appears only on the dashboard and the plugins screen (1.12.4).
• With WordPress in a subdirectory, the admin path and the login page typed at the home root stay language neutral (1.12.4).

All 12 compatibility cells passed: https://github.com/ProWoos-Devs/qtrad/actions/runs/38689115833

sha256 of qtrad-1.12.5.zip: dea48732a09759888c6f091b56bd6aebfad9051dcb60232ba894cdca1fbfe0d7

v1.12.3

Superseded before submission; 1.12.5 is the build submitted to wordpress.org.

• 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.

All 12 compatibility cells passed: https://github.com/ProWoos-Devs/qtrad/actions/runs/38685073686

sha256 of qtrad-1.12.3.zip: 3c7b8d85f95d36a906d0b787920ce1cfc14de65395de0de44e107455d17d0430

v1.12.2

Superseded before submission; 1.12.5 is the build submitted to wordpress.org.

• 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.
• WooCommerce emails detect a send through WooCommerce's locale filters instead of a backtrace.
• The migration notice shows on the dashboard, the plugins screen and Settings → Languages.
• Readme: privacy section.

All 12 compatibility cells passed: https://github.com/ProWoos-Devs/qtrad/actions/runs/37920865569

sha256 of qtrad-1.12.2.zip: 6c074432bc3cbd6d59122c17846b492af704a0a59797cd76c68ed0c163ef889a