1
OK, here's the problem. In the default theme's style.css, all tables are asigned a width of 100%. This causes a critical problem with my CRITICAL module.
The developer of the module (Andromeda), Scott Matthews, described it like this to me:
"Unfortunately, it now becomes a bit more of a XOOPS issue. Let me explain:
The 'rows' of the Andromeda interface have width=100%, which means that they
fill up the horizontal space that they sit within (note that the
sub-components of those rows don't themselves have width=100%).
Previously, your XOOPS CSS was forcing *all* tables to width=100% and that,
I guess, included a table that Andromeda sits within. In other words,
Andromeda's explicit width=100% appears to sit within a width=100% (implied
via CSS) and so that filled up the space.
But, by forcing *all* tables to width=100%, Xoops' CSS also forces
Andromeda's sub-components to width=100%, and that messes up the display.
And when you disable Xoops' width=100%, the enclosing table loses it's
width=100%, and then when Andromeda fills up that space, it is no longer
filling up the horizontal space. (that make sense?)
So -- what you want to look for in XOOPS (or the XOOPS skin) is that
enclosing table, and provide it explicitly with width=100%
The problem is that when the XOOPS CSS sets *all* tables to width=100% it
breaks the layout of any element that doesn't want width=100%, if you see
what I mean..."
So, if I remove that line from the style.css (width: 100%), it causes problems with other modules and the general layout of this XOOPS theme...
Is there a fix that will work for both Andromeda (my critical module) and Xoops? Or, do I need to modify the way XOOPS uses a module? If so, where do I need to go to modify that?
Thanks!
fonte