This object is in archive!
Cannot create a new response after upgrading to 2.3.4
Hello,
after upgrading to 2.3.4 we are no longer able to create a new Response. Whenever a user clicks at "Post Response" he is redirected to the login page (we use SSO), even if he is already authenticated. This seems to be done by javascript since the browser asks the user if he really whishes to leave the site when he clicks at "Post Response".
When I deativate SSO everything works again.
Any idea what could be the cause?
Files:
Events.zip
Stebi,
Please find attached zip with solution. Extract file to application\modules\loginplus\handlers\ and it should work
Stebi,
Please find attached zip with solution. Extract file to application\modules\loginplus\handlers\ and it should work
Stebi,
We can't reproduce this bug. Could you please give me more details on what SSO method do you use and what settings of SSO you setup, like settings of disabling registration email and use only sso method?
Look forward to get more details or provide FTP access to support(at)useresponse.com in order for us to take a look at the problem
Stebi,
We can't reproduce this bug. Could you please give me more details on what SSO method do you use and what settings of SSO you setup, like settings of disabling registration email and use only sso method?
Look forward to get more details or provide FTP access to support(at)useresponse.com in order for us to take a look at the problem
We use OneLogin SSO.
Nothing was changed in the UseResponse code, no js, nothing. I only added a new translation.
Cache files have been manually removed. It doesn't matter, if the user is an admin or has just regular permissions.
Registration email has been disabled and use only sso has been enabled.
As soon as I disable OneLogin SSO then posting new responses works again.
What I do to reproduce the problem:
1. Login to the UR either from our page through SSO or directly at the use response app by calling url.com/login. It doesn't matter if I really use SSO to login it just has to be activated.
2. Clicking "New Response", filling out all required fields and then clicking "Post Response"
As soon as you click at "Post Response" a popup is displayed asking if I really want to leave the page. If I click yes, then I'm redirected to the SSO login page of my website. If I click no, then nothing happens.
Is it possible that the problem relates to https://help.useresponse.com/responses/loginplus-first-login-post-with-ldap-credentials ?
The message I get seems very much like the alert you mention in your last comment.
We use OneLogin SSO.
Nothing was changed in the UseResponse code, no js, nothing. I only added a new translation.
Cache files have been manually removed. It doesn't matter, if the user is an admin or has just regular permissions.
Registration email has been disabled and use only sso has been enabled.
As soon as I disable OneLogin SSO then posting new responses works again.
What I do to reproduce the problem:
1. Login to the UR either from our page through SSO or directly at the use response app by calling url.com/login. It doesn't matter if I really use SSO to login it just has to be activated.
2. Clicking "New Response", filling out all required fields and then clicking "Post Response"
As soon as you click at "Post Response" a popup is displayed asking if I really want to leave the page. If I click yes, then I'm redirected to the SSO login page of my website. If I click no, then nothing happens.
Is it possible that the problem relates to https://help.useresponse.com/responses/loginplus-first-login-post-with-ldap-credentials ?
The message I get seems very much like the alert you mention in your last comment.
Stebi,
The bug is identified. We'll fix it shortly and provide fix for you
Stebi,
The bug is identified. We'll fix it shortly and provide fix for you
Stebi,
Please find attached zip with solution. Extract file to application\modules\loginplus\handlers\ and it should work
Stebi,
Please find attached zip with solution. Extract file to application\modules\loginplus\handlers\ and it should work
Thank you, it works.
Thank you, it works.
Replies have been locked on this page!