Drych

Сүрөттөө

Drych connects an English WordPress website to a clear English and Welsh workflow. Drych Ltd owns and licenses the Drych software. Clear Translations Ltd is the current Drych operator and provides the customer service. Install the plugin, create a free Drych account or sign in, and follow the guided setup. No API keys, WordPress passwords or manual ZIP uploads are needed.

If a multilingual provider is not active, Drych links to WordPress’s standard Polylang installation and activation screens. Those actions remain under the administrator’s direct control. Once Polylang is active, Drych can configure English and Welsh, prepare linked private Welsh counterparts, and monitor new English pages and posts. Existing WPML sites can use their current English/Welsh language structure. Setup never publishes a new Welsh page.

Guided setup selects one standard accessible language-switch preset without asking for styling or template decisions. It stays hidden until a matched Welsh page is public and follows the visitor’s current language. Later, Settings can change its placement, colours, shape, size and wording, or disable it when the theme already provides a switch.

English content is split into stable, markup-preserving translation segments. Welsh wording is staged privately and can follow a review workflow or, with separate website-owner consent, publish automatically only after the complete current page is ready. During guided setup the administrator explicitly chooses publication timing. Publishing English immediately is selected by default; an optional equal-release mode keeps a newly published English page private until its complete Welsh counterpart is ready, then releases both in one protected transaction. A changed English source keeps the last approved Welsh page live while its replacement is prepared privately.

Every protected write is conditional, idempotent, read back immediately and recorded for safe recovery. A failed prerequisite, stale page, payment problem or quality check leaves Welsh work private. English remains independent under the default publication choice; equal-release mode safely keeps only new English content private until its Welsh counterpart is ready. Administrators can emergency-pause or disconnect Drych at any time.

After pairing, Drych provides three canonical destinations in the WordPress admin menu: Translations, Settings and Help. During onboarding, Translations shows saved setup progress and one Continue setup action. Afterwards, Translations is the working area for managed content, translation progress, review and payment actions; website-wide controls remain in Settings. Inventory can be refreshed whenever pages, posts or navigation change. The administrator chooses either only selected content or all current and future supported content. Managed pages can be dragged into the order in which whole items use the translation-word allowance; translation is not capped by page count. Navigation and other supporting wording follow managed pages and use the same word allowance. New or changed English content also tells Drych to refresh immediately, with a scheduled catalogue check as fallback. After the initial cycle, Drych replaces repeated edits with the latest pending revision and sends the complete pending update batch automatically at 09:00 and 17:00 UK time. In selected-content mode, pages outside the selection remain visible but are not dispatched automatically. In all-content mode, newly added supported content joins the managed scope automatically. Testing-sandbox accounts can safely clear unused test work, inventory, scans, choices and local connection state to repeat the new-user journey without deleting existing WordPress content.

Translations contains the canonical searchable content list. It filters by the customer-facing translation states, shows matched English and Welsh state, translation scope and priority, current batch and next action, and keeps content refresh beside the inventory it updates. Page and batch histories use the same concise stages while preserving page-level exceptions and factual progress.

Home opens by default. Publishing English immediately is selected by default, with equal bilingual release available during setup. More than one eligible package can remain with Clear at once. Pages and Posts retain a compact English/Cymraeg pair view. The launch requires the administrator to review every selected waiting page before translation begins. Overview later keeps one complete update batch available for review: it applies the included-word balance to whole items in the saved priority order and, when needed, offers the current Drych billing authority one exact VAT-inclusive payment for the remaining translation words.

Search terms such as “Welsh bilingual site”, “Welsh website translation” and “Welshify your site” all describe the same guided Drych workflow. Supported multilingual providers are Polylang and WPML. Participating WordPress tables must use InnoDB for transactional safety.

External service

