take a look at http://patriotguide.com/change/chapters/chapter_map_view
and http://www.patriotguide.com/change/chapters/chapters_search_node
you'll notice that those exposed form fields (both in block and inline) are way too long.. i think the reason you don't see the zipcode search inline is because the fields are too long..
how can this be remedied? Because i can't do exposed filter's currenty inline, the 2nd input box and apply button dissapears, even if i could deal with it being too long.
I'm not sure I see what you're referring to on these pages, unless you've changed it since making this post. The fields are surrounded by divs making them block items which is why they don't appear inline, and the length of the fields I'm seeing is 100px.
hi,
yeah I've been playing since I made the post...
I added 2 css's to the style.css that control those two select box's output, effectively limiting the size to 100px (i tried this originally before posting here.. but note since were using css compression now--you have to reset the cache)
code added to style.css:
#edit-distance-search-distance {
width: 100px;
display: inherit;
}
#edit-distance-postal-code {
width: 100px;
display: inherit;
}
--------------------
The code works fine, but what you'll notice is that the postal code search field and apply button go missing on this page:
http://www.patriotguide.com/change/chapters/chapters_search_node (if you examine with firebut you'll see display: none is in the css for some reason, causing it to be hidden on this page..
However, it does load fine on this page (which actually has more modules/elements):
http://www.patriotguide.com/change/chapters/chapter_map_view
So in summary, i've been able to fix the width using by manipulating the style.css, BUT I still have this problem where the apply and postal code input field go missing because of this "display: none" anomaly.
That display: none looks to be coming from the view or the module itself. It's not being pulled from a external stylesheet, but being generated and added directly into the input tag. It's not related to the theme and there's an issue about it on Drupal.org here.
Instead of display: inherit, the proposed solution on that thread is to override it with display:block or display:inline.




