Response Time
24 — 48 hours
Hi,
It seems that Easysocial handles logins for a Joomla site, and over-rides the com_users&view=login.
The problem with this in my hands is that in com_content or com_k2 or perhaps other components if one tries to access a restricted item and prompts a login with a return url as return=something_base_64_encrypted then, Easysocial will handle the login with com_easysocial&view=login. The problem here is that the return URL will be what one specifies in the backend under Settings > Users > Login Redirection (i.e. some menu item), not what the user was looking for originally.
Perhaps EasySocial should only handle Easysocial login events only and not others, leaving the rest to Joomla's com_users&view=login. Otherwise, an important usability issue gets broken by Easysocial.
You can see this problem in the example link I put in below.
Jordan
It seems that Easysocial handles logins for a Joomla site, and over-rides the com_users&view=login.
The problem with this in my hands is that in com_content or com_k2 or perhaps other components if one tries to access a restricted item and prompts a login with a return url as return=something_base_64_encrypted then, Easysocial will handle the login with com_easysocial&view=login. The problem here is that the return URL will be what one specifies in the backend under Settings > Users > Login Redirection (i.e. some menu item), not what the user was looking for originally.
Perhaps EasySocial should only handle Easysocial login events only and not others, leaving the rest to Joomla's com_users&view=login. Otherwise, an important usability issue gets broken by Easysocial.
You can see this problem in the example link I put in below.
Jordan
5 Replies
The replies under this section are restricted to logged in users or users with an active subscription with us
