OK, seems some things are missing in the CSS file for WOX.

It is now corrected, use reload to see.

thanks Ghia...that should be add to FAQ

You guys were pretty quick to attack the critic, but he is quite right on alot of it. Perhaps too shouty, but still.

For instance go from this page to try and find documentation on module building, after many many links, you get into the circular world of the wiki ... with no useful documentation.

Also try looking for info about putting a CSS sheet in just one module, not the whole theme, cannot find anything on that and been searching for months.

The point about un maintained modules is also true, why are they listed if they are not maintained?

In answer to the "so you wont be using XOOPS then" response, i personally have to use it here at work, but it is already decided that we are moving away (not my personal decision) and that is purely down to the difficulty in finding the documentation - My boss cannot find sufficient documentation to make him happy they can cope if i leave. Documentation is scattered so far and wide the only document we do use here is the Smarty documentation.

The forum is much improved but the code of XOOPS is not perfect and the project is not very well managed, sorry but it is true.

If these criticisms are hard to hear, then why have a "XOOPS.org feedback & suggestions " section on the forum.

While we are at it, is there a way to add CSS to only one module (since all modules include the same header)?

Quote:

You need to add scripts after the inclusion of header.php.
Look inside your module root files like, index.php, item.php, etc and use this:

Thank you!

hi'

Obregado Trabis

I believe there is another way.

With overrided templates (eg extgallery) :

www/
-- themes/
---- mytheme/
------ modules/
-------- extgallery/

... you can add this first line inside templates :


... and put extgallery.css in same folder than overrided template.


That works fine... if you do not use cache module

Quote:The modules are in general provided by third parties. At some point the enthousiasm for XOOPS or programming in general may fade, due a lot of reasons. That means the original developer doesn't maintain this module anymore.

This doesn't invalidate the quality of these modules. A lot of unmaintained modules are still in use and do everyday a fine job. So, there is no reason to unlist a module, just on the fact it is no longer maintained.

If problems arises and there are still users for the module, I'm sure someone will find a solution and provide a patch or new version. That's all what open source is about!

FYI: We are busy with trying to improve the repository, for having better listings.