URL: http://www.uburst.com/cgi-bin/dcforum/dcboard.cgi
Forum: uReserve_troubleshooting
Thread Number: 29
[ Go back to previous page ]

Original Message
"uburst reserve problems"

Posted by john glendinning [john.glendinning@comdirect.co.uk; macnab@vodafone.net] on at 08:27 AM
Hi
We run an online booking facility for our tennis club using uReserve. Have a strange problem, that means that the first time you book a resource everything works fine, but the next time you get a pop up - not of the booking sheet, but of the resource availability that you clicked on - ie just a copy. Once this has happened the next week and previous week buttons don;t work either.
url is www.greenegg.net/ctc -
Any help ?
Thanks
John

Table of contents

Messages in this discussion
"uReserve problems"
Posted by Microburst Support Team [support@uburst.com] on at 03:24 PM
Going to the link you provided, we seem to need an access user and password to get in, so go ahead and send us that information, along with any other information that would help, such as server type, and using our official support request form at this link:

http://www.uburst.com/supportform.html

If you have made any customizations to the script, go ahead and send us that as well.



"RE: uReserve problems"
Posted by Bill Weiner on at 07:16 AM
I took a look at your site and it appears that for some reason, you server is not accept HTTP "GET" requests.

That is, when you click on a Resource Name for a particular day, that will basically link you to the URL of your script, followed by a "?" and additional command information, such as:

http://www.greenegg.net/perl/ureserve.pl?command=who&name=Tennis_Court_1&week=06-22-2003&day=1&begin=16&seconds=1056261930

A URL followed by a "?" is the standard way of sending a "GET" request to a server (similar to a "POST" request). On your server, however, it appears that GET requests are not being processed. (Try pasting the above URL and see.)

You will need to contact your web hosting provider to help you resolve this so that you can accept http "GET" requests (a very standard thing... and in fact, I've never seen it disabled before.)