Answers.Body: <p>Your best option is to do what you were doing previously. </p>
  
  <p>However, you will need to modify your customized template to extract details from the $billingDetailsFields array rather than the hard coded fields. I suspect the names are the same, so the translation should be relatively simple. You can use smarty debug to get more details on the contents of the array.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-12T14:20:06.377Z
Answers.LastActivityDate: 2015-05-12T14:20:06.377Z
Answers.UserDisplayName: Donald Lobo
Answers.Body: <p>I would think the previous billingblock.tpl could still be a basis. All the individual fields are still assigned to the template (as required), it's just that an array of fields to show is assigned too ... &amp; this is iterated through to show the fields.</p>
  
  <p>Your layout DOES look better :-)</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-21T19:19:28.510Z
Answers.Text: Agree it looks better except for one nitpick: putting state before country affects usability since they need to be selected in reverse order.
Answers.UserDisplayName: Coleman
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-21T21:33:00.767Z
Answers.Text: Could the change be done in css with no override?
Answers.UserDisplayName: eileen
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-22T01:10:02.340Z
Answers.Text: Definitely maybe.
Answers.UserDisplayName: Coleman
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-20T10:58:59.760Z
Answers.LastActivityDate: 2015-05-20T10:58:59.760Z
Answers.UserDisplayName: eileen
Body: <p>One of the first things we're asked to change in any installation is the billing block:</p>
  
  <p><img src="https://i.sstatic.net/gS9rq.png" alt="Billing fields"></p>
  
  <p>Nothing too fancy, just some changes to layout and labels, usually yielding something along the lines of </p>
  
  <p><img src="https://i.sstatic.net/FctPR.png" alt="Billing fields, revised layout"></p>
  
  <p>This was for a long time a simple matter of copying BillingBlock.tpl to create a custom template (customtemplates/CRM/Core/BillingBlock.tpl), <a href="http://wiki.civicrm.org/confluence/display/CRMDOC/Modifications+to+Contribution+Page+Templates" rel="noreferrer">as indicated in the wiki</a>. But the hard-coded <a href="https://issues.civicrm.org/jira/browse/CRM-15509" rel="noreferrer">billing fields were removed in 4.6</a>, and instead we they are printed out from the <code>$billingDetailsFields</code> array. </p>
  
  <p>While I can't fault this from a technical perspective, I do wonder what would be the best practice as far as manipulating the layout and order for this form goes now. In the override template, would we remove the <code>for</code> block and output the old fields one by one? Is there a place where these values can be changed in the db or even through the admin UI?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-05-09T17:35:37.103Z
Comments.Text: I wish civi would implement a feature like Display Suite so that when editing a profile one could add fields that cause other fields to appear inline.
Comments.UserDisplayName: frTommy
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-12-23T21:36:04.497Z
Comments.Text: Hi choster, did you manage to get your template working with civi 4.6? Do you mind to share please?
Comments.UserDisplayName: Tapash
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-12-23T21:39:31.300Z
Comments.Text: @Tapash I didn't. Our organization is dropping support for CiviCRM.
Comments.UserDisplayName: choster
Tags: <forms><custom-templates><contribution-page>
Title: Where to modify billing information form ≥ 4.6?
ThreadText: # Where to modify billing information form ≥ 4.6?
  
  (Asked by: username_0 on 2015-05-08)
  
  One of the first things we're asked to change in any installation is the billing block:
  
  ![Billing fields](https://i.sstatic.net/gS9rq.png)
  
  Nothing too fancy, just some changes to layout and labels, usually yielding something along the lines of
  
  ![Billing fields, revised layout](https://i.sstatic.net/FctPR.png)
  
  This was for a long time a simple matter of copying BillingBlock.tpl to create a custom template (customtemplates/CRM/Core/BillingBlock.tpl), [as indicated in the wiki](http://wiki.civicrm.org/confluence/display/CRMDOC/Modifications+to+Contribution+Page+Templates). But the hard-coded [billing fields were removed in 4.6](https://issues.civicrm.org/jira/browse/CRM-15509), and instead we they are printed out from the `$billingDetailsFields` array.
  
  While I can't fault this from a technical perspective, I do wonder what would be the best practice as far as manipulating the layout and order for this form goes now. In the override template, would we remove the `for` block and output the old fields one by one? Is there a place where these values can be changed in the db or even through the admin UI?
  
  **Tags:** forms, custom-templates, contribution-page
  
  > **Comments:**
  > **username_1**: I wish civi would implement a feature like Display Suite so that when editing a profile one could add fields that cause other fields to appear inline.  
  > **username_2**: Hi username_0, did you manage to get your template working with civi 4.6? Do you mind to share please?  
  > **username_0**: @username_2 I didn't. Our organization is dropping support for CiviCRM.  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_3 on 2015-05-12. Score: 3
  
  Your best option is to do what you were doing previously.
  
  However, you will need to modify your customized template to extract details from the $billingDetailsFields array rather than the hard coded fields. I suspect the names are the same, so the translation should be relatively simple. You can use smarty debug to get more details on the contents of the array.
  
  
  ---
  
  ### Answer by username_4 on 2015-05-20. Score: 2
  
  I would think the previous billingblock.tpl could still be a basis. All the individual fields are still assigned to the template (as required), it's just that an array of fields to show is assigned too ... & this is iterated through to show the fields.
  
  Your layout DOES look better :-)
  
  > **Comments:**
  > **username_5**: Agree it looks better except for one nitpick: putting state before country affects usability since they need to be selected in reverse order.  
  > **username_4**: Could the change be done in css with no override?  
  > **username_5**: Definitely maybe.  
  
  ---
  
  