This plugin connects to the Drych service at https://drych.cymru. Drych Ltd (company number 17402546) owns and licenses the software. Clear Translations Ltd is the current Drych operator, provides the customer service and is responsible for professional translation and review. The service is required for Drych account matching, translation workflow, monitoring and controlled publication. An explicitly configured, visibly labelled sandbox installation may instead connect only to https://testing.drych.cymru for isolated test accounts, translations and Stripe test payments; production remains the default and arbitrary service addresses are not accepted.

No connection data is sent merely by installing or activating the plugin. When an administrator chooses to create an account or connect, the browser sends the site’s public URL and the exact Drych setup-step return URL to Drych. The focused account hand-off keeps the website and return route visible while the administrator signs in, registers, verifies their email, chooses the eligible organisation and matches or deliberately adds the website. After final approval, WordPress sends Drych the one-time pairing code, site URL, REST API URL, WordPress user ID, plugin version, safety-test result and a revocable site-scoped credential. Once connected, WordPress exchanges entitlement, managed-content, translation-batch, review, publication and recovery state with Drych. Drych calculates and locks exact selected wording and prices before a short-lived sign-in link opens Stripe checkout; card details are handled by Stripe and are not sent to WordPress. When managed English content is published or updated, the plugin also sends its numeric WordPress content ID, managed-catalogue revision, event type and event time so Drych can refresh that site’s authorised translation catalogue without waiting for the fallback refresh. On the explicitly allowlisted testing sandbox only, an administrator can explicitly reset unreturned test translation packages or the complete onboarding fixture. Once the bilingual workflow is enabled, authorised source wording, Welsh translation segments and the metadata required to stage, verify, publish, read back and safely roll back that wording are also exchanged with the service.

Service information and terms: https://drych.cymru/wordpress-service

Privacy notice: https://drych.cymru/privacy

Security and data

Every protected resource request requires the paired WordPress administrator and edit permission for its exact target. Every write also requires that target post type’s publish capability, a strong If-Match value and a unique Drych operation key. The plugin locks authoritative post and locale rows, verifies the exact result, stores an idempotent receipt in the same database transaction and fails closed on ambiguity.

Operation receipts contain hashes and the protected response required for safe replay. Pending receipts, which can represent an uncertain outcome, are retained until an administrator resolves them. Completed and rejected receipts are retained for 180 days and then removed in bounded daily batches. Deactivation pauses publication immediately and stops that maintenance schedule; it does not erase evidence.

Орнотуу

  1. In WordPress, open Plugins > Add New and search for “Drych”.
  2. Install and activate Drych.
  3. Follow Start bilingual setup, or choose Drych from the left admin menu.
  4. Create a free Drych account or sign in; the website address is filled in automatically.
  5. Verify your email if you are new, then return to WordPress and approve the secure connection.
  6. If needed, use WordPress’s standard buttons to install and activate Polylang, then run the guided English/Welsh setup. Choose whether English publishes immediately (the default) or new English and Welsh content are released together. Setup also previews and selects the standard accessible language switch; specialist controls remain in Settings.
  7. Review the first content inventory, confirm the pages, posts and supported custom content Drych should manage, and check the automatically included supporting site content. The inventory and scope confirmation do not send translation work or use translation words.
  8. After the initial batch, Drych automatically sends the complete eligible pending batch at 09:00 and 17:00 UK time. This does not change when English or Welsh content is published.

No WordPress password or Application Password needs to be created or copied. A reviewed ZIP remains available from Drych only as a fallback for private pilots or when the WordPress.org directory is unavailable.

FAQ.KG

Does connecting publish anything?

No. Connection runs a temporary private safety test and establishes the protected channel. Automatic publication remains off until it is separately authorised in WordPress Settings through a focused Drych account hand-off.

Do I need an existing Drych account?

No. If you install Drych from the WordPress plugin directory, the connection button can create a Drych Free account for this website. Existing customers can sign in instead.

Does my site need to be multilingual already?

No. Drych guides an administrator through WordPress’s own Polylang install and activation screens, then can configure English and Welsh and prepare linked Welsh drafts. Drych never changes another plugin’s activation state itself. If Polylang or WPML is already configured, Drych adopts the existing language structure safely.

