You will have to create the form and method to capture the donation if this is required
But ezpages can accept most all html
admin > tools > ezpages
You will have to create the form and method to capture the donation if this is required
But ezpages can accept most all html
admin > tools > ezpages
Zen-Venom Get Bitten
Okay, so if I understand correctly, the method that processes the form on the first ezpage would have to create and manage all the server-side resources that represent the transaction-in-progress, such as:
- create a shoppingCart object
- call its add_cart() method to put the donation product (with associated attributes) into the cart
- create/populate the order object
- create/populate whatever objects COWOA (or alternatively "Fast & Easy Checkout") uses to do its thing
- etc...
Presumably I would also need a second ezpage (with its own associated form and method) for presenting the confirmation dialog and commit button, and for processing the payment; and then a final ezpage for displaying the "Thank you" coda. (Right?)
Assuming that this understanding is at least somewhat close to the mark, have you got any suggestions for me on how to structure the PHP module containing the method code so that it has access to all the needed server side assets, and also for where the resulting PHP module should live in the site's directory hierarchy?
Probably most helpful, if such a thing exists (and easier than writing a lengthy narrative), would be a pointer to an actual example of an ezpage containing a form for doing something non-trivial, and to the PHP module containing the associated method code.
Thanks,
M
If I understand the question, I have used Machform (not free, but worth the cost) to create stand-alone forms in EZ pages.
But ez-pages cannot handle PHP which you would need for creating opjects etc. You need to use define pages for that - they are PHP files themselves, whereas ez-pages are only database information.
Since I haven't played with ezpages at all, and have only done super-trivial things with define pages (certainly no form processing), I'm probably not really qualified to have an opinion on this, but: wouldn't it be possible to code the form on an ezpage, and implement the form-processing logic in a PHP module, which would be invoked via the form's "submit" method?
This was how I was interpreting Kobra's response to my original post.
M
Hmm... coding an HTML form into an ezpage doesn't seem to be where the major challenge of this exercise lies.
I'm much more concerned to know how to structure the back-end PHP code that processes the form -- which I don't think Machform will help me with, unless I've missed something in my quick perusal of the appnitro.com site.
M