Shape 5

Joomla Templates => Emma Smooth - Club => : vidamin November 16, 2009, 08:46:48 AM



: Menu & 3rd party component problem...
: vidamin November 16, 2009, 08:46:48 AM
Hello,

I'm experiencing a situation that my menus go below the content
of 3rd party imaginery components. I have contacted the vendor
of the 3rd party component developers and they gave the following
answer. I would need to know how to really get rid of this issue -
should I follow their advice ?

Regards,

Ville

**************************
3rd PARTY COMPANY ANSWERED :

It's really a common template problem...

All suckerfish (or other, like Supersucker, Transmenu etc.) menus should be included inside a container div to bypass such issues, mainly for compatibility with flash banners, javascript rotators which use relative positioning etc. But most template developers forget that.

So, here's what you can do.
You need to add a container div that wraps your menu. Open your template's index.php file and look for the place where the menu is called. It should be something like:

Code:

<div id="nav">***menu code here***</div>


So, add a "wrapper" div, like so:

Code:

<div id="menu-container"><div id="nav">***menu code here***</div></div>


And then in your template's CSS file (template_css.css), add the following code snippet:

Code:

#menu-container {position:relative;z-index:99;}

This should fix any issues.


: Re: Menu & 3rd party component problem...
: mikek November 16, 2009, 08:51:40 AM
Hello, the menu is already in a wrapper.

Please post a url to where the problem is occurring.


: Re: Menu & 3rd party component problem...
: vidamin November 24, 2009, 02:24:44 PM
The problem is occurring in the site :

www.vidamin.com

BTW, only when the panel is opened - in the panel I have
the 3rd party image display component...

Regards,

Ville


: Re: Menu & 3rd party component problem...
: mikek November 24, 2009, 02:57:46 PM
Hello, that module is not coded correctly, there are a lot of un-needed css position calls. If you add the following to the bottom of the template_css.css file it should correct it:

#fpss-container {
z-index:1;
}