Can Drych add the language switch?

Yes. Guided setup selects one standard accessible preset and previews it without exposing specialist controls. It remains hidden until a matched Welsh page is public. Its location, colours, shape, size and wording can be changed later in Settings, and it can be turned off if the theme already has a switch.

Can I place the language switch inside a page builder or theme template?

Yes. Add the [drych_language_switcher] shortcode in a shortcode block, widget or page-builder module. Theme developers can use <?php if (function_exists('drych_language_switcher')) { drych_language_switcher(); } ?>. Both use the colours, shape, size and wording configured in Drych and output nothing until both language versions are public. Turn off the automatic switch position when using a manual placement to avoid displaying it twice.

What happens if I edit English content while it is being translated?

Drych retires the superseded wording so it cannot be published, retains unchanged translation work and sends only the new or changed text through the replacement workflow. Any allowance reserved for the superseded section is reduced or released before the replacement is reserved, so an in-flight edit is not counted twice. An existing Welsh page stays live while the update is prepared privately.

Can I stop Drych immediately?

Yes. Drych in the left admin menu includes an emergency pause and a complete disconnect control. Pausing prevents new mutations while preserving protected reads needed to reconcile an already in-flight outcome. Disconnecting also revokes the site token.

What data is stored in WordPress?

The plugin stores a one-way publishing-token hash, a separate revocable site-scoped credential, the connected WordPress user ID, certification state and an operation ledger. Completed and rejected operation receipts are retained for 180 days; unresolved receipts are preserved for safe reconciliation.

Сын-пикирлер

There are no reviews for this plugin.

Contributors & Developers

“Drych” is open source software. The following people have contributed to this plugin.

Мүчөлөрү

Translate “Drych” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Өзгөртүүлөр

3.0.20

  • Remove and Restore update from the save response, avoiding an extra page load and repeated batch calculations.

3.0.19

  • Shows each page once in Ready for translation. Coverage notes appear as a small label only on pages that are partly covered or not yet verified.
  • Lists pages outside the current batch that have coverage notes once, in one collapsed section, instead of repeating them in every card.

3.0.18

  • Keep translation coverage details compact, beside content headings and closed until opened.

3.0.17

  • Recognise registered shortcodes without reporting CSS selectors or bracketed prose as integrations.

3.0.16

  • Include applicable shared header and footer text in translation work and show page coverage limitations before selection and payment.

3.0.15

  • Restore eligible shared headers and footers with the current Elementor header/footer integration.

3.0.14

  • Preserve Elementor page layouts and matching header/footer templates on managed translations.

3.0.13

  • Show the current allowance period and the date, time and word count of the next monthly allowance on the Translations dashboard.

3.0.12

  • Fix Remove, Restore and managed-page saving requests.
  • Display the total with its currency symbol on hosts without PHP Intl.

3.0.11

  • Focus page selection on pages and selected content, with other content available on demand.
  • Provide a direct billing setup and payment recovery path.
  • Clearly identify sandbox payments for designated test websites.

3.0.10

  • Preserves existing header and footer templates when preparing multilingual content.

3.0.9

  • Fixes an empty Managed pages tab before the first translation batch is sent.

3.0.8

  • Setup now has four steps and finishes when you save your publishing choice. Finishing setup sends and charges nothing.
  • The first translation batch is chosen and sent from the Translations overview, like every later batch, so you can remove pages before sending or paying for extra words.
  • After installing Polylang from setup, one button activates it and returns to Drych; the separate Polylang language wizard is skipped because Drych configures English and Welsh.

3.0.7

  • Automatically restarts expired website connections with the website details preserved.

3.0.6

  • Fixes website connection certification on MySQL while preserving atomic updates and rollback checks.
  • Fixes preparation of navigation menu items with CSS classes.

