I've just started using TP with SMF 1.1.1 and although the Shoutbox works fine for admin-level users, it always comes back with the error "Unable to verify referring url" for anyone else. I've searched these forums for an answer, but haven't seen one. Is anyone else having this problem or know how to solve it?
Quote from: TWD on February 06, 2007, 09:06:40 PM
I've just started using TP with SMF 1.1.1 and although the Shoutbox works fine for admin-level users, it always comes back with the error "Unable to verify referring url" for anyone else. I've searched these forums for an answer, but haven't seen one. Is anyone else having this problem or know how to solve it?
I've had this problem every once in awhile even as an admin.I usally just try again and it works.One of my members had the same issue.I think I checked the permissions for that member and checked allowed and that cleared it up.Try that and see if it helps.
I get this all the time and it appears to be getting worse. Recounting the totals seems to clear it up for a while, but it always comes back.
I get this error as admin. Anyone come across a solution? I mean, my permissions are fine...
I also get this every once in a while. Not sure what causes it .
I think this happens to most of you because you may be browsing your forum while using http://www.yourdomain.com when your domain in your SMF server settings is set to http://domain.com. I noticed this on TWD and riders site. You're guys links to your site has www. in them but your server is set not to use the www. When you post in the shoutbox from www.yourdomain.com and your server is set to use www. the referring URL is wrong, hence the error. Change your SMF server setting to have the www. and I bet it goes away.
Thanks Ichbin, I'll give that a try tomorrow...will update if solved.
Quote from: IchBinÃ,â,,¢ on April 06, 2007, 02:29:59 AM
I think this happens to most of you because you may be browsing your forum while using http://www.yourdomain.com when your domain in your SMF server settings is set to http://domain.com. I noticed this on TWD and riders site. You're guys links to your site has www. in them but your server is set not to use the www. When you post in the shoutbox from www.yourdomain.com and your server is set to use www. the referring URL is wrong, hence the error. Change your SMF server setting to have the www. and I bet it goes away.
Hey, that's a great tip regardless of whether there is an issue or not ATM. Thank you :) I'm going to check this out to make sure it's www anyway right now.
I've also seen this type of thing cause session problems with people not being able to logout or login etc.
Quote from: IchBinÃ,â,,¢ on April 06, 2007, 02:29:59 AM
I think this happens to most of you because you may be browsing your forum while using http://www.yourdomain.com when your domain in your SMF server settings is set to http://domain.com. I noticed this on TWD and riders site. You're guys links to your site has www. in them but your server is set not to use the www. When you post in the shoutbox from www.yourdomain.com and your server is set to use www. the referring URL is wrong, hence the error. Change your SMF server setting to have the www. and I bet it goes away.
Let me buy you a beer.I'm pretty sure that worked.Didn't get the message.Thanks for the help.
Hi
Cheers for the Info IchBinâ,,¢ and it appears to have fixed the Problem :)
Well, let me just say THANK YOU for using the search!
:up: :up: :up:
Ok, this'll ruin your day. ;D
I have the server settings without the www but the interesting bit is that the browser also shows it without the www in the address bar.
So in both cases it's showing http://ourdomain.com and I still get the "referring url" error intermittently.
Bet you aint gonna thank me for using the search feature. ;)
EDIT: Scratch this, I think I've got it. When I was logged into admin the address bar was showing http://ourdomain.com but when I logged out and came back to the site via my bookmark it said http://www.ourdomain.com
Obviously to log in I had to be hooked up to the server url. I've changed that to include the www.
Should be fine now but I'll mention it if the error comes back.