Tagged: x
-
AuthorPosts
-
August 2, 2016 at 11:04 am #1113960
Greg WParticipantThere is a CSS conflict (overwrite) issue with X and Gravity Forms.
I simply need a balanced 2 column layout.
GF CSS Ready Classes: gf_left_half + gf_right_half.
Please see my dev page and assist with a fix.
http://lappetitopizza.com/shop/lappetito-2/appetizers/
(WooCommerce Single Product Page w/ Gravity Form)WordPress 4.5.3
X Theme 4.6.1
WooCommerce 2.6.4
Gravity Forms 1.9.17.6August 2, 2016 at 12:24 pm #1114077
RahulModeratorHey There,
Would you mind providing us with login credentials so we can take a closer look? To do this, you can make a post with the following info:
– Link to your site
– WordPress Admin username / passwordDon’t forget to select Set as private reply. This ensures your information is only visible to our staff.
Thanks.
August 2, 2016 at 2:12 pm #1114262
Greg WParticipantThis reply has been marked as private.August 2, 2016 at 6:13 pm #1114592
FriechModeratorHi There,
Thanks for the credentials and sorry you’re having this issue. Please follow this post: https://community.theme.co/forums/topic/gravity-forms-layout-css-issues/#post-1086168
Hope it helps, Cheers!
August 2, 2016 at 7:40 pm #1114639
Greg WParticipantDoesn’t help.
Right column doesn’t respond correctly.
Why did you ask for credentials and then send me a link?
I’m missing something in CSS and I can’t put my finger on it. Plz look again.
August 3, 2016 at 3:31 am #1115086
LelyModeratorHi There,
Please add this custom CSS:
body .gform_wrapper .top_label li.gfield.gf_left_half, body .gform_wrapper .top_label li.gfield.gf_right_half, body .gform_wrapper .top_label li.gfield.gf_left_third, body .gform_wrapper .top_label li.gfield.gf_middle_third, body .gform_wrapper .top_label li.gfield.gf_right_third { float: none !important; } body .gform_wrapper .top_label li.gfield.gf_left_half, body .gform_wrapper .top_label li.gfield.gf_left_third, body .gform_wrapper .top_label li.gfield.gf_middle_third { margin-right: initial; }Then remove the following from your current custom CSS:
body .gform_wrapper .top_label li.gfield.gf_left_half+.gform_footer, body .gform_wrapper .top_label li.gfield.gf_left_half+li.gfield, body .gform_wrapper .top_label li.gfield.gf_right_half+.gform_footer, body .gform_wrapper .top_label li.gfield.gf_right_half+li.gfield { float: left !important; margin-top: -1em !important; }Result:
August 3, 2016 at 12:40 pm #1115756
Greg WParticipantThis is the desired 2-column layout. I’m almost there… plz assist.
August 3, 2016 at 2:57 pm #1115977
LelyModeratorHello Greg,
If you will give us a screenshot on how you want it to display we would be happy to help and check further. But based on your current setup/structure that what we came up with.
Cheers!
August 3, 2016 at 3:09 pm #1115993
Greg WParticipantThis is the desired 2-column layout. I’m almost there… plz assist.
August 3, 2016 at 6:58 pm #1116248
RadModeratorHi Greg,
Hmm, that would be tricky. It’s not aligned because titles and prices belong to different items. Example,
<ul> <li>title</li> <li>price</li> <li>title</li> <li>price</li> <li>title</li> <li>price</li> </ul>Which means each title and prices has their own respective columns independent to the title. Plus, there are items that are hidden which mean the column counts is greatly affected.
I tried but it won’t align, how about using different form plugin? GF form structure is really different now, and it greatly affect the styling and class names.
Thanks!
August 6, 2016 at 5:01 pm #1120432
Greg WParticipantI guess GF time has come and gone… too much bullsh**t (css, ui, wpadmin warnings, etc).
Thanks Rad… for stopping the bleeding. I spent too much time (AGAIN) on custom page layouts w/ GF… it’s embarrassing, frustrating, and expensive.
Please note my vote for a future X partnership with a modern form provider.
August 7, 2016 at 6:15 am #1120810
ChristianModeratorYou’re welcome. And, thanks for your feedback.
-
AuthorPosts
- <script> jQuery(function($){ $("#no-reply-1113960 .bbp-template-notice, .bbp-no-topic .bbp-template-notice").removeClass('bbp-template-notice'); }); </script>