3.0.5

  • Shows the exact pages, words, publishing choices and any one-off total before the first translation batch is sent or paid for.
  • Explains each publishing option during setup and asks for standing authority only when automatic Welsh publication is chosen.
  • Sends setup reminders back to the current setup step, links Help to Translations and Settings, and keeps one connection route.
  • Names pages in reorder controls, keeps keyboard focus on them and announces the new position.
  • Translates the Drych menu and remaining fallback labels, formats amounts in the configured currency and shows how remaining words are made up.

3.0.4

  • Separates all wording that still needs translation from the exact content ready for the next batch.
  • Shows affected pages and lets an authorised administrator retry an earlier cancellation that has not completed.

3.0.3

  • Restores an initially private Welsh draft safely if a later page blocks an automatic multi-page release.
  • Uses the latest protected WordPress version token for rollback when only unrelated metadata changed, while still refusing any changed managed content.

3.0.2

  • Shows the current Welsh translation state and any changed English source directly beside every managed page’s allowance priority.
  • Safely moves untouched approval previews into automatic publishing when the site owner switches publication mode, without offering an obsolete manual approval action.

3.0.1

  • Removes translation page caps so each package is governed by its word allowance; page counts now describe website-check coverage only.
  • Adds selected-content and all-content scope modes, including automatic enrolment of newly added supported content.
  • Adds drag-and-drop managed-page priority for deciding which whole items use the available word allowance first.

3.0.0

  • Prices one complete post-activation update batch at a time, applies included words to whole items first and lets the current WordPress administrator and Drych billing authority open one firm VAT-inclusive checkout.
  • Lets the current WordPress administrator and Drych billing authority withdraw unclaimed paid translation work, track the original-route refund and resubmit eligible content after the provider accepts it, while retaining separately purchased managed-page entitlements.
  • Replaces withdrawal after Clear Translations claims a batch with a recorded, status-visible change request that does not promise cancellation or a refund.

  • Lets each authorised WordPress administrator or editor use their own WordPress identity and existing capabilities.

  • Assigns translation-review, technical and billing contacts explicitly instead of emailing every administrator.
  • Adds verified production moves, provider-migration revalidation and managed-page choices after plan downgrades.
  • Keeps published content, drafts, language relationships and account records through pause, disconnect, deactivation and uninstall.
  • Keeps content deletion separate from every lifecycle control.

2.9.0

  • Shows provenance-aware quality and publication exceptions in WordPress.
  • Routes unchanged supplied Welsh wording to Clear Translations with no customer action.
  • Offers one deliberate recovery choice for WordPress wording changes and failed public verification.

2.8.0

  • Added matched English/Welsh review, auditable approval and page-level correction rounds in WordPress.

2.7.0

  • Consolidates the latest revisions of all managed content into one complete pending update batch.
  • Adds a stated once-daily default, manual dispatch and an explicit Send now action.
  • Keeps unmanaged new pages visible without selecting, purchasing or dispatching them automatically.
  • Waits without partial dispatch when the complete batch needs more entitlement or payment authority.

2.6.0

  • Adds the canonical searchable Translations content list with English/Welsh state, managed-page use, refresh recovery and factual page and batch history.
  • Selects and previews one safe language-switch preset during setup, keeps it hidden until matched Welsh content is public and leaves specialist customization in Settings.
  • Separates English release timing from Welsh review or automatic publication.
  • Shows the consequence of every publishing combination and records website-specific versioned standing authority.
  • Supports an audited urgent-English override without changing the website-wide matched-release setting.

2.5.5

  • Opens a focused Drych account hand-off that keeps the website, Connect Drych task and manual WordPress return visible through sign-in, registration and verification.
  • Lets an authorised account match or deliberately add the current website to its eligible organisation before issuing the one-time connection.
  • Returns to the exact Connect Drych setup step and explains organisation or domain mismatches without exposing another organisation’s details.

