Redirect on http://error.yze/ ?

[vidierre]

May be this is a newbie question and it couldn't be a CASPIO matter. But in may App I have a dashboard page that randomly, on the first display, redirects to http://error.yze/ 

I googled about it but I found nothing. I tryed also to ask to my theme support (CASPIO is deployed on a Wordpress site) but they do not know about it.

Anyone has been faced with this?

[sandy159]

Hi @vidierre,

Is there any redirection upon login? 

Please check the Advanced settings in the Authentication: https://howto.caspio.com/authentications-and-connections/authentication/authentication/

You may also want to check any script for the redirection on login on the DataPage or in WordPress.

Please feel free to update this thread with more details.

[vidierre]

20 hours ago, sandy159 said:

Hi @vidierre,

Is there any redirection upon login? 

Please check the Advanced settings in the Authentication: https://howto.caspio.com/authentications-and-connections/authentication/authentication/

You may also want to check any script for the redirection on login on the DataPage or in WordPress.

Please feel free to update this thread with more details.

20 hours ago, sandy159 said:

Hi @vidierre,

Is there any redirection upon login? 

Please check the Advanced settings in the Authentication: https://howto.caspio.com/authentications-and-connections/authentication/authentication/

You may also want to check any script for the redirection on login on the DataPage or in WordPress.

Please feel free to update this thread with more details.

You caught the culprit, because I had a page with an old  authentication pattern. I sow what happened making a movie to the browser to looking into the changin Urls.

Before I used one authentication redirecting to an HTML datapage in charge of redirect users based on their profile-role (students or teachers).
Now I use two different authentication.

What happened was:

• Techers authenticate with the Teacher-authentication that redirect to page-A (the new one)
• page-A was still based on the All-Autehtication (the old one) that redirect to the HTML Page that lead to the desired page.

I think the mess was that an authenticated user was on a page requiring a different authentication. Using the right authentication all works fine.

BUT I do not understan fromwhere does it come from the error.yze Url that I never saw before.