Why Faceted Search Module shows results on a small width column?
Iulian81 - June 18, 2009 - 12:46
| Project: | Faceted Search |
| Version: | 6.x-1.0-beta2 |
| Component: | General |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Hi! After one or two weeks of searching I finally found a method to show the results in my video gallery how it should be. However the problem now is that I am using a 2 columns layout and the results will show in the first one, the one in the left side of the screen. So when I try to search something with Faceted Search module the results will show in the left part of screen but a part of them is not shown as I manually reduced the width of that column like 0.50 inch of the right part of that column. So the content there is invisible, instead there is just blank space.
I think there must be a way to modify the width of the results page... what do I must modify please?
#1
That looks like a CSS or theme issue. There can be a number of reasons for this happening. It is likely that people will only be able to help you by seeing your theme's code.
In any case, this is probably not an issue with the Faceted Search module itself.
#2
Yes... and why "more options" feature do not show anything but the full content of the site.. can this be still a CSS problem...??
#3
The "more options" link should take you to the search environment's base path.
#4
??? Then way it is called so? I believed it can refine the search results or something...
#5
The current search is preserved nonetheless, and the page corresponding to the base path allows you to refine your search either with keywords or facets. If you are seeing content rather than a search page, then something might be wrong in your setup. What URL do you get for the "more options" link, and what's your search environment's base path? Do they match?
#6
I've done it !!! Thanks! I renamed the page with 'more options' link with the same name as the search enviroment base path.
#7
#8
Automatically closed -- issue fixed for 2 weeks with no activity.