beventsmadeeasy
Member
Good, thank you. I've got to test it with a live payment.
In the future, a useful feature might be to distinguished between RESERVED (currently "booked") attendees and CONFIRMED/PAID attendees --for purposes of event planning and determining available seating.
Franky
Key Master
No, that will always be a manual process (well, at least for now). No real cron-integration exists for wordpress, so "timeouts" are difficult.
Franky
Key Master
Well, for each booking a unique number is already being generated. The thing is: I've never seen asynchronous payment using paypal yet. People would need to "log in" to EME again in one way or another and then click the button. That's possible of course ... I could always regenerate the payment code for each unpaid booking for a user. Hmmm ... interesting ....
beventsmadeeasy
Member
Let me be more clear -- My "going a different way" suggestion was, for the regular existing real time order process:
1. User registers/requests event seats, just as happens now. EME Unique Number generated, just as happens now. But #_BOOKEDSEATS does NOT increment yet.
2. User then clicks the provided PayPal link and immediately pays for seats (via PayPal or new method). EME Unique Number switches to PAID, just as happens now.
3. Only THEN, with the EME Unique Switched to PAID, does the #_BOOKEDSEATS get incremented.
This way we could track "registered" (requested) spots versus actual confirmed/paid spots. This behavior for #BOOKEDSEATS could be controlled by a new "require payment confirmation" toggle WITHOUT having to deploy a separate #_CONFIRMEDSEATS counter, which was my original thought.
As to the "asynchronous payment" idea, my related wishlist item was having a few variables (either replacing or in addition to #_BOOKEDSEATS) that would tell not only who had "registered" for (requested) the event but also who had PAID (or been approved for) the event. Right now EME seems to treat every unconfirmed request as reducing the number of available seats. This is not realistic for many purposes.
The asynchronous payment idea is similar to GuiltyCol's request #4 at PayPal Integration Feedback
Ideally the email confirmation should contain a url that allows the user to return and pay at some point in the future (the url of the Thank You page in (3) above would do...."
Anyhow, just food for thought for your future road map.
beventsmadeeasy
Member
Hi Franky. You wrote that "Payment in paypal changes the payed status for the booking".
We finally got our first live payment, and it did NOT work that way. The reservation still shows as pending, with a paid status of "No".
It was paid via PayPal "e-check" -- is that why? Does the automatic EME update only work with credit card transactions?
Hmm, you have an IPN.php file, but I don't see any log directories where I can track what happened, and the IPN script seems to have everything set at defaults? Am I looking in the right place? Do I need to change this code manually?
class IPN {
// Official url: https://www.paypal.com/cgi-bin/webscr
// Testing urls: (do test!)
// - https://www.sandbox.paypal.com/cgi-bin/webscr
// - http://www.eliteweaver.co.uk/testing/ipntest.php
public $paypal_url = 'https://www.paypal.com/cgi-bin/webscr';
// your paypal email (the one that receives the payments)
public $paypal_email = 'paypal@example.com';
// log to file options
public $log_to_file = true; // write logs to file
public $log_filename = '/path/to/ipn.log'; // the log filename (should NOT be web accessible)
// log to e-mail options
public $log_to_email = true; // send logs by e-mail
public $log_email = 'log@example.com'; // where you want to receive the logs
public $log_subject = 'IPN Log: '; // prefix for the e-mail subject
// database information
public $log_to_db = true; // false not recommended
public $db_host = 'localhost';
public $db_user = 'some_user';
public $db_pass = 'some_password';
public $db_name = 'ipn';
Franky
Key Master
See the function "eme_paypal_ipn" in eme_rsvp.php if you want to activate logging. I never tried an e-check though ...
beventsmadeeasy
Member
[ Very strange; the forum wouldn't let me post this here until I created a dummy post and then edited the below in... ]
Thanks, I'm doing that now. (Maybe the option should be in Settings.) I guess these are the only two fields I should touch:
// log to file options
$ipn->log_to_file = true; // write logs to file
$ipn->log_filename = '/paypal-ipn.log'; // the log filename (should NOT be web accessible and should be writable)Apparently the library you've used supports e-mail notification and database integration... I'm assuming the log comes into play ONLY during active PayPal sessions, and doesn't log any other part of the reservation process.
I'm guessing the slow echeck is by definition NOT an "instant payment" so that's why our payment didn't register in EME... But it's still the case that the stock EME setup is supposed to automagically update the "Paid" status, correct?
Looking into what "IPN" is, I find a nice tutorial at http://www.micahcarrick.com/paypal-ipn-with-php.html
Hmm, looks like there's at least one Google Checkout routine on phpkode.com too. Too bad I can't really program PHP...
beventsmadeeasy
Member
Wait a second; do I need to specifically enable "IPN" for our PayPal account? This site implies that I do...
http://net.tutsplus.com/tutorials/php/using-paypals-instant-payment-notification-with-php/
Franky
Key Master
sometimes the forum does act strange ... I should switch to something else :-)
Did you got it working ok now?
beventsmadeeasy
Member
It just occurred to me that I might need to use /home/myaccount/paypal-ipn.log as the path, because I'm on a shared hosting account. (I was assuming that my account's root was considered root but perhaps that's wrong.) I was just trying to keep it out of www/mydomain, as instructed. I'll let you know if it starts logging now.
On the bright side, the automated "Paid:Yes" function is working now, even for that "echeck", which took a couple of days but now shows Paid, somehow.
A minor bug to report -- in the "Respondents" sidebar in the Event setup screen, there are little "x" circles next to each reservation. These highlight when hovered over, but clicking them does NOT delete the reservation...
Franky
Key Master
That's fixed in the current dev, see here: http://www.e-dynamics.be/bbpress/topic.php?id=1767#post-6852
You must log in to post.