So I made a sidebar.php file in my child theme folder. In the file, I only used the code you gave me – I didn’t repeat the Enfold code. It works – kind of… Basically the whole sidebar is gone, but I still wanted to show the Archive, which I’m assuming is “avia_dummy_widget(4);” According to your code, I understand it should show Archive, but I wonder why not?

I put the code in exactly as you gave it to me.

I will send site link next.

Yes it worked. Thanks!

It seems to have worked. Will give it some testing time. Thanks.

Ok but not sure what part to modify. I don’t want to mess anything up! Especially when the theme updates.

Is there a way to add to custom.css? I just want to change the part where it’s around ~860px wide.

Also, regarding my other post above, for 4-column footer, how can I make each column with less padding/marginin between each? When the browser is about ~860 wide (same as above) the columns display in a 2×2 (2 across, 2 rows) but want it to still be 4 columns across at the ~860 size. (Remember the ~860 is my guess since I always have the scrollbar and can’t tell exact pixels!)

Thanks

Oh, also, at around the 960 width – I’d like to make sure the footer (set at 4 columns) still shows the 4 columns in one row, rather than breaking them in a 2×2 grid (which it now does at the ~860 size).

Thanks

I actually already tried that. But it still overrides any specific field width settings in Formidable.

To “sort of” help (but still doesn’t solve the problem) I used:
#top .input-text, #top input[type=”text”], #top input[type=”input”], #top input[type=”password”], #top input[type=”email”], #top input[type=”number”], #top input[type=”url”], #top input[type=”tel”], #top input[type=”search”], #top textarea, #top select {
min-width: 0 !important;
}

It’s better, but that doesn’t solve the problem either.

The main issue is that in Formidable, you can specify whether a field is full-width, or you can choose your own width (i.e. 5 characters wide for a number field, etc) and it seems like the “width” in base or child CSS should really be cleared/deleted for Formidable to work properly. Just my guess.

It seems like I have to get into the base CSS and delete “width: 210px” since I can’t really null it out. But, where is the base CSS? (Sorry, I’m not a WordPress or CSS master, but still learning!) Even though I prefer not to touch ANY base code, I’d be curious to know if this would solve the problem.

By the way, I was wondering why did you guys choose 210px for fields?

Just curious – I bought Formidable since you guys recommended it, but has anyone else mentioned any issues between Enfold and Formidable??

Thanks for the help!

1. The width field settings in Formidable are being overridden by Enfold CSS:
/* #Forms
================================================== */
#top .input-text,
#top input[type=”text”],
#top input[type=”input”],
#top input[type=”password”],
#top input[type=”email”],
#top input[type=”number”],
#top input[type=”url”],
#top input[type=”tel”],
#top input[type=”search”],
#top textarea,
#top select {
…
width: 210px;
…
}

2. In Formidable, if I choose the field labels to be set to “none” (rather than top, right, left, etc…) then the “block” CSS parameter overrides it:
#top label {
display: block;
font-size: 12px;
font-weight: bold;
}

It seems if I get rid of the “#top” class in the Forms area of Enfold’s base CSS, then I should be ok? I’d rather not mess at all with the base CSS. But I need to solve this is my client’s site.