Changelog

2.0.9

• Fixed jQuery compatibility

2.0.8

• Fixed JavaScript error for the console page and login/register page

2.0.7

• Using local jQuery for consistency to avoid versioning errors.

2.0.6

• Fixed an issue with compatibility plugin

2.0.4

• Fixed an issue with compatibility plugin

2.0.3

• Minor fix on compatibility issue

2.0.2

• Minor fix on compatibility issue

2.0.1

• Minor fix on compatibility issue

2.0.0

• Complete plugin redesign to fully manage the login and register flow for WordPress users
• Plugin activation is now done without external pages.
• Customise your site’s login page with colors and images
• Customise the in-app notification your users will receive
• Choose between the default WordPress login page and the UNLOQ login page
• Choose between Password Only, UNLOQ Only or Password & UNLOQ as second factor for your site’s authentication mechanisms
• Backward-compatibility for previous versions of the plugin supported
• Manage your site’s users directly from the plugin and invite your users to enable two-step authentication

1.5.19

• Fixed incorrect login URL redirects when used with plugins that perform i18n, and password reset/welcome email URL sending.

1.5.18

• On successful login, the global $user variable is updated with the user that just logged in, so that other plugins that depend on the global $user variable can read the latest user data.
  Specific issues were tested with “redirect-after-login” plugin.

1.5.17

• Custom login path is completely disabled while iTheme Security plugin is active. This is to avoid login issues and incompatibilities between plugins.

1.5.15

• Custom login path is now compatible with the iTheme Security plugin

1.5.14

• Fixed issues with PHP < 5.3 for class constants accessing

1.5.12

• Fixed an issue where all-in-one-wp-security-and-firewall plugin interferes with the login flow.

1.5.11

• Updated the authentication flow to prevent redirect loop

1.5.10

• The login.js file now handles the UNLOQ-only login method’s token redirect without relying on the widget URL.

1.5.9

• The login.js file now automatically handles the token redirect without relying on the widget URL.

1.5.8

• Login JS script is now correctly enqueue and check for correct jQuery version to avoid theme conflicts

1.5.7

• Fixed static declaration to use array() constructor

1.5.6

• Fixed $_GET non-isset() checked variable

1.5.5

• util->getQuery() now works with $_GET in stead of $_SERVER

1.5.4

• Fixed $_POST variable checking to supress warnings
• Fixed register_hooks() function to be static

1.5.3

• Added the “Expos wp-admin/” functionality. If set to false, un-authenticated users that land on wp-admin/ will get a 404 in stead of the redirect to the login page. By default, this feature is disabled.

1.5.2

• Token parsing now takes place right after the “init” hook, and now looks directly into the server’s querystring for the unloq_uauth key. Previously this was done using the “parse_request” hook, but quite a few plugins abuse of that hook and were stopping the UNLOQ authentication
• Updated the error message for expired tokens to include a bit more information

1.5.1

• Fixed UNLOQ-only enforcement on site administrators. It now applies only when the UNLOQ-only setting is active
• Fixed wp-admin/ 404 messages for single-site installations, for users that are not authenticated and apply the default functionality

1.5.0

• Fixed WooCommerce issues & other SSO plugins
• Added custom login path
• Added custom login logo and login page colors

1.1.3

• Updated plugin description, screenshots, FAQs

1.1.2

• Updated the setup steps text
• Do not restrict UNLOQ init only on wp-login.php and wp-register.php in order to load on all sites.