2.5.4

  • Checks administrator capability, the canonical HTTPS website address and live same-origin REST availability before guided Polylang setup, with a recovery action for each problem.
  • Returns automatically to Prepare WordPress after WordPress activates Polylang so interrupted setup can resume safely.
  • Shows exactly which selected items use included words and names every item requiring an optional one-off payment.
  • Returns deleted or trashed Welsh counterparts to the translation queue during a fresh inventory scan.

2.5.3

  • Makes managed-page selection the main onboarding action, separates automatic navigation, and keeps completed content out of translation activity.

2.5.2

  • Recover cleanly when a completed one-time connection request is submitted again.

2.5.1

  • Adds automatic update discovery from drych.cymru for installations outside the WordPress.org directory.
  • Verifies the downloaded release against Drych’s published SHA-256 checksum before WordPress can install it.

2.5.0

  • Keeps inventory refresh, publication timing and managed-page selection inside the guided WordPress journey.
  • Adds repeatable page, post and navigation inventory refresh.
  • Enforces each tier’s managed-page cap independently of its monthly word allowance.
  • Lets administrators choose which pages are included and change the selection later.
  • Adds a sandbox-only complete onboarding reset while preserving WordPress content.

2.4.0

  • Adds a guided first inventory and missing-Welsh check without consuming translation words.
  • Recommends explainable visitor tasks such as Home and Contact, lets the administrator confirm every managed item explicitly, and keeps supporting site content separate from the managed-page limit.
  • Makes immediate English publication the preselected default while offering an explicit setup choice to release new English and Welsh content together.

2.3.3

  • Simplifies WordPress Translations to words available, words waiting and clear one-off or monthly payment choices.
  • Keeps unused starter words available in later allowance periods while monthly words reset.
  • Makes a paid package’s monthly words available as soon as Stripe confirms it, alongside any unused starter words.

2.3.2

  • Lets administrators select WordPress pages that cannot fit the remaining allowance, see an exact one-off price and pay securely without requiring an audit.
  • Reserves the selected page revisions against duplicate sending and dispatches them immediately when Stripe confirms payment, bypassing the grouped-send cron.
  • Keeps unfinished payment controls visible so the customer can continue or cancel and release the unchanged pages.
  • Requires paired-administrator, exact-resource edit and post-type publish capabilities before the protected WordPress write route can change or publish managed Welsh content.

2.3.1

  • Shows the current Drych translation status from the page and post editor, including a direct link to WordPress Translations.
  • Renders the grouped-send countdown immediately on the server before the live seconds begin updating.

2.3.0

  • Notifies Drych when managed English content changes so the WordPress queue refreshes promptly, with the scheduled catalogue check retained as a fallback.
  • Groups eligible waiting pages into fixed 15-minute translation dispatch windows instead of sending one package for each page save.
  • Shows a live minute-and-second countdown to the next grouped translation dispatch.

2.2.1

  • Allows only WordPress’s exact first-publication metadata and Polylang term-translation side effects while retaining atomic rollback for every unexpected change.
  • Uses the latest protected WordPress version token when visible managed wording and publication state are unchanged.

2.2.0

  • Adds managed Welsh translation for classic menu items and Navigation blocks while preserving links, order and structure; linked pages publish before navigation and unavailable Welsh destinations keep navigation private.
  • Sends a genuinely empty Welsh target for first translations and keeps existing Welsh only for correction work.
  • Gives navigation and other managed WordPress content clear type and status labels in WordPress Translations.
  • Prevents a WordPress segment claimed by a manual correction package from also entering an automatic package.

2.1.15

  • Adds the translator guidance required for every interface string containing numbered or count placeholders.

2.1.14

  • Shows the one-off starter allowance separately from the plan’s monthly allowance.
  • Reflects the revised self-service packages, including Active’s automatic weekly website check.

2.1.13

  • Makes clear that a public-site audit is separate from automatic translation of new WordPress content and that the customer chooses which audit findings to send.

2.1.12

  • Simplifies monthly allowances to correction words only. Pages found within the audit scope can be sent whenever the complete page fits the remaining word allowance.

