Get XOOPS XOOPSXOOPS FAQFAQ ForumsForums NewsNews ThemesThemes ModulesModules

Search

Donate to XOOPS!

Please select an amount to donate


Do you want your username revealed with your donation?
Yes - List me as a Generous Donor
No - List my donation as from an Anonymous Donor


Local Support

Advertisement

XOOPS Code hosted on SourceForge

Cumulus Tag Cloud

admin Arabic banner block Christmas comments cumulus DayDawn dhsoft e-Commerce E-Learning Git Google GUI hacks instant-zero jQuery module mygalleries news Nordic Olédrion oxygen PageRank PHP rmcommon security SEO simple-XOOPS Smarty sport tag Theme tutorial wiki WOX xoops XoopsEngine ZendFramework

New Users

Registering user

# 133970

compuedobaja

Welcome to XOOPS!
[Main Page]

1.2. Modules

From XOOPS Web Application System

Main Page | Recent changes | View source | Page history | Switch to MediaWiki mode

Printable version | Disclaimers | Privacy policy
Category: Operation Manual

العربية * * Deutsch * * sc * * Español * * Français * * Italiano * * Nederlands * * Polski * * Português do Brasil * * 中文 * *


Operation Manual Index

As mentioned before, modules are the software constructs that, taking advantage of the infrastructure that XOOPS provides, let the webmaster offer the site’s users dynamic or static content generated using a Web interface that more often then not is very easy to use.


Part of the power of XOOPS resides in the way modules are managed. The webmaster can easily install, uninstall, activate or deactivate any specific modules (except the System module, for obvious reasons). It’s also possible to rename modules, and to determine the order in which they will appear to the end user in the site’s menu


TIP:

–if you want them to appear at all–,

  • because you can also provide hidden functionality, defining active modules that have no visible presence to the casual user. For instance, you could install a News module, edit its xoops_version.php file so that the installation directory is something difficult to guess (let’s say: gaeqhweas), and then define this modules as not visible by defining its menu position as zero (“0”). Then you could send private messages to an elite bunch of your users and tell them to access that directory typing the address in the URL field, something like http://www.yoursite.com/gaeqhweas. They could access that News module as a regular News module.


Up to now, XOOPS has been distributed including a set of “official” or “core” modules. Soon there will be no “officialy” modules, that is, XOOPS will be offered as a framework or operating core, and XOOPS webmasters will decide what modules to install. There will be, on the other hand, a ReviewingProcess that will serve to identify modules built by xoopsers and that operate correctly under XOOPS Frameworks. These modules will be marked with an “approved” seal and as such will have the XOOPS core team endorsement as secure to use in a XOOPS Web site.


MD-Tutorials * ModuleWriters * ReviewingProcess * Frameworks * modules

Retrieved from "http://xoops.org/modules/mediawiki/index.php/1.2._Modules"

This page has been accessed 6,847 times. This page was last modified 01:04, 4 December 2007. Content is available under XOOPS Web Application System.