Answers.Body: <p>This is an inconsistency in the CiviCRM interface that others have noticed before as well.</p>
  
  <p>This inconsistency does NOT exist for the "New Contribution" screen - because that screen has a "submit credit card contribution" link to bring you to the live entry screen.</p>
  
  <p>For kicks, I added <code>&amp;mode=live</code> to the "New Event Registration" URL - and it APPEARS to work.</p>
  
  <p>I would recommend:</p>
  
  <ul>
  <li>Append <code>&amp;mode=live</code> to the "New Event Registration" URL and confirm that it works correctly.</li>
  <li>If it does, it should be a simple matter to submit a patch to generate the "submit credit card registration" link to the appropriate template.</li>
  </ul>
  
  <p><a href="https://i.sstatic.net/6sc9A.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/6sc9A.png" alt="enter image description here"></a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-11-28T20:12:30.760Z
Answers.Text: I'll give this a try and let you know (and hopefully submit a patch)
Answers.UserDisplayName: ericG
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-12-13T01:04:58.597Z
Answers.Text: seems to work. Going to do this on a client's site and let them give it some real use testing. Thanks Jon
Answers.UserDisplayName: ericG
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-02T18:10:54.247Z
Answers.Text: Jon G, I've put this in place and it is working as expected
  
  /templates/CRM/Event/Form/ManageEvent/Tab.tpl
  
  line 35 
  changed from 
                      <li><a class="crm-event-participant" href="{crmURL p='civicrm/participant/add' q="reset=1&action=\
  add&context=standalone&eid=`$id`"}">{ts}Register Participant{/ts}</a></li>
  to
                      <li><a class="crm-event-participant" href="{crmURL p='civicrm/participant/add' q="reset=1&action=\
  add&context=standalone&eid=`$id`&mode=live"}">{ts}Register Participant{/ts}</a></li>
Answers.UserDisplayName: ericG
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-11-27T07:34:18.960Z
Answers.LastActivityDate: 2017-11-27T07:34:18.960Z
Answers.UserDisplayName: Jon G - Megaphone Tech
Answers.Body: <p>Another approach for them would be to use the public facing 'event registration' form, and when logged in they should see a "want to register as someone else".</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-11-15T19:10:22.603Z
Answers.LastActivityDate: 2017-11-15T19:10:22.603Z
Answers.UserDisplayName: petednz - fuzion
Body: <p>When staff (at a client org) go to register people for paid events there is a difference in the interface and the ability to actually take/process a payment depending on what path is taken to the registration form. </p>
  
  <p>If they start from the event admin page and click "Event Links" -> "Register Participant" they get a form that only allows for entering the last 4 digits of the credit card number (which of course is not enough data to actually charge the person the fee)
  <a href="https://i.sstatic.net/0UrKa.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/0UrKa.png" alt="enter image description here"></a>
  If they start at a contact record, click the Events tab and then Submit Credit Card Event Registration, once they select the event and the price from the price set, they get a form that allows for entering all necessary payment information which does allow them to charge the user the fee.
  <a href="https://i.sstatic.net/71kTL.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/71kTL.png" alt="enter image description here"></a>
  Why is there a difference? Is this a bug, or intentional for some reason? </p>
  
Tags: <civievent><payment>
Title: confusing interface for staff registering contacts for events
ThreadText: # confusing interface for staff registering contacts for events
  
  (Asked by: username_0 on 2017-11-11)
  
  When staff (at a client org) go to register people for paid events there is a difference in the interface and the ability to actually take/process a payment depending on what path is taken to the registration form.
  
  If they start from the event admin page and click "Event Links" -> "Register Participant" they get a form that only allows for entering the last 4 digits of the credit card number (which of course is not enough data to actually charge the person the fee)
  [![enter image description here](https://i.sstatic.net/0UrKa.png)](https://i.sstatic.net/0UrKa.png)
  If they start at a contact record, click the Events tab and then Submit Credit Card Event Registration, once they select the event and the price from the price set, they get a form that allows for entering all necessary payment information which does allow them to charge the user the fee.
  [![enter image description here](https://i.sstatic.net/71kTL.png)](https://i.sstatic.net/71kTL.png)
  Why is there a difference? Is this a bug, or intentional for some reason?
  
  **Tags:** civievent, payment
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2017-11-27. Score: 2 | Accepted answer
  
  This is an inconsistency in the CiviCRM interface that others have noticed before as well.
  
  This inconsistency does NOT exist for the "New Contribution" screen - because that screen has a "submit credit card contribution" link to bring you to the live entry screen.
  
  For kicks, I added `&mode=live` to the "New Event Registration" URL - and it APPEARS to work.
  
  I would recommend:
  
  * Append `&mode=live` to the "New Event Registration" URL and confirm that it works correctly.
  * If it does, it should be a simple matter to submit a patch to generate the "submit credit card registration" link to the appropriate template.
  
  [![enter image description here](https://i.sstatic.net/6sc9A.png)](https://i.sstatic.net/6sc9A.png)
  
  > **Comments:**
  > **username_0**: I'll give this a try and let you know (and hopefully submit a patch)  
  > **username_0**: seems to work. Going to do this on a client's site and let them give it some real use testing. Thanks Jon  
  > **username_0**: Jon G, I've put this in place and it is working as expected  /templates/CRM/Event/Form/ManageEvent/Tab.tpl  line 35  changed from                      <li><a class="crm-event-participant" href="{crmURL p='civicrm/participant/add' q="reset=1&action=\ add&context=standalone&eid=`$id`"}">{ts}Register Participant{/ts}</a></li> to                     <li><a class="crm-event-participant" href="{crmURL p='civicrm/participant/add' q="reset=1&action=\ add&context=standalone&eid=`$id`&mode=live"}">{ts}Register Participant{/ts}</a></li>  
  
  ---
  
  ### Answer by username_2 on 2017-11-15. Score: 1
  
  Another approach for them would be to use the public facing 'event registration' form, and when logged in they should see a "want to register as someone else".
  
  
  ---
  
  