Does anyone know a fix for this....

As in....when you place Multimenu drop down navigation in your theme, you are also placing at the top of the template a CSS part that should not go there and instead should be placed at module header if possible...yet I am unsure how and have tried loads of things...as for it to work the Smarty variable is placed in the template for the menu number....

Yet then that after being completed through Smarty as it is set out to do, that whole bit of CSS in the template needs moving to the XOOPS module header...

is there away for Smarty to be told place something in template file into module header or does it need telling this in PHP?


any help would be much appreciated as we are nearly 100% W3C and then get this nasty red cross from Multimenu...

I'll probably looking for this in the next multiMenu version, but have no idea so far how to solve this.

It appears the only style that depends on the block settings is

width: <{$block.block_size}>px;

Making that an inline style should allow you to move the rest of the styles to an external stylesheet. The other classes that include the block variables do not have any dependence on the variable -

#dropmenudiv<{$block.mm}>

can be simplified to

#dropmenudiv

I'll be trying this myself -

The other challenge for validation will be to move the script to the header...

Good luck!

Thxz Tried it again, did try that before also my self, yet it appears not to place the desired style around where needed...really we need a way to make in Smarty this happen.....


<{$xoops_module_header = the style goes here }>


Been reading tons of Smarty guides on how to do this, yet still not found the correct way to do it yet, yet do believe it is possible just unsure on how....?


You can use <{capture}> I found something along the lines of adding a CSS file that way ....yet I couldn’t get it to work as the Smarty Idea had said...?

I've been playing with this, and I think I'm on the right track...

By editing multimenu.php and adding before the stylesheet link is placed in the head, like it should. You can also extend this to the script that needs to go in the head.

Victory is at hand!

p.s. you need to declare $xoopsTpl and $xoops_module_header as globals, too