內容簡介
Drych 外掛可將英語 WordPress 網站連接至清晰的英語和威爾斯語工作流程，簡化多語言內容管理。用戶可輕鬆設置並管理翻譯，無需 API 金鑰或手動上傳，提升網站的多語言功能。
【主要功能】
• 連接英語與威爾斯語工作流程
• 自動化翻譯管理與發布
• 支援 Polylang 安裝與啟用
• 提供翻譯進度與內容管理
• 可選擇性隱藏語言切換按鈕
• 測試沙盒帳戶安全清除測試資料
外掛標籤
開發者團隊
📦 歷史版本下載
原文外掛簡介
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.
