Aug 2010
6 / 7
Aug 2010
Aug 2010
gsgkenny
Aug '10

Wondering if there is a way to tie in e-junkie to my webistes database?

That way when users log in they can see all previous transaction details. What they ordered, when, what the code was, etc.

  • created

    Aug '10

  • last reply

    Aug '10
  • 6

    replies

  • 1.1k

    views

  • 2

    users

  • 1

    link

gsgkenny
Aug '10

Im still trying to learn PHP / MySQL.

So that works by me setting up a specific page that the info will get sent to, then once the info hits that page my PHP throws it into my database?

E-junkie_GuruWebmaster & Support Guru
Aug '10

It doesn't have to be a "page" per se, in that it doesn't need to output any HTML that a browser would display, since this would be a one-way back-end transmission from our server to your script's URL.



Our Integration submits the data via HTTP POST, which is the same method most Web-based HTML forms would typically use, so any generic form-handler type of script should be able to receive our Integration data and do whatever that script normally does with form data (send it to you in email, save it to a database, append it to a text file, etc.)

gsgkenny
Aug '10

Right, for my logout page it is nothing but PHP code to logout, there is no actual HTML or design. It just closes the session and redirects to login page. Same concept with the page I was talking about.



Like I said I am new though, and when it comes to doing things with MySQL and PHP it usually does not work out for me...



So when my page accepts this info. is it accepting it just like it shows on the in house transaction history? I would have to set columns for all of the info. e-junkie logs and accept NULL in many cases?

gsgkenny
Aug '10

$dbconnect = mysql_connect($dburl,$dbuser,$dbpass);

mysql_select_db($dbname,$dbconnect);



$time = $_POST[' ? TIME ? '];

$email = $POST['payeremail'];

$item = $POST[itemname''];

$qty = $_POST['quantity'];

$code = $_POST['key'];



mysql_query("INSERT INTO orders (paydate, username, items, qty, code) VALUES ('$time', '$email', '$item', '$qty', '$code')");



So this is basically what I think I will need. However I did not see any thing for time on that list and Im not sure what the item specific "x" refers to.

Im also unsure if this will run in the backend, or if the page will have to be viewed to upload to the database. When I was uploading all old transaction records I had to refresh the page for it to send the data into the database.

E-junkie_GuruWebmaster & Support Guru
Aug '10

Any custom PHP (or other custom script) development at your end would be entirely up to you, as we cannot advise you on general-purpose programming techniques. You might want to look up references on PayPal IPN, since our Integration submissions are designed to follow PayPal's IPN data format for easy compatibility with third-party services and "off the shelf" scripts designed to accept IPN. Just make sure you are not trying to validate the IPN with PayPal (which would fail since the submissions are coming from us rather than PayPal, and we validate the original IPN with PayPal before forwarding it to you anyway), and make sure your script can handle or ignore some extra fields we add to the base IPN data spec, for data we collect or provide that PayPal does not.



All that said, we can certainly explain how things work at our end, such as the "X" in item-specific variable names that we can submit to your URL via our Integration feature.



Whenever we POST to your Integration URL, we always provide the complete order data, including data for all items in the order, regardless of whether we're submitting to a Common Notification URL (for all orders) or to a Payment Variable Information URL (only for orders of a specific product).



The item-specific variable names will each have a numeric suffix corresponding to the item's cart position in that order, so you can tell which variables go together for which item in the orcer. E.g., 'item_name2' goes together with 'item_number2' and other item variables suffixed with '2', all referring to the same item in that order, where the '2' indicates that was the second item listed in the buyer's cart.



When we POST this full set of order data to a Payment Variable Information URL given in the settings of a specific product, you may want to know which particular item in the order triggered that particular submission, and that's what the 'item_cart_position' variable reveals. E.g., if item_cart_position=2, you will know the 2nd item in the cart was the one that had the Pmt. Var. Info. URL configured which triggered that particular submission, so data pertaining to that item would be given as 'item_name2', 'item_number2', etc. in that submission.