Gatey 2.1.10 – Authenticator remount fix

This release fixes Authenticator-specific mounting behavior.

What changed

• Adjusted Authenticator mounting so Authenticator screens can fully remount when needed.
• Corrected issues introduced by the previous mount hardening changes in cases where full screen remounting is part of the expected behavior.
• Improved reliability of Authenticator screen transitions and re-rendering.

Why it matters

Unlike simpler frontend components, Authenticator screens require full remounting in certain flows. The earlier mount-hardening changes were too strict for this behavior. This update restores the required remount logic while keeping the overall initialization more robust.

Impact

• No configuration changes required
• Recommended for all Gatey users
• Important fix for Authenticator screen behavior

Gatey 2.1.9 – Safer frontend mounting and shared race-condition hardening

This release improves frontend initialization reliability.

What changed

• Improved frontend mounting so components cannot mount multiple times in parallel on the same element.
• Unified the shared race-condition protection into a common helper.
• Reduced the chance of duplicate frontend initialization in edge cases.

Why it matters

In some cases, frontend race conditions could allow duplicate parallel mounts on the same target element. This update makes initialization more deterministic and improves overall frontend stability.

Impact

• No configuration changes required
• Improves frontend stability
• Reduces duplicate initialization issues

Gatey 2.1.8 – Improved Elementor integration

This release improves Elementor integration.

What changed

• Improved Elementor widget parameter handling.
• Refined widget behavior in Elementor-based layouts.

Why it matters

This update makes Gatey widgets more reliable when configured and rendered through Elementor.

Impact

• No configuration changes required
• Recommended for sites using Elementor
• Improves consistency of widget behavior

Gatey 2.1.7 – Fixed admin-side initialization issue

This release fixes an admin-side initialization issue affecting logger availability.

What changed

• Stabilized loading of admin/logger.php.
• Stabilized initialization timing of the Logger class.
• Prevented cases where PHP-based admin pages could fail because the logger was not yet available when needed.

Why it matters

In some cases, the logger initialized later than expected during admin page loading. If an affected admin PHP page relied on the logger too early, the page could break. This update makes logger availability deterministic during admin bootstrap.

Impact

• No configuration changes required
• Recommended update for all users
• Improves reliability of admin page loading

Gatey 2.1.6 – Compatibility and startup reliability

This release focuses on compatibility and startup reliability.

What changed

• Switched Elementor widget loading to namespace-based registration under SmartCloud\WPSuite\Gatey.
• Improved shared hub loading across WP Suite plugins.
• Hardened race-condition handling during plugin bootstrap.

Why it matters

When multiple WP Suite plugins load together, more predictable hub initialization helps avoid startup timing issues. The Elementor widget loading update also aligns the plugin more cleanly with namespaced registration patterns.

Impact

• No configuration changes required
• Recommended for sites running multiple WP Suite plugins
• Improves startup consistency in shared environments

Gatey 2.1.4-2.1.5

• Improved the robustness of script loading and dependency ordering for shared functions, blocks, and related frontend assets.
• Scripts are now loaded with defer wherever possible, reducing render-blocking behavior during page load.
• Fixed a logout race condition in the Authenticator block.
• Prevented premature redirect to the redirectSignIn page before logout had fully completed.
• Gatey now waits for the full sign-out flow to finish properly, including the Cognito revokeToken call, helping prevent users from remaining signed in unintentionally.

Gatey 2.1.3 – Admin-configurable sign-up visibility and passwordless settings

This release adds new admin-side controls for configuring the sign-in experience.

What changed

• Added a Hide Sign Up setting in the admin UI.
• Added Passwordless Settings to the admin UI.
• Passwordless configuration now includes:
  • hidden authentication methods
  • preferred authentication method
  • passkey registration prompt settings

Why it matters

These settings make it easier to tailor the authentication experience directly from the plugin admin interface, without needing code changes for common sign-in flow adjustments.

Impact

• No migration steps required
• No backend template update implied by this change
• Useful for sites using passwordless or passkey-oriented authentication flows

Gatey 2.1.2 – Bootstrap race condition fix for shared WP Suite hub

This release focuses on bootstrap reliability in multi-plugin WP Suite environments.

What changed

• Improved the shared hub loader and plugin initialization order.
• Hardened global WpSuite namespace initialization.
• Prevented Gatey from starting before the common inter-plugin hub is ready.

Why it matters

When multiple WP Suite plugins were loaded together, startup timing could occasionally create race conditions. This update makes Gatey’s initialization more deterministic and improves interoperability with other WP Suite plugins.

Impact

• No configuration changes required
• No frontend behavior changes expected
• Recommended update for sites using more than one WP Suite plugin

Gatey 2.1.1

Changed

• Updated the shortcode column rendering/behavior.

Gatey 2.1.0

• Moved reCAPTCHA handling and script loading to the shared hub-for-wpsuiteio package.
• Added admin-configurable debug logging for monitoring plugin PHP execution when needed. Requires both WP_DEBUG and WP_DEBUG_LOG to be enabled.
• Fixed a redirection issue.
• Simplified attribute handling across all block rendering flows.
• Renamed the Redux store from wpsuite/gatey to smartcloud/gatey to better align with the naming convention used across other plugins.