Answers.Body: <p>I think jQuery is the best way to achieve this at the moment, rather than trying to customise the template, or load a custom template for an individual event. Doing this in jQuery also keeps the logic separated out.</p>
  
  <p>If it's critical that the questions appear in this order, then you can use the introductory message and some creative CSS / JS to hide the entire booking form unless JS is enabled. This is the approach we sometimes take.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-24T01:01:54.473Z
Answers.Text: Thanks John. Have you ran into any performance issues using this approach? I am also considering the need for splitting fields into a 2-col layout.
Answers.UserDisplayName: Zachary
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-06-03T08:23:21.973Z
Answers.Text: Obviously it's not ideal ;] . We haven't hit any significant performance issues doing this. It can take an extra bit of time to load the page, but if it's critical for you that the questions are reordered then it's a reasonable trade-off I think.
Answers.UserDisplayName: John
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-06-04T04:07:12.687Z
Answers.Text: That's what I did. I also used some jquery code to make conditional fields. In the end, it was tedious and laborious but it worked well.
Answers.UserDisplayName: Zachary
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-23T09:51:54.537Z
Answers.LastActivityDate: 2016-05-23T09:51:54.537Z
Answers.UserDisplayName: John
Body: <p>Is there any way to edit a CiviEvent template where I can take price set fields and put them in groupings with specific profile fields (from included profile)?</p>
  
  <p>Reasoning - we are collecting data, which would go into Profile fields. We are also collecting Fees that correspond to those profile fields. </p>
  
  <p>I want it to be grouped like</p>
  
  <pre><code>Profile Field 1 a
  Profile Field 1 b
  Price Set field 1
  
  Profile field 2 a
  Profile Field 2 b
  Price Set field 2
  </code></pre>
  
  <p>Currently I am using jQuery .insertBefore and .prependTo to accomplish this, but it just seems ugly? </p>
  
  <p>Thank you! </p>
  
  <p>Sometimes questions should be right next to the Price Set option on the form - hence our need. </p>
  
Tags: <civievent><profile><templates>
Title: CiviEvent - How to Template Profile Fields and Price Set Questions In Custom Groups
ThreadText: # CiviEvent - How to Template Profile Fields and Price Set Questions In Custom Groups
  
  (Asked by: username_0 on 2016-05-21)
  
  Is there any way to edit a CiviEvent template where I can take price set fields and put them in groupings with specific profile fields (from included profile)?
  Reasoning - we are collecting data, which would go into Profile fields. We are also collecting Fees that correspond to those profile fields. 
  I want it to be grouped like
  Profile Field 1 a
  Profile Field 1 b
  Price Set field 1
  
  Profile field 2 a
  Profile Field 2 b
  Price Set field 2
  
  Currently I am using jQuery .insertBefore and .prependTo to accomplish this, but it just seems ugly? 
  Thank you! 
  Sometimes questions should be right next to the Price Set option on the form - hence our need.
  
  **Tags:** civievent, profile, templates
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2016-05-23. Score: 2 | Accepted answer
  
  I think jQuery is the best way to achieve this at the moment, rather than trying to customise the template, or load a custom template for an individual event. Doing this in jQuery also keeps the logic separated out.
  
  If it's critical that the questions appear in this order, then you can use the introductory message and some creative CSS / JS to hide the entire booking form unless JS is enabled. This is the approach we sometimes take.
  
  > **Comments:**
  > **username_0**: Thanks username_1. Have you ran into any performance issues using this approach? I am also considering the need for splitting fields into a 2-col layout.  
  > **username_1**: Obviously it's not ideal ;] . We haven't hit any significant performance issues doing this. It can take an extra bit of time to load the page, but if it's critical for you that the questions are reordered then it's a reasonable trade-off I think.  
  > **username_0**: That's what I did. I also used some jquery code to make conditional fields. In the end, it was tedious and laborious but it worked well.  
  
  ---
  
  