You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to suggest adding an option to use the legacy login page in the ps_accounts module.
The new login page introduces some challenges for our team:
Complexity: The new login page requires additional steps compared to the legacy version, such as clicking "Login to Back Office" before entering credentials or using Google login. This can be cumbersome for frequent logins.
Customizability: The new login page includes background images that may not be visually appealing to all users, especially those featuring people. The option to customize or remove these images would improve user satisfaction.
We believe a toggle button to switch between the new and legacy login pages should be added to the module's configuration settings. This would allow store administrators to choose the preferred login method for their team.
Hi there,
I'd like to suggest adding an option to use the legacy login page in the ps_accounts module.
The new login page introduces some challenges for our team:
Complexity: The new login page requires additional steps compared to the legacy version, such as clicking "Login to Back Office" before entering credentials or using Google login. This can be cumbersome for frequent logins.
Customizability: The new login page includes background images that may not be visually appealing to all users, especially those featuring people. The option to customize or remove these images would improve user satisfaction.
We believe a toggle button to switch between the new and legacy login pages should be added to the module's configuration settings. This would allow store administrators to choose the preferred login method for their team.
Thank you for your consideration.
new login page execution link:
ps_accounts/src/Hook/ActionAdminLoginControllerSetMedia.php
Line 54 in 4317045
The text was updated successfully, but these errors were encountered: