SaranacLake
Members-
Posts
648 -
Joined
-
Last visited
Everything posted by SaranacLake
-
I'm just going off of what all of the UI/UX experts says is the best way to lessen "cart adandonment". I've read tons of articles and research studies so I trust that these people know more than me. Besides, what their research shows makes sense. Either way, will the approach we have been talking above work?
-
Here is a crude mockup... Complete your subscription in a few easy steps... Step 1: Confirm items << shopping cart details here >>> Step 2: Enter Account Details Name: ____________ Username: _________ Email Address: _____________ << Send a "Security Code" to my email >> <===== user would click here Security Code: ____________ (**Paste the code from the email you just received) Password: ___________ Confirm Password: _____________ Step 3: Sign Member TOS __link to Member TOS____ Type "I agree with the Member TOS": __________________ Step 4: Make Payment Cardholder: _________ Credit card #: ____________ and so on...
-
Correct. But when they click the "Send a security code to my email" and then presumably go check their email address and copy & paste the security code into the field directly beow the button they just clicked, then I will know that their email address is valid.
-
That is what I have... When a new customer decides to subscribe, I now have a one-page registration and check-out page where they enter Username, Email, Password, Sign TOS, Name, Address, Tele #, and Credit Card Details. The point of my OP is that after the Name, Username, and Email, I want them to click on a button label "Send Security Code to my email", the click a button, it fires off an email with an activation link to the email they entered just a second ago, they then paste that code in the form, and continue filling out things like Password, Billing Address, CC Details. I would just assume know from my end that the email is valid *before* I give them an account, but I want to avoid this being a multiple page registration process like websites did in the past and even how this website does it today.
-
This is a combination Registration and Payment form. The user is creating an account AND paying for an online subscription all at once. (I've done lots of research on this, and all of the experts say that if you can do all of this on ONE page versus the old-fashioned way of multiple screens then you will have much better conversion rates!) So on this form, the user enters Name, Username, Email - then I want to take that email and make sure it works so I have a "Send code to my email" button - and then after that comes Password and so on, although they should have entered anything in those fields yet. So I guess the reason I was unsure if reloading the form was avoidable is so I didn't lose the initial fields. Since I don't know JavaScript yet, I do form validation when the form is submitted using PHP. If it fails, I reload the form. So I guess that would be the "catch" in this approach is that I wouldn't have validated the email field yet, although I guess I could validate that field when the form is submitted with partial data. On a side note, how important/beneficial do you think it is to send an email trying to verify if the email is valid and accessible? Is that "old-school" or does it have any value in what I am doing? Since I use email to communicate with customers/users, I want to make sure I have a valid email on file. Then again, I buy stuff online all of the time and a lot of ecommerce sites just trust you that you gave them a valid email to send a receipt to. So what do you think about all of that?
-
I want to learn JavaScript, but what you described would take too long for right now. So if I go the PHP route, you are saying I would have to submit the form to fire off an email and then reload the same form, right? Pseudo-code like this maybe... if ($_POST['submit']=="Send Security Code"){ // Send email here callPHPMailer( ); exit(); } Then I could use "sticky" fields to retain most of the data the user entered right?
-
I am creating a Registration form and want to have a command button in the middle of the form that, when clicked, will send the user an email with an activation code. How can I do that? When the user clicks the button, I would like it to fire off an email, however I do not want the user to be taken off of the form or to lose anything the entered. I suppose you would normally do this with JavaScript, but since I don't know that, I am looking for a PHP solution for now. Thanks.
-
Does this website not support BBCode? (It's a real PITA to use...) > ginerjm's reply wasn't about a static form with x predefined sets of input fields. > it was about entering one line item of data at a time, submitting the data (where it would be validated, > so you can correct any errors as they occur), and then presenting an empty set of input fields for the next data item. > the already entered data items would be shown with edit/delete buttons. Okay, I follow you/him now. The problem is that I don't want to do things piecemeal because that isn't how you'd do data entry in the real world. If this was for an order, at the top of the page you would enter customer and order information, and then below that on the same screen you would enter the order details for as long as necessary. (It would be insane to enter the customer and order info, click "Submit", and then get another page to enter the 1st item out of 100 items, click "Submit" and then get a another screen to enter the 2nd of 100 items and so on!!) With just PHP, you would either have to hard-code in A LOT of blank line item fields or do what you are are proposing, but neither really represents how the real world works, which leads me to think I need Javascript - which i don't know.
-
If I understand you, that is the design I am trying to avoid, i.e. a static order details form with a finite number of entry fields. Let's say this was for Walmart and not a restaurant - although the problem exists in either - and Customer A buys one banana. That is easy to design a subform for that, - I could just have 5-10 slots and I'm safe. But let's say that Customer B is buying a monthly order for their family of 15... There could be HUNDREDS of order details, and you just cannot program a static subform and *hope* there are enough slots - plus it would look sloppy. How hard is Javascript to learn? While I want to keep learning, what I do NOT want is to get stuck spending learning Javascript all summer long. If I accept this new project, I would need to turn around a working prototype in under a month, and then once I have someting that at least works, then I can more easily invest time to becoming a Javascript guru while I work on version 2.
-
Thanks for the reply. My background is with databases, so yes, I feel very comfortable with the data model part. It's just that I have been away from programming for several years, and my web programming skills are "light" (e.g. I don't know any of the fancy Javascript stuff). When I did used to do web development, it was mostly html pages/forms and serverside PHP, although I think I even forgot how to do that! As far as the database part, just doing this on the fly, I'd likely have this... CUSTOMER - id - and so on... ORDER - id - order_date - vendor - location - subtotal - discounts - taxes ORDER_DETAILS - id - order_id - product_id - unit_sale_price - quantity PRODUCT - id - name - description - unit_price - category - and so on... What I really need help with is figuring out how to build a control for the order details that acts like a spreadsheet where you can keep adding row after row as long as the customer is ordering more items.
-
I guess you answered one question, in that I need to handle this on the client side, right? As far as your comments above, I'm not sure I entirely understand what you mean, since I don't know Javascript. How difficult would it be to learn how to do all of this? I have a good idea in my head what I want, but am just unsure where to begin since this is on the web.
-
I want to build a webpage where an employee can key in an order, including the order details. Building an entry form for just the order is easy enough, because it is simply one webpage with a set number of fields. And when you need to enter in a new order, you simply load a new blank form. But the order details part seems trickier, because one order can have one-to-many order details, and so I need a subform that expands as more items are entered. For instance, let's say this is in a restaurant, and a large group of people walk in. There is no telling how many items they might order, but I would need a way to let the waiter keep adding items to their bill as long as necessary. On the web, I'm not sure even where to begin with this?!