-
- Contenido provides autoloading for source files of classes/interfaces which are
-delivered by a Contenido package.
-The main goal of autoloading is to reduce the list of needed includes which is usually
-at the beginning of scripts. By implementing a autoloader, the PHP engine has the
-possibility to load the file while trying to use a class/interface.
The Contenido autoloader will be initialized during the application startup process. -The autoloading solution in Contenido uses the class map strategy. It uses a generated -class map configuration file, which is available inside contenido/includes/ folder.
-contenido/includes/config.autoloader.php-
Each class type name is pointed to a file which contains the implementation of the
-required class type. By trying to use a class type, the autoloader will load the
-needed file if not done before.
-
-Example:
-Usually you have to ensure that a class file is already loaded by using include/require
-statements or by using Contenido's cInclude function:
-cInclude('classes', 'class.article.php');
-$oArt = new Article();
-
-
-With a autoloader the manually loading is not required anymore.
--$oArt = new Article(); --
At the moment all available classes/interfaces inside following directories -of a Contenido installation:
--contenido/classes/ --
NOTE:
-The autoloader doesn't handle loading of files which don't belong to the Contenido package.
-This means, additional added files (e. g. user defined classes/libraries) aren't
-automatically available for the autoloader. Read the section below, if you want to
-provide autoloading of additional class type files.
Don't edit the class map configuration manually, the next update could overwrite -your changes. The autoloading is extendable by adding a additional user defined class map -file inside the "includes" folder, which could contain further class map settings or -could overwrite settings of main class map file.
-contenido/includes/config.autoloader.local.php-
This file will not be overwritten during a update.
-
-The content of the user defined file should have the following structure:
-<?php
-return array(
- '{classname_1}' => '{path_to_classfile_1}',
- '{classname_2}' => '{path_to_classfile_2}',
- '{classname_3}' => '{path_to_classfile_3}',
-);
-
-Where {classname_X} is the name of the class/interface and {path_to_classfile_X} is the -path (from Contenido installation folder) to the file which contains the implementation of the class/interface.
- -
Example:
-Let's assume that Contenido is installed in folder /var/www/ which contains a
-additional library "myLib" (full path: /var/www/myLib/) with a class "myFoobarClass"
-in file "class.myfoobarclass.php" (full path: /var/www/myLib/class.myfoobarclass.php).
-Then the user defined class map file should contain a entry for this like:
-<?php -return array( - ... - 'myFoobarClass' => 'myLib/class.myfoobarclass.php', - ... -); --
If you don't want to maintain the user defined class map configuration manually, then
-you may let a copy of the command line script (which is adapted to your requirements)
-contenido/tools/create_autoloader_cfg.php
-to do the job.
-
-Do following steps to achieve this:
$context->pathsToParse = array( - $context->contenidoInstallPath . '/my_path/', - $context->contenidoInstallPath . '/my_other_path/', -); --
// class type finder options
-$context->options = array(
- // list of directories which are to exclude from parsing (case insensitive)
- 'excludeDirs' => array('.svn'),
- // list of files which are to exclude from parsing (case insensitive), also possible regex patterns like /^~*.\.php$/
- 'excludeFiles' => array(),
- // list of file extensions to parse (case insensitive)
- 'extensionsToParse' => '.php',
- 'enableDebug' => false,
-);
-
- By using the Contenido autoloader it's possible to extend/overwrite Contenido core classes - (except classes inside conlib directory) without changing the core files.
-Let's assume, you want to use your own Template class in Modules, but everything should
- still be downwards compatible.
-
-Do following steps to achieve this:
-NOTE:
-There is one main disadvantage by using this way of extending the Contenido core.
-Each time after an update of your Contenido installation it's strongly recommend
-to check your user defined implementations against changes in original Contenido
-core files and, if applicable, to adapt your files to those changes.
- 
| Area/Type | -Property | -Value (Description) | -Applies to | -
| backend | -currentlogintime | -Date and Time when this session has been started (automatically set by the backend) | -Users | -
| backend | -lastlogintime | -Date and Time when the last session was started (automatically set by the backend) | -Users | -
| backend | -preferred_idclient | -ID of the client which should be selected after backend login | -System, Clients, Groups, Users | -
| backend | -leftframewidth | -Defines the width of the left frame. Standard - value is 250. | -System, Clients, Group, Users | -
| backend | -small-navigation | -(true, false): If true, a small navigation is shown. Default: false | -System, Clients, Groups, Users | -
| articles | -show-new-window-checkbox | -- (true, false): If true, show "new window" checkbox for redirects in article properties. - Note: If a redirect has been specified, the page is redirected to the new URL using an html - page header. As header redirects can't open new windows, this setting is only useful, - if a navigation module is used, which mentions the "open in new window" setting and - adds a ′target="_blank"′ to the link, if necessary. Default: false - | -System, Clients, Groups, Users | -
| cms_img | -directory-height | -Height of the directory lister in rows, default 5 | -System, Groups, Users | -
| cms_img | -directory-width | -Width of the directory lister in pixels, default 300 | -System, Groups, Users | -
| cms_img | -file-height | -Height of the file lister in rows, default 5 | -System, Groups, Users | -
| cms_img | -file-width | -Width of the file lister in pixels, default 300 | -System, Groups, Users | -
| cms_img | -description-height | -Height of the description box in rows, default 5 | -System, Groups, Users | -
| cms_img | -description-width | -Width of the description box in characters, default 70 | -System, Groups, Users | -
| cms_img | -preview-height | -Height of the preview area in pixels, default 400 | -System, Groups, Users | -
| cms_img | -preview-width | -Width of the preview window in pixels, default 600 | -System, Groups, Users | -
| imagemagick | -available | -Set "1" if ImageMagick is available on your server to receive best results when resizing images | -System, Groups, Users | -
| modules | -java-edit | -Enable the java module editor | -System, Groups, Users | -
| modules | -edit-with-tabs | -(true, false) If set to "true" you can use the <tab> key to insert tabs in the input and output code areas (IE 6/7, FF 1.5/2). Default: false | -System, Clients, Groups, Users | -
| modules | -disable-history | -(true, false) If true, don't use the module history. Default: false | -System, Clients, Groups, Users | -
| modules | -storeasfiles | -Defines if Contenido should store modules as text files. THIS IS HIGHLY EXPERIMENTAL, ONLY USE IF YOU KNOW WHAT YOU ARE DOING! Default off. | -System | -
| modules | -loadfromfiles | -Defines if Contenido should load modules as text files. THIS IS HIGHLY EXPERIMENTAL, ONLY USE IF YOU KNOW WHAT YOU ARE DOING! Default off. | -System | -
| modules | -force-menu-check | -If system/modulecheck is enabled, force module check while module list will be generated (instead of using database information). Default $quot;false$quot;. | -System, Clients, Groups, Users | -
| system | -modulecheck | -if set to "false" (as string), modules aren't tested for syntax errors (needed for older PHP versions) | -System | -
| system | -languageorder | -If set to "name", languages in the drop-down (top right) will be shown ordered by name, - if not specified or set to something else, languages will be ordered by language id (default) | -System, Clients, Groups, Users | -
| system | -multiassign | -If false, don't allow multi assignments for articles. | -System, Clients | -
| layout | -htmlvalidator | -(true, false): If true, use the HTML validator. Default: true | -System, Groups, Users | -
| newsletter | -option-cronjob-available | -(true, false): If true, then a newsletter - option can be activated to send the newsletter using cron jobs. Note, that - this option should only be used, if a real cron service is available - (do not use the Contenido built-in pseudo cron service). Additionally, - note, that there is a send job file available in the contenido/cronjobs - folder, but it hasn't been added to the cron job list - just generate - a real cron job on your server running this file. Default: false | -System, Clients, Users | -
| newsletter | -disable-rn-replacement | -(true, false): If true, "\r\n" will not - be replaced by just "\n" to prevent double lines in mails. This may be - a good idea on Windows-Servers. Usually, use the default setting. Default: false | -System | -
| newsletter | -remove_base_tag | -(true, false): Usually every article contains a "e;base href"e;
- tag. This is nice, as all links, URLs and sources can be relative and we can
- move the client around, as we like. But there is a problem with anchors: They - only work, if the link to the anchor (on the same page) contains the URL of the - current article (e.g. "front_content.php?idart=77#MyAnchor"). This works - fine, if you are on the website, but not, if you use anchors in html newsletter - articles (as the mail doesn't has this URL). If you like to use anchors in html - newsletters, set this setting to "true" and check everything twice, as - also all URLs and source path will be changed by Contenido code. Default: false |
- Client | -
| newsletter | -html_username html_password |
- If the frontend (the website) is proteced - using .htaccess (username/password), you have to specify html_username and - html_password to be able to send html newsletters (as html newsletters - are just usual articles). Default: empty or not specified | -Client | -
| frontendusers | -pluginsearch | -(true, false): If true, the frontend users - menu also searches trough plugins. However, searching trough plugins - have a huge performance inpact on the list. If you have alot of frontend - users, set this to false to disable this function. Default: true | -System, Clients, Users | -
| frontendusers | -pluginsearch_valid_plugins | -If pluginsearch is set to true, you can hereby - limit the plugins to search over. This property must be a comma-separated list - (no whitespaces) of all plugins that should be used for pluginsearch. - All other plugins will be skipped to improve performance. | -System, Clients, Users | -
| generator | -xhtml | -(true, false): Defines if the tags generated by Contenido - should be XHTML compliant. WARNING: This does not alter the HTML code - in your layouts and modules! You have to revise your modules and layouts - to be XHTML compliant. Default: false. | -System, Clients | -
| generator | -basehref | -(true, false): Defines if Contenido should automatically - insert a base href tag. Default: true. | -System, Clients | -
| edit_area | -activated | -(true, false): Defines if syntax highlighting editor is used in backend for modul, js, css and html code Default: true. | -System, Clients, Groups, Users | -
| system | -insight_editing_activated | -(true, false): Defines if insight editing is used in article editor | -System, Clients, Groups, Users | -
| maintenance | -mode | -(disabled, enabled): In maintenance mode, only sysadmins are allowed to login into contenido backend. Default: disabled | -System | -
| pw_request | -enable | -(true, false): Property definies if contanido is allowed to generate new passwords for backenduser and submits them via mail. Default: true | -System | -
| system | -mail_host | -Host which is used for sending system mails (PW-Request). Default: localhost | -System | -
| system | -mail_sender | -Sender mail-adress of Contenido Systemmails. (PW-Request). Default: info@contenido.org | -System | -
| system | -mail_sender_name | -Sender name of Contenido Systemmails. (PW-Request). Default: Contenido Backend | -System | -
| update | -check | -(true, false): Update checker notifies sysadmins, if there are new updates for contenido on contenido org. Default: false | -System | -
| update | -news_feed | -(true, false): Update RSS News notifies sysadmins, about news on contenido org and security issues. Default: false | -System | -
| tinymce | -content_css | -Defines the stylesheet to - include within tinyMCE (<= V4.6.15: wysiwyg/tinymce-stylesheet-file). | -System, Groups, Users | -
| tinymce | -theme_advanced_styles | -Defines the available styles in the tinyMCE style - dropdown (<= V4.6.15: wysiwyg/tinymce-styles) | -System, Groups, Users | -
| tinymce | -width | -Defines the width of tinyMCE (<= V4.6.15: wysiwyg/tinymce-width, - default 100%) | -System, Groups, Users | -
| tinymce | -height | -Defines the height if tinyMCE (<= V4.6.15: wysiwyg/tinymce-height, - default 480px) | -System, Groups, Users | -
| tinymce | -contenido_height_html | -Overrides the tinyMCE height when editing - the CMS_HTML element (<= V4.6.15: wysiwyg/tinymce-height-html) - | -System, Groups, Users | -
| tinymce | -contenido_height_head | -Overrides the tinyMCE height when editing - the CMS_HTMLHEAD element (<= V4.6.15: wysiwyg/tinymce-height-head) | -System, Groups, Users | -
| tinymce | -contenido_gzip | -If set to "true" use gzip compression. - The server has to provide the compression method. Default: "false" | -System, Groups, Users | -
| tinymce | -contenido_toolbar_mode | -Defines the tinyMCE toolbar mode (default - "full"). Available choices: full, simple, mini, custom (<= V4.6.15: wysiwyg/tinymce-toolbar-mode) | -System, Groups, Users | -
| tinymce | -theme_advanced_buttons1 - theme_advanced_buttons2 - theme_advanced_buttons3 |
- Defines which items should be shown on - the first/second/third toolbar. Please have a look at the tinyMCE documentation to - find out which items you can use (<= V4.6.15: wysiwyg/tinymce-toolbar1/2/3). - Only used if the toolbar mode is "custom". | -System, Groups, Users | -
| tinymce | -plugins | -Defines which plugins should be loaded - (<= V4.6.15: wysiwyg/tinymce-plugins). Only used if the toolbar mode is "custom". | -System, Groups, Users | -
| tinymce | -valid_elements | -Defines which elements are allowed. See
- tinyMCE documentation for more information (<= V4.6.15: wysiwyg/tinymce-valid-elements). - Default: +a[name|href|target|title],strong/b[class],em/i[class],strike[class],u[class], - p[dir|class|align],ol,ul,li,br,img[class|src|border=0|alt|title|hspace|vspace|width|height|align], - sub,sup,blockquote[dir|style],table[border=0|cellspacing|cellpadding|width|height|class|align], - tr[class|rowspan|width|height|align|valign],td[dir|class|colspan|rowspan|width|height|align|valign], - div[dir|class|align],span[class|align],pre[class|align],address[class|align],h1[dir|class|align], - h2[dir|class|align],h3[dir|class|align],h4[dir|class|align],h5[dir|class|align],h6[dir|class|align],hr |
- System, Groups, Users | -
| tinymce | -extended_valid_elements | -Defined which elements are allowed. These
- elements are added to valid_elements (<= V4.6.15: wysiwyg/tinymce-extended-valid-elements). - Default: form[name|action|method],textarea[name|style|cols|rows],input[type|name|value|style|onclick], - a[name|href|target|title|onclick],img[class|src|border=0|alt|title|hspace|vspace|width|height|align|onmouseover|onmouseout|name], - hr[class|width|size|noshade],font[face|size|color|style],span[class|align|style] |
- System, Groups, Users | -
| tinymce | -contenido_background_color | -Defines the tinyMCE background color (any - valid CSS color value can be used). If you use an HTML hex color code, - also include the # sign before the color (e.g. #ffffff). Default is - "white" (<= V4.6.15: wysiwyg/tinymce-backgroundcolor). | -System, Groups, Users | -
| tinymce | -convert_urls | -(true, false): Defines, if URLs will be converted (e.g. to relative URLs) - at all. Please note, that URLs should be converted (e.g. for the time you may have to - change the domain or server path). Default: true (<= V4.6.15: wysiwyg/tinymce-convert-urls) | -System, Clients, Groups, Users | -
| tinymce | -relative_urls | -(true, false): If convert_urls is true, then - this setting specifies, if URLs will be converted to relative or absolute URLs. - Please note, that relative URLs should be used (e.g. for the time you may have to - change the domain or server path). Default: true (<= V4.6.15: wysiwyg/tinymce-relative-urls) | -System, Clients, Groups, Users | -
| tinymce | -contenido_lists | -If specified, adds dropdown lists with links
- for all articles (Insert Link popup window), images (Insert Image popup window) and/or
- all media/flash files (Insert Media/Flash popup window). Valid values are: link, image,
- media, flash.
- Values have to be separated by a comma, e.g. "link,image". - Do not specify, if you have a lot of articles, images and/or media files - (<= V4.6.15: wysiwyg/tinymce-lists). - |
- System, Groups, Users | -
| style_editor | -wrap | -{on, off} Default off. Defines the wrap attribute of the textarea to edit the CSS file. In case of 'on' the lines will be wraped. | -System, Clients, Users | -
| script_editor | -wrap | -{on, off} Default off. Defines the wrap attribute of the textarea to edit the JS file. | -System, Clients, Users | -
| html_editor | -wrap | -{on, off} Default off. Defines the wrap attribute of the textarea to edit the HTML file. | -System, Clients, Users | -
- - \ No newline at end of file diff --git a/docs/techref/backend/backend.localconfig.html b/docs/techref/backend/backend.localconfig.html deleted file mode 100644 index 39db568..0000000 --- a/docs/techref/backend/backend.localconfig.html +++ /dev/null @@ -1,60 +0,0 @@ - - - - -
-
- function active_directory_auth ($username, $password)-
{
global $cfg;
if ($cfg['ldap']['server'] != "")
{
$ad = ldap_connect($cfg['ldap']['server']);
if ($ad)
{
ldap_set_option($ad, LDAP_OPT_PROTOCOL_VERSION, 3);
$bd = ldap_bind($ad, $username . $cfg['ldap']['suffix'], $password);
if (!$bd)
{
return false;
}
}
}
return true;
}
register_auth_handler("active_directory_auth");
-By registering the function, the login mechanism knows that it should
-call "active_directory_auth" for certain users. Finally, you have to
-include your new handler file (the recommended place is
-config.local.php).
- Backend customizing-
|
-
| Area/Type | -Property | -Value (Description) | -Applies to | -
| login_error_page | -idcatart | -If specified, then a user who is logged out or tries to open a protected - category if not logged in will get redirected to the page specified by idcatart. This setting overrides other - login_error_page settings. | -Clients, System | -
| login_error_page | -idcat | -If specified, then a user who is logged out or tries to open a protected - category if not logged in will get redirected to the category specified by idcat. You can specify idcat - and/or idart (see next setting). | -Clients, System | -
| login_error_page | -idart | -If specified, then a user who is logged out or tries to open a protected - category if not logged in will get redirected to the article specified by idart. You can specify idcat - and/or idart (see previous setting). | -System, Clients | -
- - diff --git a/docs/techref/frontend/frontend.permissions.html b/docs/techref/frontend/frontend.permissions.html deleted file mode 100644 index bf2f93a..0000000 --- a/docs/techref/frontend/frontend.permissions.html +++ /dev/null @@ -1,118 +0,0 @@ - - - - -
- Frontend Permissions
- |
-
| Author | -Timo A. Hummel | -
| Created | -20th May 2005 | -
| Audience - |
- Site Integrators, Module Developers - |
-
| Applies to - |
- Contenido 4.6 or later - |
-
Contenido 4.6 introduces so-called frontend users. These users are splitted - apart the regular backend users, because they should be seen and handled completely - different as backend users. Frontend users themselves can't have permissions, - all permissions are assigned to groups.
-Frontend objects and permissions are designed to be very generic. Basically, -the developer has to define:
-- A class which defines how the object works
- - Checks to make the permissions effective
-
-Step by Step manual:
1. Think of a name for the object you're going to use. The name should be
- lowercase. In this example, we're going to use "object".
- 2. If the folder "frontendlogic" in the plugins directory doesn't exist, create
- it
- 3. Create a folder with the object name you're going to use in the folder "frontendlogic"
- 4. Create a file with the objectname and ".php" as extension. In our example,
- you would have the path "plugins/frontendlogic/object/object.php".
- 5. Extend the class FrontendLogic. Your class name must have the name "frontendlogic_"
- plus your object name, in our example it would be "frontendlogic_object".
- 6. Override the methods getFriendlyName(), listActions() and listItems().
-You can find descriptions for these methods in the FrontendLogic phpDoc.
-7. Define the object name in the variable $cfg['plugins']['frontendlogic'], e.g.
-$cfg['plugins']['frontendlogic'][] = "object". You should place this in the file
-config.local.php, so your changes are preserved during updates.
Test your object:
-Login into Contenido. Go to the frontend groups, create a new group (or edit - an existing). In the subnavigation beneath "Overview", you should see your - object name which you defined in the method "getFriendlyName()". Click on it. - In the list, you should see all actions you defined, and all items you return. - Your administrators can now start to apply permissions to the items.
-Checking permissions:
-This is actually pretty easy. Create a new FrontendPermissionCollection-Item - and use the method checkPerm() to query if a specific permission is set:
-$myPermissionCheck = new FrontendPermissionCollection;
- var_dump(
-$myPermissionCheck->checkPerm(2, "object", "permissionname", "itemid"));
If you want to check for a global right, replace "itemid" with "__GLOBAL__".
-
- Protected frontend categories
- |
-
| Author | -Timo A. Hummel | -
| Created | -20th May 2005 | -
| Audience - |
- Site Integrators, Module Developers - |
-
| Applies to - |
- Contenido 4.6 or later - |
-
Download the plugin "Frontend Category Permissions" from the Contenido website. - Extract the archive to your plugins directory. Open (or create) the file config.plugin.php in the directory contenido/plugins/chains/includes/ - and add the necessary includes and chain entries (see below). Afterwards, open - the file config.local.php in your contenido/includes directory (create the - file - if it - doesn't exist) and add the following line at the end:
-$cfg['plugins']['frontendlogic'][] -= "category";
-Example config.plugin.php:
-<?php
- global $_cecRegistry;
- cInclude("plugins", "chains/includes/include.chain.frontend.cat_backendaccess.php");
-cInclude("plugins", "chains/includes/include.chain.frontend.cat_access.php");
$_cecRegistry->addChainFunction("Contenido.Frontend.CategoryAccess", "cecFrontendCategoryAccess");
- $_cecRegistry->addChainFunction("Contenido.Frontend.CategoryAccess", "cecFrontendCategoryAccess_Backend");
- ?>
The chain Contenido.Frontend.CategoryAccess is - called everytime a protected category is accessed. If the chain functions return - true, access is granted. The function cecFrontendCategoryAccess validates - frontend users and their permissions, and cecFrontendCategoryAccess_Backend does - the same for the backend user counterparts. If you wish to disable backend - users for access frontend categories, remove the line which contains cecFrontendCategoryAccess_Backend. - You can also define chains for more custom checks, please refer to the chains - documentation for more information.
-
- Frontend Session Information
- |
-
| Author | -Timo A. Hummel | -
| Created | -20th October 2003 | -
| Audience - |
- Module Developers - |
-
| Applies to - |
- Contenido 4.4 or later - |
-
class Contenido_Frontend_Session extends Session {
var $classname = "Contenido_Frontend_Session";
var $cookiename = "sid"; ## defaults to classname
var $magic = "Phillipip"; ## ID seed
var $mode = "cookie"; ## We propagate session IDs with cookies
var $fallback_mode = "cookie";
var $lifetime = 0; ## 0 = do session cookies, else minutes
var $that_class = "Contenido_CT_Sql"; ## name of data storage container
var $gc_probability = 5;
-function Contenido_Frontend_Session ()-The important variables are "$mode" and "$fallback_mode". Both of these -can either be "get" or "cookie". Remember that if you set "get", you -have to rewrite most of your modules (in fact, each module which -generates or display links).
{
global $load_lang, $load_client;
$this->cookiename = "sid_".$load_client."_".$load_lang;
}
}
- Creating a frontend login module using Contenido-
|
-
echo $auth->auth["uid"];-This statement shows the current logged in user. For anonymous sessions -(i.e. nobody is logged in), the "uid" is always "nobody". To test the -login, create a new user in Contenido's Backend, then call the frontend -like this:
front_content.php?username=<youruser>&password=<yourpassword>-If previously the test statement returned "nobody", it should now -display your user id.
front_content.php?logout=true
-Type: login_error_page -Name: idcatart -Value: <Specify the idcatart of the article containing the login form>-
-Type: login_error_page -Name: idcat -Value: <Specify the idcat of the category containing the article with the login form>-
-Type: login_error_page -Name: idart -Value: <Specify the idart of the article containing the login form>-
$myUsers = new Users; // User Collection-
$myUser = new User; // Single user
$ret = $myUsers->create("nameofuser");
/* Note the three equal signs: This checks for the boolean type */
if ($ret === false)
{
/* User already exists */
die("User already exists");
} else {
/* User was successfully created, now we can set the password */
$user->loadUserByUserID($ret);
$user->setField("password", md5("theuserspassword"));
}
- Writing modules for use with Contenido
- |
-
| Author | -Timo A. Hummel | -
| Created | -3rd November 2003 | -
| Audience - |
- Module Developers - |
-
| Applies to - |
- Contenido 4.4 or later - |
-
echo " <table>-CMS_VAR[x] is the variable (which is set using "magic" :)) to "receive" -the desired value, and CMS_VALUE[x] is the current value. The same -story goes for the output area:
<tr>
<td>Test</td>
<td><input type=\"text\" name=\"CMS_VAR[1]\" value=\"CMS_VALUE[1]\"></td>
</tr>
</table>";
echo "CMS_VALUE[1]";
-To avoid problems, you should always take care of the following things:$foo = "CMS_VALUE[1]";-
if ($foo == 1)
{
echo "Worked";
}
| DB_Contenido - |
- The well-known PHPLib DB-Object.
- - -Example: - -$mydb = new DB_Contenido; -$mydb->query("SELECT * FROM test"); - -Reference: -See -http://www.sanisoft.com/phplib/manual/DB_SqlMethods.php#DB_SqlMethodsInt - -You should always use $cfg["tab"][*] to access Contenido tables. - -Warning: You should never ever use $db in your modules. Always use your -own variables. - |
-
| $sess - |
- The current session. Useful
-variables: - -$sess->id (current session ID) - |
-
| $auth - |
- Authentification information.
-Useful variables: - -$auth->auth["uid"] (current user ID) -$auth->auth["uname"] (current user name) - |
-