Long tax text causes bad display of totals, and unable to change tax text in payment wizard

  • Profile Image
    Asked on November 19, 2016 at 10:10 AM

    I found that my tax text was too long and caused the presentation of shipping and tax to be fouled up in the rare case when tax was actually charged.  (i.e. when the State code = WI)

    I tried to reduce the length of the text from "5.5% Wisconsin Tax" to "Wisconsin Tax", but the Payment Wizard would not apply the change to my form.  I managed to do the change by returning to your old application with ?old, but this should be fixed.  I do not believe this problem is confined to any particular form. 

    I suppose too that the payment wizard should either prevent tax text that is so long that it screws up the totals presentation or it should not screw up the presentation.  See below for an example of what happens when the tax text is too long on my forms.

  • Profile Image
    Answered on November 19, 2016 at 03:43 PM

    I was able to replicate the issue. My suggestion is to increase the max-width payment total field. Here's the custom CSS code:

    .form-payment-subtotal, .form-payment-shipping, .form-payment-tax { 

    max-width: 300px !important; 

    .form-payment-divider { 

    max-width: 300px !important; 

    .form-payment-total { 

    max-width: 300px !important; 


    Here's the guide: How-to-Inject-Custom-CSS-Codes


    Hope that helps. If you need further assistance, contact us again. Thank you.


  • Profile Image
    Answered on November 20, 2016 at 02:10 AM

    Thank you for the CSS to alter the totals numbers presentation allowing for a longer tax text.  Useful.

    I still cannot change the tax text though.  I am unable to do a change and have it applied.  Is there some "save" button I am missing?
  • Profile Image
    Answered on November 20, 2016 at 09:30 AM

    Hi there,

    There seems to be a problem with saving the tax name. I need to double-check. However, it has to be separated from this thread to be addressed properly. Please see the thread here.