Skip to content

Releases: code4recovery/oiaa-direct

v1.3.1

29 Apr 16:28
538442f

Choose a tag to compare

#99 template redirect + creatBrowserRouter support
#100 major i18n support
#102 minor additional support
#97 JointsWP docker-compose.yml

What's Changed

  • fix: Localize search placeholder and pass primary WPML language to SPA by @SIA-WEBSUP in #102
  • Add local WordPress dev setup with JointsWP theme by @sblack4 in #97

Full Changelog: v1.3.0-beta-rc-4...v1.3.1

Add i18n support

17 Apr 11:21
ce7a4de

Choose a tag to compare

see PR#100

Beta-RC-4

12 Apr 01:06
735d9ed

Choose a tag to compare

Release Description (v1.2.0-beta.0)

This release is a major WordPress integration upgrade focused on clean routing, better theme compatibility, and simpler setup.

Highlights

  • Migrates plugin rendering from shortcode-based embedding to template_redirect rendering.
  • Adds configurable Base Path routing (for example, /meetings) with browser-router support.
  • Enables direct deep-link navigation to sub-routes (like group detail pages) with WordPress rewrite rules.
  • Introduces automatic page lifecycle handling:
    • Creates the meetings page on activation if missing.
    • Removes only plugin-created pages on deactivation (safe ownership checks).
  • Adds block-theme-aware header/footer rendering with fallback behavior for broader theme compatibility.
  • Supports homepage mode when Base Path is /.
  • Keeps flexible asset loading:
    • jsDelivr CDN (versioned tags)
    • Local plugin assets fallback
  • Updates docs and plugin settings UX to match the new routing-first model.
  • Removes legacy shortcode flow.

Why this matters

  • Cleaner URLs and better SEO/shareability.
  • No dependence on placing shortcodes in page content.
  • More predictable routing and admin control.
  • Improved compatibility with modern WordPress themes and multilingual page path scenarios.

Notes

  • This is a beta release (1.2.0-beta.0).
  • If Base Path changes, permalinks should be re-saved in WordPress.
  • Built frontend assets are included for CDN delivery from the tagged release.

If you want, I can also draft a GitHub Releases version with “What’s Changed” and “Upgrade Steps” sections in your preferred tone (technical vs admin-friendly).

Beta-RC-3

24 Mar 16:39
ff73775

Choose a tag to compare

Release created via Github UI, creating new tag.

Beta-RC-1

22 Mar 19:17
c4dae58

Choose a tag to compare

First Release of beta plugin using new JSDeliver workflow