Use of the $xoopsModule->getVar('dirname')
Don't hardcode your module dirname in your php files and templates. We can translate the module content, if you use this we can translate the module name too with a small change in the module's xoops_version.php (E.G. An Italian website doesn't needs a wordbook module, but it needs a 'dizionario' one)
Since XOOPS v. 2.0.10 a new smarty var is added in the core, <{$xoops_dirname}>, that return the module dirname so you can use this in your templates - if an absolute path is needed.

Peekay wrote:
In a future version of Xoops, do you think the XOOPS editor could be enhanced a little so that authors can highlight text and make it larger, bold, italic or coloured just by pressing a button? Like a WYSIWYG editor - but without the HTML.

Don't know how difficult that would be, but if it could be fixed so that inserted links, images, smilies etc. actually appear at the cursor position, the need for a fully blown WYSIWYG editor would be unnecessary in most modules, except where tables etc. are needed.

kenmcd wrote:
Quote:

banned wrote:
Xoops, as is, is not good enough.

Interesting.
Not good enough for what?
Not good enough to use now as a CMS?

Regards,

KM

jdseymour wrote:
Quote:

banned wrote:
- An Official chat for instant support and for help grow up (more and more) the community. Do I've to tell you that an 'official guy' have to live this as a second life?

The above is a part that I disagree with. I think the current method of support is sufficient. If we go to a chat support the solutions will be lost and not searchable, as well as making the solutions harder to enter into the faq.

Your other points are valid in my view. Maybe we should start a new thread of what XOOPS needs to compete. Because again, it is getting off the main topic.