Skip to main content

Changelog

1.4.0 (2026-10-05)

Features

  • Hyvä support now ships with the extension — The companion package mirasvit/module-social-login-hyva is gone: the sign-in buttons on the login and registration pages and the Social Accounts block in the customer account are part of Social Login itself, and one template now serves Luma and Hyvä alike. There is no second package to find and keep in step, and on a Luma store the Hyvä part simply stays dormant. Composer removes the companion package by itself when you upgrade. On Hyvä, the "Or sign in with" caption still shows above the social buttons, as it did with the companion package.

Improvements

  • ⚠️ On Hyvä, rebuild the theme styles after upgrading — The Hyvä look of the buttons now comes from this module's own Tailwind source, so run these once after setup:upgrade, then deploy static content as usual:

    bin/magento hyva:config:generate
    cd vendor/hyva-themes/magento2-default-theme/web/tailwind && npm run build

    For a custom Hyvä theme, run npm run build in that theme's web/tailwind directory instead. Until then the buttons work, but unstyled.

  • ⚠️ Hyva_MirasvitSocialLogin is gone, not renamed — You only need to act if you referenced it yourself: in a custom di.xml, a layout file, or a deployment script that enables modules by name.

  • ⚠️ If you overrode a template, repoint it — Hyva_MirasvitSocialLogin::login.phtml and Hyva_MirasvitSocialLogin::account/accountList.phtml are now Mirasvit_SocialLogin::login.phtml and Mirasvit_SocialLogin::account/accountList.phtml on both themes. An override at the old path is simply not read, with no error to say so. On Luma, the Mirasvit_SocialLogin/js/login script is replaced by Mirasvit_SocialLogin::js.phtml; a mixin on it is no longer loaded.

Fixed

  • Unlinking a social account is now protected against forged requests — The Unlink link in the customer account's Social Accounts block was a plain URL, so a hidden image or link on any page a signed-in customer visited could silently remove their Google or Facebook sign-in. Unlinking now only works through the button in the customer account, with the store's form-key check, on Luma and Hyvä alike. The button looks exactly like the old link.
  • Social Login configuration page no longer breaks on an unexpected field — If a provider's callback URI field had an unexpected ID or pointed to a provider that does not exist, the whole Stores → Configuration page failed to load. Now only that one row is left empty, and a warning naming the field is written to the log so you can find the cause.
  • Error on social accounts with no saved profile — A linked social account with no stored profile information caused an "Unable to unserialize value" error. Such accounts now load normally. If the stored profile is corrupted, the error now names the account so you can find and fix it.

1.3.1 (2026-09-14)

Improvements

  • Deleting a customer now also clears their linked social-login connections, so a shopper can sign in again with the same Google or Facebook account without being blocked.

1.3.0 (2026-07-07)

Features

  • Headless / GraphQL social login — Customers can now sign in with Google, Facebook, and your other configured providers from a PWA or headless storefront. A new mstSocialLoginProviders GraphQL query returns the enabled providers and their sign-in URLs, and the mstSocialLogin mutation exchanges the one-time login code for a customer token. Accounts are created and linked exactly as they are in the standard storefront login.
  • Headless login settings — New Stores → Configuration → Mirasvit → Social Login → GraphQL section with a Headless callback URL field (the only URL the login is allowed to redirect to, so there is no open-redirect risk) and a Nonce lifetime (seconds) field that controls how long a login code stays valid — default 120, automatically clamped to the 60–600 second range.

Improvements

  • Compatibility with Magento 2.4.9 and PHP 8.4 — resolved a setup:di:compile deprecation warning that could break compilation.
  • Faster social-account lookups during login, thanks to a new database index on the social-login account table (applied automatically on setup:upgrade).

1.2.5 (2026-04-21)

Improvements

  • Added i18n support for 15 core locales (ar_SA, cs_CZ, de_DE, es_ES, fr_FR, it_IT, ja_JP, nl_NL, pl_PL, pt_BR, pt_PT, sv_SE, tr_TR, uk_UA, zh_Hans_CN)

1.2.4 (2025-08-08)

Fixed

  • Redirect to the previous page after login on mobile devices

1.2.3 (2025-06-18)

Improvements

  • Improve WCAG 2.2 AA accessibility for social login templates

1.2.2 (2025-04-14)

Fixed

  • Compatibility with php8.4

1.2.1 (2024-07-05)

Improvements

  • Email status is automatically set to “Confirmed” if the customer registers via a social network

1.2.0 (2024-06-25)

Fixed

  • Added dependency on hybridauth/hybridauth package

1.1.5 (2023-12-13)

Fixed

  • Deprecated creation of dynamic property in OAuthConsumer.php

1.1.4 (2023-06-12)

Improvements

  • Additional checks when linking a social account with a customer

1.1.3 (2023-02-27)

Improvements

  • Added support of Magento 2.4.6

Fixed

  • Сompatibility with php8.1

1.1.2 (2022-08-19)

Fixed

  • Instagram icon

1.1.1 (2022-06-20)

Improvements

  • remove db_schema_whitelist.json

1.1.0 (2022-06-06)

Improvements

  • Migrate to declarative schema

1.0.12 (2022-03-24)

1.0.11 (2022-02-18)

Fixed

  • Issue with multistore

1.0.10 (2022-01-24)

Fixed

  • Compatibility with php8

1.0.9 (2021-01-12)

Fixed

  • Fixed the issue with the error during login when the customer has been deleted
  • Welcome email after creating acount with social login
  • Fixed the issue with social login related to required JS not loaded yet

1.0.8 (2020-10-22)

Fixed

  • Label for Client ID (Google) (12())

1.0.7 (2020-09-11)

Improvements

  • Small spelling fixes

1.0.6 (2020-08-25)

Fixed

  • Magento 2.4 compatibility (8())

1.0.5 (2020-08-05)

Improvements

  • Added social login block to the checkout

1.0.4 (2020-07-30)

Improvements

  • Support of Magento 2.4

1.0.3 (2020-06-17)

Fixed

  • Session clear issue

1.0.2 (2020-06-01)

Fixed

  • Reloading page on postMessage
  • Cache issue

1.0.0 (2020-04-13)

Features

  • Initial release