- Thread starter
- #41
It will continue to be supported for the foreseeable future; there is currently no replacement. "validate.php" was added back since some applications wouldn't follow the redirect to "/legacy/validate".Question, saw that validate.php was added back for us - is this preferred?
You should always check to see if a user has voted for redirecting them. Otherwise you open up yourself to redirecting your users to a site that is down. Setting a cookie is advised, especially for bigger hotels. I don't know if it'd actually cause issues, as I'm pretty sure those in the past were caused by hotels that would send a request to FindRetros every time they updated the user count on the client, which was a problem. You should always send the user with the "return" query arg set, as that will guarantee that they are sent back to the "return_url".What way should we go about it if we were not to use that file to check the request? (return=1 on voting URL & a cookie?)
I'd love to hear if anyone is having issues as well, feel free to post in this thread.Off-topic: Who is having redirection loop issues? I was put off from enabling voting due to this, but I've just enabled it and are not having any issues. So I'm curious to what some people are using? Feel free to PM me if you are having issues.