Skip to content

1.7.0 — Translation-ready + smarter URL rewriting

Latest

Choose a tag to compare

@gunjanjaswal gunjanjaswal released this 28 Jul 03:23
· 3 commits to main since this release

Two things in this release: the plugin is now translation-ready, and the URL rewriter catches more of your in-post links.

Translation-ready

The admin UI, the Setup Guide, and the contextual Help tabs are wrapped in WordPress i18n functions against the staticforge-for-cloudflare-pages text domain, with a languages/staticforge-for-cloudflare-pages.pot template (314 strings) shipped in the plugin. Translations can be contributed at translate.wordpress.org. Activity-log messages stay in English on purpose so they still match the troubleshooting reference. Nothing changes for English installs.

More in-post links get rewritten

The rewriter used to match only your site's exact home URL, so a link an editor had pasted as http:// when the site is https://, or with a stray www. (or missing one), or as a protocol-relative //your-site/..., kept pointing at the WordPress origin instead of the Public Site URL. Those near-miss spellings of your own host are now folded onto the canonical form before the rewrite, so they get swapped along with everything else.

  • Only your origin's own host and its www/non-www counterpart are touched — third-party links are left alone.
  • /wp-content/ assets still follow the bundle / keep-on-origin rules as before.
  • New SFORGE_Renderer::normalize_origin_aliases().

Run one Full Rebuild + Deploy after updating so every page picks up the change.

Also on wordpress.org: https://wordpress.org/plugins/staticforge-for-cloudflare-pages/