Body: <p>I have set up a webform to take event registrations. A user can click through to the payment form without selecting an event and can click submit. This doesn't register them for the event, but I would like to stop this. Due to the way I have setup the form I cannot use required fields on event selection. The webform is pretty complex.</p>
  
  <p>Ideally, I would remove the submit button on the payment page unless the amount is greater than $0. Is this possible?</p>
  
  <p><a href="https://i.sstatic.net/kVZ0u.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/kVZ0u.png" alt="enter image description here"></a></p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-10-04T00:59:23.207Z
Comments.Text: I don't understand why you can not use required fields on Event selection?
Comments.UserDisplayName: KarinG - Semper IT
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-10-04T03:14:04.457Z
Comments.Text: A user can select to attend 1 or 2 days (using radio buttons).  I have set these up at different events within civievent. Users can also select to attend a dinner (checkbox). Users are not required to attend 1 or 2 days, or the dinner.
Comments.UserDisplayName: Ben
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-10-04T03:52:05.100Z
Comments.Text: How about making it one field with all events - checkboxes - and required (so they must check at least one checkbox but could do 1 day + dinner; or 2 days no dinner, etc?
Comments.UserDisplayName: KarinG - Semper IT
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-10-04T13:22:16.023Z
Comments.Text: Wouldn't that mean that a user could book 1 day and both days? That wouldn't be great.
Comments.UserDisplayName: Ben
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-10-04T17:16:30.340Z
Comments.Text: Not if you make your events day 1, day 2, dinner day 1, dinner day 2.
Comments.UserDisplayName: KarinG - Semper IT
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-10-10T11:22:03.273Z
Comments.Text: Thanks Karin. Good idea. I've already setup the webform with complex rules. But the next time I'll it up like this.
Comments.UserDisplayName: Ben
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-10-10T12:43:24.537Z
Comments.Text: You're welcome - glad you got things working!
Comments.UserDisplayName: KarinG - Semper IT
Tags: <webform-civicrm><payment>
Title: Webform - can accept zero payment
ThreadText: # Webform - can accept zero payment
  
  (Asked by: username_0 on 2018-10-03)
  
  I have set up a webform to take event registrations. A user can click through to the payment form without selecting an event and can click submit. This doesn't register them for the event, but I would like to stop this. Due to the way I have setup the form I cannot use required fields on event selection. The webform is pretty complex.
  
  Ideally, I would remove the submit button on the payment page unless the amount is greater than $0. Is this possible?
  
  [![enter image description here](https://i.sstatic.net/kVZ0u.png)](https://i.sstatic.net/kVZ0u.png)
  
  **Tags:** webform-civicrm, payment
  
  > **Comments:**
  > **username_1**: I don't understand why you can not use required fields on Event selection?  
  > **username_0**: A user can select to attend 1 or 2 days (using radio buttons).  I have set these up at different events within civievent. Users can also select to attend a dinner (checkbox). Users are not required to attend 1 or 2 days, or the dinner.  
  > **username_1**: How about making it one field with all events - checkboxes - and required (so they must check at least one checkbox but could do 1 day + dinner; or 2 days no dinner, etc?  
  > **username_0**: Wouldn't that mean that a user could book 1 day and both days? That wouldn't be great.  
  > **username_1**: Not if you make your events day 1, day 2, dinner day 1, dinner day 2.  
  > **username_0**: Thanks Karin. Good idea. I've already setup the webform with complex rules. But the next time I'll it up like this.  
  > **username_1**: You're welcome - glad you got things working!  
  
  ---
  
  ## 0 answers
  
  