PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

CSS Class Name for Pricing Field

  1. ehong33234
    Member

    I'm using multiple pricing calculation fields to come up with my pricing. However, I don't need all of the product pricing calculations to show up on the front end. If I put CSS Class Name "hidden-total" it doesn't show on the front end but the calculation also doesn't work.

    So... how can I create a CSS Class Name so that the field is transparent?

    The form id is 22 and field id is 31 if that helps.

    Thank you!

    Posted 7 years ago on Saturday February 9, 2013 | Permalink
  2. If you hide the field with CSS, it's the same way we hide fields which should be hidden by conditional logic, and the field won't be used in the calculation. You could reposition the text off screen using something like this:

    [css]
    body .gform_wrapper .hidden-total {
       position: absolute !important;
       top: -9999px !important;
       left: -9999px !important;
    }

    To make the text 'invisible' you have to make it the same color as the background it's on. If you do that, the space which would have been used to display it is still used, so that's not an optimal solution.

    Posted 7 years ago on Saturday February 9, 2013 | Permalink
  3. ehong33234
    Member

    Hey Chris, thanks for the answer. I went ahead and did the invisible method. Not optimal I know but it works for what I need it to do.

    }
    body .gform_wrapper li#field_24_21 {
        color: #fcfcfc;
    }
    .gform_wrapper span.ginput_product_price {
        color: #fcfcfc;
    }
    Posted 7 years ago on Sunday February 10, 2013 | Permalink
  4. Thank you for the update. I think you had another topic open for this as well. Can you update that one too and I will close it as well.

    Posted 7 years ago on Sunday February 10, 2013 | Permalink

This topic has been resolved and has been closed to new replies.