This topic has 10 replies, 2 voices, and was last updated 2 years, 2 months ago ago by ryan@rrwebdesign.co.uk
Hi,
I am using gravity forms, I have added some CSS to the form but it’s still showing, I have used the same CSS on another site and it works fine so I am guessing its the theme that’s blocking it
Could you take a look
Hello,
We can’t open your site, unfortunately. Please check the Private content area.
Regards
website moved domains
Hello,
Please provide URL of page where you added the gravity forms, and let us know what exactly CSS not working. Screenshots will be appreciated.
You can use the Lightshot screenshot or Gyazo tool to make screenshots and share links here.
Regards
Every gravity form is used for totalling up add ons for the basket page
hide-offscreen wc-gforms-hide-from-email-and-admin
this is added to the customisation cost widget –
it should remove the total cost from the product page but doesn’t on your theme
Hello,
I can’t find the form on front end of your site, and you did not provide URL of page with it.
gravity forms plugin doesn’t come bundled with our theme. Please note that we do not give a guarantee for full theme compatibility with all existing 3rd party plugins and we do not provide support for such plugins.
Please spend some time and provide URLs/explanations to make the situation clear for me, in another case I will not be able to help you.
Regards
This is on every product page,
You will see customisation cost,
Customisations Cost
Price: £ 0.00
This should be hidden from the product page using the CSS provided,
Yes I know you don’t provide support but the issue seems to be with the theme as the CSS works on other themes
Add the next code in Theme Options > Theme custom CSS:
.single-product .hide-offscreen.wc-gforms-hide-from-email-and-admin {
display: none !important;
}
Regards
Perfect,
Thank you very much for your support
Tagged: basket page, gravity forms, troubleshooting, woocommerce, wordpress
The issue related to '‘gravity forms css not working on basket page’' has been successfully resolved, and the topic is now closed for further responses