haamid.gazi
Posts: 13 Joined: Wed Jun 25, 2008 11:30 am
Post
by haamid.gazi » Thu Sep 25, 2008 2:05 pm
Hi,
we have installed webinator on a new server. the error messages are coming on the front end page. is there a setting to hide the error messages from coming on frontend whereas they continue to come in vortex.log and that is the behavior on our other servers as well.
Regards
Haamid
mark
Site Admin
Posts: 5519 Joined: Tue Apr 25, 2000 6:56 pm
Post
by mark » Thu Sep 25, 2008 2:47 pm
You shouldn't have to but you could add
<putmsg print off>
to the beginning of the search script.
But what kind of errors are you getting? You shouldn't
generally get errors unless the user enters bad queries.
Also make sure you're not in test mode. Test mode will show the errors visibly whereas normal mode will hide them within html commands on the page.
John
Site Admin
Posts: 2625 Joined: Mon Apr 24, 2000 3:18 pm
Location: Cleveland, OH
Post
by John » Thu Sep 25, 2008 2:47 pm
You can use the PUTMSG directive to control the behaviour of messages.
http://www.thunderstone.com/site/vortexman/putmsg.html
John Turnbull
Thunderstone Software
haamid.gazi
Posts: 13 Joined: Wed Jun 25, 2008 11:30 am
Post
by haamid.gazi » Thu Sep 25, 2008 3:31 pm
Hi John,
using same script we are not getting errors on front end in production. so i believe it has to do with some system settings. and how can I check whether i am in test mode.
Regards
Haamid
haamid.gazi
Posts: 13 Joined: Wed Jun 25, 2008 11:30 am
Post
by haamid.gazi » Thu Sep 25, 2008 3:32 pm
This is the rror message which usalluy come in vortex log is appearing on frontend
32: command sh returned exit code 137 118 /webinator/search
command sh returned exit code 1
mark
Site Admin
Posts: 5519 Joined: Tue Apr 25, 2000 6:56 pm
Post
by mark » Thu Sep 25, 2008 3:52 pm
In test mode there's "mode=admin" in the url.
What's line 2008 of your search script? It looks like whatever shell command is being run there is failing.
haamid.gazi
Posts: 13 Joined: Wed Jun 25, 2008 11:30 am
Post
by haamid.gazi » Thu Sep 25, 2008 4:00 pm
The issue is not why it is failing , the issue is why the error output is coming in the html code (i.e. front-end) can you please help me in figuring that out.
Regards
haamid
haamid.gazi
Posts: 13 Joined: Wed Jun 25, 2008 11:30 am
Post
by haamid.gazi » Thu Sep 25, 2008 4:01 pm
the url which I am accessing does not have mode=test in it.
Regards
Haamid
mark
Site Admin
Posts: 5519 Joined: Tue Apr 25, 2000 6:56 pm
Post
by mark » Thu Sep 25, 2008 5:02 pm
You have 2 options. Hide the messages as described above or fix the failure so no message is generated.
mark
Site Admin
Posts: 5519 Joined: Tue Apr 25, 2000 6:56 pm
Post
by mark » Thu Sep 25, 2008 5:02 pm
One other possibility is that your vortex.log is not writable by the user that texis is running as.