2. PHPRunner General questions
  3. [SOLVED]  Event Registration Form?
This topic is locked
[SOLVED]

 Event Registration Form?

 		10/31/2012 00:09:00
PHPRunner General questions
bbarker author

<img src='https://asprunner.com/forums/file.php?topicimage=1&fieldname=question&id=20235&image=1&table=forumtopics' class='bbc_emoticon' alt=':D' /> I need to build a form for 800 users to register for an EVENT. They will have about 25 different selectable options that all have different costs associated with them.
Does anyone have a suggestion on how I should begin this effort? Are there any templates that would help accelerate the design stage? Any non-PHPRunner builders that I could use, and then ADD to my PHPRunner environment?
By the way I have a MySQL db with all users already identified - along with current membership information (eg. Expiration dates)
And -- once they register, I'll want to process it for credit card payments.
Sergey Kornilov admin 10/31/2012

Typically registration page is simply an ADD page of the login table.
Though your situation is a bit different the same idea can be applied. Create a new table in your database dedicating a single field for each option. Then create an ADD page for this table which will be your event registration page. In AfterAdd event you can add your logic to calculate the cost users need to pay and you can, for example, redirect them to the Paypal page after that so they can pay.
You can check Paypal template that comes with PHPRunner to see how Paypal 'Paynow' button can be implemented.
bbarker author 10/31/2012

Thanks Sergey. That was a good summary.
This might be a good tutorial for someone to add to the Tips and Tricks (with screenshots).

I'm sure that lots of folks need REGISTRATION forms on their site.
Specifically, detailed info on the "math" routines for calculating line-item fees,

and the TOTAL calculation, would be useful.

Also, showing the PayPal code would be easier than having to go look find/look at other applications.
But I have enough now to get started. Thanks again.