Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We've moved the forum!

Please use forum.silverstripe.org for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

E-Commerce Modules /

Discuss about the various e-commerce modules available:
Ecommerce, SS Shop, SilverCart and SwipeStripe
Alternatively, have a look the shared mailinglist.

Moderators: martimiz, Nicolaas, Sean, Ed, frankmullenger, biapar, Willr, Ingo, Jedateach, swaiba

MemberID and OrderID empty in DB


Go to End


3 Posts   2057 Views

Avatar
fritzkopf

Community Member, 10 Posts

24 August 2009 at 7:24pm

hi guys,

i create a website with the ecommerce-module...

when i make an order, everything works fine and the order writes to the DB,... but the only Problem is, that in the DB in the Payment the orderID and memberID are empty... and i cant see what a payment-method the the client have select...

here is the DB: http://www.reimer-ministries.com/PaymentDB.jpg ... see at the right that the fields are empty (0) ...

and here is my orderform.php ... http://gist.github.com/173712

has anybody an idea why its not working?

thank you for helping me !!!

fritzkopf

Avatar
dalesaurus

Community Member, 283 Posts

25 August 2009 at 6:18am

You appear to be using the stock processOrder function, if these fields are not linking correctly check out the error logs. These certainly should be throwing errors if the save isn't working. Can you use your site in Dev mode to checkout to see what happens?

Avatar
runnerman

Community Member, 24 Posts

25 August 2009 at 8:28am

Hey,

What version of silverstripe and the ecommerce and payment modules are you using? The latest ecommerce version (0.6 beta 1) does not work properly with previous versions of silverstripe and I'm sure I read somewhere that the error you describe is part of the incompatibility. If you're not running the latest version of silverstripe, I'd suggest upgrading to version 2.3.3.

Hope that helps.