2.1.11

  • Explains the exact setup or connection issue instead of showing a generic warning.
  • Puts a required safety-check action in plain sight, including when an earlier certificate has become stale.

2.1.10

  • Adds an allowlisted sandbox-only reset for unreturned WordPress test translation packages.
  • Restores reserved words and page allowances, returns affected pages to waiting and pauses automatic translation after a reset.
  • Protects returned, exported, billed, Scheduler-linked and publication-linked packages from deletion.

2.1.9

  • Opens healthy connected sites in WordPress Translations, with language-button controls moved to Settings and setup or connection checks in a separate attention-aware tab.
  • Allows additional eligible WordPress translation packages to be sent while earlier packages are still with Clear.

2.1.8

  • Shows translation-word and WordPress-page allowances as separate balances, including used and reserved amounts.
  • Counts a complete WordPress page as one page allowance instead of counting each technical text section separately.
  • Explains whether pages are waiting for words, page allowance or the current translation package to return.

2.1.7

  • Keeps the protected safety certificate identical between real WordPress cron and HTTPS web requests by fingerprinting the configured canonical site URL.

2.1.6

  • Shows linked English and Cymraeg page or post titles side by side in the WordPress content list.
  • Links each language card directly to its editor, highlights the page represented by the current row and recognises existing Polylang or WPML pairs as well as Drych-managed content.

2.1.5

  • Shrinks and vertically centres the Drych icon in the WordPress admin menu with balanced internal padding.

2.1.4

  • Adds a fail-closed, visibly labelled testing mode for the protected Drych WordPress sandbox.
  • Keeps production as the default and accepts only the named production or testing Drych service.
  • Invalidates connection and safety certification when a WordPress installation changes service environment.

2.1.3

  • Presents one page-level WordPress translation queue instead of repeated text-segment issues.
  • Explains automatic translation, WordPress detection and live-site verification as one clear workflow.
  • Shows draft correction requests separately and previews the allowance remaining after they are sent.
  • Keeps later scan concerns about Drych-managed wording with the original job for complimentary review, without charging the words twice.
  • Adds Drych to the main WordPress admin menu with the Drych icon and shows Welsh translation status in Pages and Posts.
  • Adds [drych_language_switcher] and a safe PHP template helper for manually placed language buttons.
  • Protects mid-translation edits by retaining unchanged work and replacing—not double-counting—superseded wording.

2.1.2

  • Replaced WordPress authentication-salt credential derivation with independent random site credentials.
  • Moved admin and language-switch assets to WordPress’s enqueue APIs.
  • Restricted the managed content catalog to WordPress administrators.

2.1.1

  • Restores the previous local connection and pause state when Drych cannot confirm a reconnect.

2.1.0

  • Added the original WordPress-native translation screen for allowances and correction work; the confirmed 3.0 journey later replaced its obsolete audit and correction branches.
  • Added separate site-scoped authentication and short-lived one-use links for Drych account actions and checkout.
  • Added direct self-service plan selection for Free customers.
  • Removed the enforced colour-contrast threshold from language-switch settings.

2.0.0

  • Added direct Drych Free registration and passwordless site pairing from WordPress.
  • Added guided English/Welsh setup using WordPress-controlled Polylang installation or existing Polylang/WPML adoption.
  • Added linked private Welsh counterparts, stable translation segments and safe source-change shadow drafts.
  • Added review-first and consent-gated hands-off Welsh staging and publication support.
  • Added an automatic accessible language switch with configurable location, colours, shape, size and wording.
  • Added protected content cataloguing, exact read-back, rollback and recovery support.

1.1.0

  • Added WordPress-native, passwordless Drych pairing.
  • Added a site-scoped bearer credential limited to protected Drych routes.
  • Runs certification during connection and safely re-certifies after relevant environment changes.
  • Added one-click emergency pause, disconnect and token rotation controls.
  • Added WordPress.org service and privacy disclosures.

1.0.0

  • Initial certified WordPress page/post publication adapter.