Version: 5.1.37
URL:
|
Daniel
Member Usergroup: Member Joined: Jul 08, 2009 Total Topics: 17 Total Posts: 31 |
Posted 07/01/10 - 2:03 PM:
If the guest can submit a listing and this doesn`t "needs validation", then the guest get the following message when he submits a link: No such content exists. The link you are following seems to have been incorrect. The link appears in the correct category but an other message would sure be better. Something like: Congratulation! Your listing appears in the directory. Thanks Paul for this software! |
|
Paul
developer Usergroup: Administrator Joined: Dec 20, 2001 Location: Diamond Springs, California Total Topics: 65 Total Posts: 7614 |
Posted 07/04/10 - 6:12 AM:
I get "The listing has been added." See here, I've enabled guests without validation in this sandbox: http://sandbox.webmastersite.net/wsnlinks/ Are you getting that as a redirect message, or as an error page that doesn't redirect? |
|
Daniel
Member Usergroup: Member Joined: Jul 08, 2009 Total Topics: 17 Total Posts: 31 |
Posted 07/24/10 - 12:29 PM:
Sorry for the late answer, but I`ve been on holiday for some days... I didn`t understood your question until now. There are two possibilities to show this message: 1. A redirect message namely "nosuchlink: {LANG_NOSUCHLINK}" 2. The page badrequest.tpl It is the badrequest.tpl page in my case. I wonder why this problem only is there if one submit a listing as a guest and not if one submit a listing as a member. Your sandbox-page has no problems at all. But I`ve got a (hidden) WSN-Installation without any changes in the templates (only chmod some files) only to see the update-features and only to see if some fault is my (template-)fault or perhaps a WSN-bug. On this page is the same behavior. |
|
Paul
developer Usergroup: Administrator Joined: Dec 20, 2001 Location: Diamond Springs, California Total Topics: 65 Total Posts: 7614 |
Posted 07/24/10 - 11:33 PM:
Bad request pages in various inappropriate places were a known bug due to new data-protection precautions in a version somewhere around 5.1.37. Was fixed in the release after the one where the bug was introduced. |
Sorry, you don't have permission to post. Log in, or register if you haven't yet.

Print