TranslateSimple

Changelog

0.1.22

• Escape stored translations at every plain-text and HTML-attribute rendering boundary.
• Add regression coverage for malicious translations imported or written directly to the database.

0.1.21

• Detect the visitor language and localize the landing page in English, French, Spanish, Italian, Portuguese and German.
• Add a compact remembered language selector and serve localized accessibility metadata.
• Show each non-English visitor an example from their local language into English; keep English to Spanish for English visitors.

0.1.20

• Put support for 33 languages in the primary landing-page promise without adding another hero row.
• Refresh the portal asset version so the compact language badge renders correctly for returning visitors.

0.1.19

• Present automatic translation as a fully managed TranslateSimple service across the landing page, customer portal and WordPress onboarding.
• Remove infrastructure and credential jargon from the customer journey while retaining required external-service disclosures.
• Introduce the aligned-lines brand mark across the customer portal and WordPress workspace.

0.1.18

• Expand source and target selection from three to 33 common languages supported by the managed translation service.
• Keep the twelve most-used choices visible and place 21 additional languages in a compact expandable picker.
• Map canonical English, Portuguese and Chinese codes to service-specific and native WordPress locales.

0.1.17

• Cover fifteen representative WordPress site profiles with a browser crawler that scrolls every source and translated route.
• Resolve translated static fronts, posts indexes and archives without dropping the locale during canonical redirects.
• Keep the integrated selector available on translated home, blog, search and archive routes.
• Prevent stale Elementor source markup and render WooCommerce product descriptions and excerpts from the local translation catalogue.
• Install available official language packs for active plugins and themes when languages are saved.
• Reject leaked source text, formatting markers, encoded HTML, missing selectors, 404 pages and browser errors in the compatibility matrix.

0.1.16

• Keep the integrated language selector on translated home, category, author and date archive routes.
• Resolve localized author/date archives and preserve their corresponding URL when switching languages.
• Discover and translate classic navigation-widget headings used in theme footers.
• Exercise literal FR/ES home, category and author routes in the public browser smoke suite.

0.1.15

• Reload native WordPress interface strings in the selected public language and install missing official core language packs when languages are saved.
• Keep the integrated language selector available on translated home, blog and archive routes.
• Cover translated comment forms and localized home navigation in the public browser smoke suite.

0.1.14

• Normalize allow-listed encoded formatting on source-language and untranslated fallback routes.
• Hide revoked WordPress connections from the customer portal while preserving account history.
• Expand deterministic smoke and browser journeys across support, password devices, billing, exports, disconnect, deletion and outage paths.

0.1.13

• Translate document titles, media-library alt text, rendered image attributes and generated internal links.
• Translate legacy Custom HTML widget attributes and SureForms default field labels and submit buttons.
• Restore allow-listed Spectra encoded formatting as safe HTML without leaking encoded markup.
• Expand the integration fixtures and realistic showcase audit for these rendering paths.

0.1.12

• Replace separate Gutenberg allowlists with one extensible declarative registry.
• Auto-detect safe static content and display fields from registered block metadata.
• Support nested wildcard attribute paths and safe rendered HTML attributes.
• Report metadata-backed coverage while excluding raw code, URLs and secret-like settings.
• Expand the customer landing page with product workflow, ownership and honest coverage guidance.

0.1.11

• Make target languages react to the selected source language and simplify the language picker.
• Keep protected formatting markers invisible while editors change only the readable text.
• Report unexpected service redirects clearly instead of showing a generic invalid-response error.

0.1.10

• Translate current Spectra content/button blocks and SureForms field labels, placeholders, help text and custom buttons.
• Preserve encoded inline formatting in dynamic block attributes.
• Use the proxy-compatible site-pairing collection endpoint without following sensitive API redirects.

0.1.9

• Add a three-step WordPress onboarding checklist with one clear next action.
• Explain how existing paid customers connect and approve their site without an API key.
• Add WordPress.org directory screenshots for setup, block editing and the translated visitor experience.

0.1.8

• Add guided post-payment WordPress connection and verified-device password sign-in to the hosted portal.

0.1.7

• Unify customer-facing, publisher and service branding under TranslateSimple.

0.1.6

• Publish the service terms, privacy notice and support route referenced by the WordPress.org listing.

0.1.5

• Discover public custom post types and taxonomies, including WooCommerce products, categories, tags and attributes.
• Switch the native WordPress locale on translated routes so core and plugin language packs render system text.
• Translate supported Elementor, ACF, legacy/block widget, Contact Form 7, WPForms and Gravity Forms display fields.
• Preserve translated WooCommerce product names in cart, checkout and stored-language order items.
• Show detected content types, taxonomies and compatibility adapters in the scan report.

0.1.4

• Translate page-list and navigation-link labels from block themes.
• Keep internal menu, site-title and logo links inside the selected language.
• Scan navigation labels stored in block templates, template parts and patterns.
• Translate static text and image alternatives stored in active-theme templates and patterns.

0.1.3

• Integrate the automatic language selector into block-theme and classic navigation menus.
• Add lightweight CSS variables for theme-specific styling.

0.1.2

• Place the automatic language switcher above the site header without overlaying theme controls.
• Keep a footer fallback for themes that do not expose the standard body-open hook.

0.1.1

• Add Microsoft Azure Translator support to the hosted service.
• Clarify the machine-translation provider disclosure.

0.1.0

• Initial private-pilot release.