Quote:

Module have a versions log manager to store notes about releases. Since this module is intendeed to manage downloads items, forum section and bug reporting can be integrated trough other modules.

RMCommon will continue functioning with XOOPS 2.6, currently I'm working on a new version and all tests are working fine. However, now that XOOPS 2.6 will include many features taht already existing in rmcommon, I'm thinking about to port my modules to XOOPS 2.6 native code, but at this moment I can confirm that rmcommon modules will continue developing.

Quote:

D-Transport can manage two types of directories: Normal and Protected. Both locations are customizable.

Normal directory can be located inside public folder, and protected directory is recommended to put outside public folder.

D-Transport is a downloads modules for XOOPS.

Please post here your questions and I'll appreciate your feedback.

Download Module

You can see D-Transport in action here (Note that this is not a demo).

Requirements:

• XOOPS 2.5
• Common Utilities 2.1.8
• Lightbox Plugin for rmcommon (optional)

About images, I think that modules must avoid the use of language in images, I mean, images with text.

Buttons and other kind of components that require text, must be created with CSS and HTML for consistency, accessibility and standardization.

I think that all options are good, even translations driven by definitions, but my concern is about ease of use.

A system that allows to any person, even if does not know anything about programming, participate actively in translations will be better.

I think that by making the system more abstract will affect the future participation of other kind of contributors. I refer specifically to use of classes for translations.

I think that you know that I've used gettext for all my modules, and this desition is taken for two reasons:

1. Transparency for translate.
2. Ease of use.

What do I mean?

1. For me, to write modules using strings with:



Is more transparent than:



and then use this constant wherever I need. Using gettext simply I write a module and forget translations. Translations must be done using a gui editor easily.

Same thing about clases and other methods. This point bring me to point 2.

2. Is very easy for programmers write code and using strings directly and forget about translations. At the same time it's easier for translator simply to use the GUI editor and translate the strings without worrying about code.

Well, It is only an example. The main idea here is that regardless the choosen system, the important is the ease of use for those people that will use it.

IMHO, we need to think on every kind of contributor separately:

1. Translators
2. Developers
3. Designers
4. Final users
5. Other interested people.

I mean, wich tool is much convenient for every type of xoopser?

Sorry for my bad English.

Seems to be that xthemes is not active in file "XOOPS_CACHE_PATH/xoops_..._system_modules_active.php"

I've setup a demo site with a basic configuration for Inception:

http://xdemo.xoopsmexico.com

This result is obtained by following the instructions on readme file.

Please note that xThemes requires:

✔ Common Utilities
✔ AdvancedForms

And Inception Theme requires:

✔ xThemes
✔ MyWords

If you don't have this components installed, Inception will display those errors.

Please note that the log that you've posted previously does not contain any error related to Inception or xthemes. The blank page is generated because during the theme installation, the theme options could not be created.

This problem must be solved by uninstalling and reinstalling the theme with changes applied.

The attached screenshot shows the result of this process.

The problem occurs due to a wrong option line in the file "assemble/incpetion-options.php".

This bug has been corrected and the new file has been published.

Please donwload theme again:

http://www.xoopsmexico.net/downloads/download/29/

Or if you want to correct the error manually please follow next steps:

1. Open "assemble/inception-options.php" with a code editor.
2. Search line 71 and change \'Oswald\' to Oswald
3. Save file.
4. Go to xThemes themes manager and uninstall Inception (if inception is activated you need to activate another theme before).
5. Install inception theme again.

Now you can configure and use inception theme.

This solution is valid for both questions...

Please tell me if another error occurs.

Please, post here your questions about Inception Theme for xThemes 1.5.

Update:
Inception Demo:http://xdemo.xoopsmexico.com