Hi,
When I have created a booking, then it is coming to be set to approval. (showing up in the admin area.) If it is not been approved yet, but updated first by the client -then the staus in the bookings_schedules tabel will be set to 4 - from 1. This means, that it will not show up to approval, and the date and time will not show up as a conflict.
I will try to find a solution to it myself, and post it here.
If you have any experience with this problem, I would of course be happy to not use a lot of time on it.
If you need access to some of my things, to check out this problem, then just say so.
I have installed this module on drupal 6. I am running php5.2.9.
Thanks in advance,
AndreaD
Comments
Comment #1
andread commentedHi,
I find my way:
In the public.admin.inc file I have set a few line in - it will creat a new tabel with those booking, which have been updated by the clients:
From line 9 my code looks like this:
And that is it! Now I can keep an extra eye on those bookings, which have been updated by customer.
(I don´t exactly know yet, if the customer delete a booking before approval what happens.)
Hope it will help others,
AndreaD
Comment #2
Anonymous (not verified) commentedNormally a booking should show up on the administrative page after the client has confirmed his email address by clicking the link in the confirmation email. Unconfirmed bookings neither conflict with existing bookings nor are they shown on the administrative page to avoid spam-related problems.
And changing a booking after it was confirmed should not change its status - I'll look into this.
But I'd be happy to add your patch (or something similar) as an optional setting - Thanks :)
Should - in your eyes - an unconfirmed booking conflict with new bookings?
Comment #3
andread commentedHi,
These bookings I have been talking about, was sent from booking request, then cofirmed by client, and then updated by client - before admins approval. It means, it was in the approval que before the client has updated it. So maybe, the real problem is, that when updateing by client, then the status is set to 4. I could not really find out (probably not used enough time on it) what are the different status codes means.
I don´t think unconfirmed booking should come up as a conflict - or it should be maybe chooseable in a checkbox. (I will only allow registreted users to book - so that is a security itself against spam.)
But I think when a client can update the booking there is standing, you can delete the booking too. I can not see any button for it, or it is not working as it should. I will set in the translation that they have to write in the comment line that they woul like to get this booking deleted.
Thanks, and I would like to say that I have used some time to check out the other modules doing bookings, but I find that your module is working very nice. Thank you!
Regards,
AndreaD
Comment #4
Anonymous (not verified) commentedThanks for the info, I'll look into it. Could you update to DEV (both in Bookings API and Public Bookings)? I don't think this would solve the problem, but it would make patching easier ;)
Comment #5
andread commentedHow do I do that? :)
Comment #6
Anonymous (not verified) commentedDownload
extract both to your sites/all/modules/ directory and run update.php (just install them like a normal module update) :)
Comment #7
andread commentedNo, you are right, it is not solveing the problem.
Those entries uppdated by the customer dosen´t show up in the dev either.
Is it still ok to run dev on a site, which will handle online bookings from the next week? is it stable enough? or there is no difference form the other just the patching?
Comment #8
Anonymous (not verified) commentedAt the moment the dev-release contains a couple of minor bug-fixes and should be more stable then the ALPHA-release. Under normal conditions I would recommend against using the DEV-release on a production site but ATM this should not be a problem.
I'll release a new Alpha as soon as this bug is fixed (I guess Tuesday), you should then be able to update back to ALPHA.
Comment #9
Anonymous (not verified) commentedWhat's actually happening is that a booking is set back to "unconfirmed".
The attached patch should set a booking to "Pending" (awaiting approval) if it was confirmed previously, otherwise to unconfirmed.
Could you test this?
Comment #10
Anonymous (not verified) commentedCommitted after separate testing by a friend. Updating to the last dev (should be available in less then 12hours) should fix this problem. Please report back (working or not) - I'll release the next ALPHA with this bugfix and the option to allow "display of unconfirmed" and (perhaps) "conflict with unconfirmed"
Comment #11
Anonymous (not verified) commentedCommitted an optional (true by default) view on unconfirmed bookings on the administration page (see comment#1 by AndreaD)
Comment #12
Anonymous (not verified) commentedCommitted (optional) conflict with unconfirmed or pending bookings.
Please update BOTH (Bookings API and Public Bookings) and give feedback whether its working now - I'd like to release the next ALPHA.