==================================================================================================== HOW TO UPDATE - read below for update instructions ==================================================================================================== CONTENT * HOW TO UPGRADE TO UDDEIM 1.1 FROM UDDEIM 1.0 or 0.9 - How to upgrade - Optional steps * HOW TO UPGRADE TO UDDEIM 1.0 FROM UDDEIM 0.8 OR EARLIER - How to upgrade - Migration of uddeim_config.php - Optional steps * FIRST INSTALL OF UDDEIM - Installation - Optional steps * ADDITIONAL JOOMLA 1.5 NOTES * FAQ - Community Builder - Community Builder Enhanced - Popup notifications - Email notifications - Miscellaneous questions * APPENDIX A - Folder structure * APPENDIX B - Languages supported * APPENDIX C - Import from other PMS * APPENDIX D - How to add more smileys * APPENDIX E - Important links * APPENDIX F - Template CSS * APPENDIX G - Supported BB code tags ==================================================================================================== HOW TO UPGRADE TO UDDEIM 1.1 FROM UDDEIM 1.0 or 0.9: ==================================================================================================== How to upgrade: --------------- 1. Backup your uddeIM template (if you do not use uddeIM's default templates) Backup your database (at least all tables prefixed "uddeim", when using phpMyAdmin you can copy the tables given the copy a new name, e.g. jos_uddeim_backup). 2. Backup your configuration using the internal backup function and/or backup the config file: /administrator/components/com_uddeim/config.class.php I recommend to uninstall the previous version of uddeIM and then upgrade to uddeIM 1.1 using the component installer, so you might need this file to restore your settings. When you are an experienced user you can also overwrite the existing files with the new files from the archive. Please check appendix A for the correct folder structure. 3. After upgrading uddeIM, update your database tables (go to phpMyAdmin and enter following SQL statements in the SQL box, this will create the missing fields). When you upgrade 1.0 to 1.1: ALTER TABLE `jos_uddeim` ADD `publicname` TEXT ; ALTER TABLE `jos_uddeim` ADD `publicemail` TEXT ; ALTER TABLE `jos_uddeim_emn` ADD `public` INT( 1 ) DEFAULT '0' NOT NULL ; ALTER TABLE `jos_uddeim_emn` ADD `lastsent` INT( 11 ) DEFAULT '0' NOT NULL ; CREATE TABLE IF NOT EXISTS `jos_uddeim_userlists` ( `id` int(11) NOT NULL auto_increment, `userid` int(11) NOT NULL default '0', `name` varchar(40) NOT NULL default '', `description` text NOT NULL, `userids` text NOT NULL, PRIMARY KEY (`id`), KEY `userid` (`userid`) ) TYPE=MyISAM; When you upgrade 0.9b to 1.1: ALTER TABLE `jos_uddeim` ADD `publicname` TEXT ; ALTER TABLE `jos_uddeim` ADD `publicemail` TEXT ; ALTER TABLE `jos_uddeim_emn` ADD `public` INT( 1 ) DEFAULT '0' NOT NULL ; ALTER TABLE `jos_uddeim_emn` ADD `lastsent` INT( 11 ) DEFAULT '0' NOT NULL ; CREATE TABLE IF NOT EXISTS `jos_uddeim_config` ( `varname` tinytext NOT NULL, `value` tinytext NOT NULL, PRIMARY KEY (`varname`(30)) ) TYPE=MyISAM; CREATE TABLE IF NOT EXISTS `jos_uddeim_userlists` ( `id` int(11) NOT NULL auto_increment, `userid` int(11) NOT NULL default '0', `name` varchar(40) NOT NULL default '', `description` text NOT NULL, `userids` text NOT NULL, PRIMARY KEY (`id`), KEY `userid` (`userid`) ) TYPE=MyISAM; 4. Restore your uddeIM template (from step 1, when you do not use uddeIM's default templates) 5. Restore your configuration. When you have used the internal backup feature its just one click, otherwiese restore config.class.php from step 2. After doing that it is important that you review the new added settings and save the new configuration! 6. Check Community Builder settings (it is not required to use CB with uddeIM but it is highly recommended for a community platform). There are uddeIM settings for the "cblogin" module and "mypms" plugin of the Community Builder. When possible choose "uddeIM 1.1" otherwise "uddeIM 1.0". It is recommended to install the uddeIM specific modules (see the important note below). IMPORTANT: The patched modules "mod_cblogin" and "plug_pms_mypmspro" introduced with uddeIM 0.6 are not longer supported by me (though they are still in the archive I will remove them in future). a) plug_pms_uddeim A plugin for the Community Builder that allows to send a "Quick message" from a user's profile. Install this with the plugin installer in CB. You have also to publish and configure a tab in CB. "plug_pms_uddeim" is the uddeIM-only version of "plug_pms_mypmspro" (delivered with CB) and supports several additional features of uddeIM. Note: Unpublish "plug_pms_mypmspro" (delivered with CB) when you use this plugin! b) plug_pms_uddeim_inbox A plugin for the Community Builder that shows the content of the inbox in a profile tab. Install this with the plugin installer in CB and you have also to publish and configure a tab in CB. When you want to enable popup notifications it is not longer required to replace module "cb_login" with a patched version. If you have replaced this module restore the original files OR disable popup notification in the patched version since this job is done in module "mod_uddeim" now. a) mod_uddeim A message notifier module. Install this module with the module installer. The module provides popup notifications introduced with uddeIM 0.8. When you do not want to have any output, switch of the module title and select "No output" in the module configuration (so it will only do the notifications for you). Note: DO NOT enable popup notifications in "mod_uddeim" AND "cb_login" (patched). If you use both packages it is recommended to enable popups in mod_uddeim. b) mod_uddeim_mailbox A mailbox module for uddeIM. Install this module with the module installer. The module shows some statistics and links to the inbox, outbox, trashcan, archive, settings and compose form. Note: Use this module on small sites only. It creates some cpu load on your database server because of some additional queries performed on each page view. Optional: When you want to use message obfuscating check the "key" which can be set in uddeIM administration. Default is "uddeIMcryptkey" but it can be changed to whatever you like. This "key" is used to obfuscate all new messages. You cannot change this value later. You have to set it before the first new message has been written and obfuscating of messages is enabled in the preferences. ==================================================================================================== HOW TO UPGRADE TO UDDEIM 1.1 FROM UDDEIM 0.8 OR EARLIER: ==================================================================================================== How to upgrade: --------------- 1. Backup your uddeIM template (if you do not use uddeIM's default templates) Backup your database (at least all tables prefixed "uddeim", when using phpMyAdmin you can copy the tables given the copy a new name, e.g. jos_uddeim_backup). 2. This version uses a new configuration file. You will find this file here: /administrator/components/com_uddeim/config.class.php Because of this change I recommend to uninstall the previous version uddeIM first and then upgrade to uddeIM 1.1 using the component installer. When you are an experienced user you can check the section below how to migrate your configuration. 3. After upgrading uddeIM update your database tables (go to phpMyAdmin and enter following SQL statements in the SQL box, this will create the missing fields). Please check the version you have already installed. When you have installed uddeIM 0.6 then you have to apply: ii), iii), iv), and v) You can also compare your database tables with the table structure given in uddeim.xml. i) When you upgrade 0.5b and below to 1.1: ALTER TABLE `jos_uddeim` ADD `totrashoutbox` INT( 1 ) DEFAULT '0' NOT NULL ; ALTER TABLE `jos_uddeim` ADD `totrashdateoutbox` INT( 11 ) DEFAULT NULL ; ii) and additionally when you upgrade 0.6b and below to 1.1: ALTER TABLE `jos_uddeim` ADD `cryptmode` INT( 1 ) DEFAULT '0' NOT NULL ; ALTER TABLE `jos_uddeim` ADD INDEX `toid_toread` ( `toid` , `toread` ) ; ALTER TABLE `jos_uddeim_emn` ADD INDEX ( `userid` ) ; UPDATE `jos_uddeim` SET totrashoutbox=1, totrashdateoutbox=1 WHERE ((systemmessage IS NOT NULL) AND (systemmessage<>'')) AND (totrashoutbox=0) ; iii) and additionally when you upgrade 0.7b and below to 1.1: ALTER TABLE `jos_uddeim` ADD `crypthash` VARCHAR( 32 ) DEFAULT NULL ; iv) and additionally when you upgrade 0.8b and below to 1.1: ALTER TABLE `jos_uddeim` ADD INDEX `datum` ( `datum` ); ALTER TABLE `jos_uddeim` ADD INDEX `totrashdate` ( `totrashdate` ); ALTER TABLE `jos_uddeim` ADD INDEX `totrashdateoutbox` ( `totrashdateoutbox` ); ALTER TABLE `jos_uddeim` ADD INDEX `toread_totrash_datum` ( `toread`, `totrash`, `datum` ); ALTER TABLE `jos_uddeim` ADD INDEX `totrash_totrashdate` ( `totrash`, `totrashdate` ); v) and additionally when you upgrade 1.0 and below to 1.1: ALTER TABLE `jos_uddeim` ADD `publicname` TEXT ; ALTER TABLE `jos_uddeim` ADD `publicemail` TEXT ; ALTER TABLE `jos_uddeim_emn` ADD `public` INT( 1 ) DEFAULT '0' NOT NULL ; ALTER TABLE `jos_uddeim_emn` ADD `lastsent` INT( 11 ) DEFAULT '0' NOT NULL ; CREATE TABLE IF NOT EXISTS `jos_uddeim_userlists` ( `id` int(11) NOT NULL auto_increment, `userid` int(11) NOT NULL default '0', `name` varchar(40) NOT NULL default '', `description` text NOT NULL, `userids` text NOT NULL, PRIMARY KEY (`id`), KEY `userid` (`userid`) ) TYPE=MyISAM; 4. Restore your uddeIM template (from step 1, when you do not use uddeIM's default templates) 5. Restore your configuration. When you have used the internal backup feature its just one click, otherwiese restore config.class.php from step 2. After doing that it is important that you review the new added settings and save the new configuration! 6. Check Community Builder settings (it is not required to use CB with uddeIM but it is highly recommended for a community platform). There are uddeIM settings for the "cblogin" module and "mypms" plugin of the Community Builder. When possible choose "uddeIM 1.1" otherwise "uddeIM 1.0". It is recommended to install the uddeIM specific modules (see the important note below). IMPORTANT: The patched modules "mod_cblogin" and "plug_pms_mypmspro" introduced with uddeIM 0.6 are not longer supported by me (though they are still in the archive I will remove them in future). a) plug_pms_uddeim A plugin for the Community Builder that allows to send a "Quick message" from a user's profile. Install this with the plugin installer in CB. You have also to publish and configure a tab in CB. "plug_pms_uddeim" is the uddeIM-only version of "plug_pms_mypmspro" (delivered with CB) and supports several additional features of uddeIM. Note: Unpublish "plug_pms_mypmspro" (delivered with CB) when you use this plugin! b) plug_pms_uddeim_inbox A plugin for the Community Builder that shows the content of the inbox in a profile tab. Install this with the plugin installer in CB and you have also to publish and configure a tab in CB. When you want to enable popup notifications it is not longer required to replace module "cb_login" with a patched version. If you have replaced this module restore the original files OR disable popup notification in the patched version since this job is done in module "mod_uddeim" now. a) mod_uddeim A message notifier module. Install this module with the module installer. The module provides popup notifications introduced with uddeIM 0.8. When you do not want to have any output, switch of the module title and select "No output" in the module configuration (so it will only do the notifications for you). Note: DO NOT enable popup notifications in "mod_uddeim" AND "cb_login" (patched). If you use both packages it is recommended to enable popups in mod_uddeim. b) mod_uddeim_mailbox A mailbox module for uddeIM. Install this module with the module installer. The module shows some statistics and links to the inbox, outbox, trashcan, archive, settings and compose form. Note: Use this module on small sites only. It creates some cpu load on your database server because of some additional queries performed on each page view. Optional: When you want to use message obfuscating check the "key" which can be set in uddeIM administration. Default is "uddeIMcryptkey" but it can be changed to whatever you like. This "key" is used to obfuscate all new messages. You cannot change this value later. You have to set it before the first new message has been written and obfuscating of messages is enabled in the preferences. Migration of uddeim_config.php: ------------------------------- 1. The old configuration files /administrator/components/com_uddeim/uddeim_crypt.php (uddeIM 0.7b/0.8b) /administrator/components/com_uddeim/uddeim_config.php (uudeIM 0.5b-0.8b) and the new file "config.class.php" are very similar. When you plan to migrate your old configuration backup these two files first before uninstalling the previous version of uddeIM. When you open the old configuration you will find entries like "$config_realnames = 0;". The corresponding value in the new configuartion file starts without the leading "$config", e.g. "var $realnames = 0;". Change all values in respect of the old configuration file. 2. After installation of uddeIM 1.0 you can overwrite the new created configuration file with your migrated one. 3. IMPORTANT: Some configuration variables may have changed so check your configuration immediately after updating all files! Don't forget to save the configuration (so uddeIM rewrites the configuration) even when you think everything is ok! ==================================================================================================== FIRST INSTALL OF UDDEIM ==================================================================================================== Installation: ------------- 1. Use the Joomla installer to install this component. 2. Check the configuration in the backend before starting to use uddeIM. Configuration setting printed in red are not available since a component is not installed on your system (e.g. Community Builder). 3. Check Community Builder settings (it is not required to use CB with uddeIM but it is highly recommended for a community platform). There are uddeIM settings for the "cblogin" module and "mypms" plugin of the Community Builder. When possible choose "uddeIM 1.1" otherwise "uddeIM 1.0". It is recommended to install the uddeIM specific modules (see the important note below). IMPORTANT: The patched modules "mod_cblogin" and "plug_pms_mypmspro" introduced with uddeIM 0.6 are not longer supported by me (though they are still in the archive I will remove them in future). a) plug_pms_uddeim A plugin for the Community Builder that allows to send a "Quick message" from a user's profile. Install this with the plugin installer in CB. You have also to publish and configure a tab in CB. "plug_pms_uddeim" is the uddeIM-only version of "plug_pms_mypmspro" (delivered with CB) and supports several additional features of uddeIM. Note: Unpublish "plug_pms_mypmspro" (delivered with CB) when you use this plugin! b) plug_pms_uddeim_inbox A plugin for the Community Builder that shows the content of the inbox in a profile tab. Install this with the plugin installer in CB and you have also to publish and configure a tab in CB. When you want to enable popup notifications it is not longer required to replace module "cb_login" with a patched version. If you have replaced this module restore the original files OR disable popup notification in the patched version since this job is done in module "mod_uddeim" now. a) mod_uddeim A message notifier module. Install this module with the module installer. The module provides popup notifications introduced with uddeIM 0.8. When you do not want to have any output, switch of the module title and select "No output" in the module configuration (so it will only do the notifications for you). Note: DO NOT enable popup notifications in "mod_uddeim" AND "cb_login" (patched). If you use both packages it is recommended to enable popups in mod_uddeim. b) mod_uddeim_mailbox A mailbox module for uddeIM. Install this module with the module installer. The module shows some statistics and links to the inbox, outbox, trashcan, archive, settings and compose form. Note: Use this module on small sites only. It creates some cpu load on your database server because of some additional queries performed on each page view. Optional: When you want to use message obfuscating check the "key" which can be set in uddeIM administration. Default is "uddeIMcryptkey" but it can be changed to whatever you like. This "key" is used to obfuscate all new messages. You cannot change this value later. You have to set it before the first new message has been written and obfuscating of messages is enabled in the preferences. ==================================================================================================== ADDITIONAL JOOMLA 1.5 NOTES: ==================================================================================================== 1. uddeIM is compatible to Joomla 1.5 in lagacy mode (i.e. you have to enable the "System - Legacy" plugin ("Use Legacy URL Routing" is not required). 2. When your .php files are running under different owner rights (e.g. "wwwrun" and "userid") make sure that you do not have ftp mode enabled in global configuration when you install uddeIM. uddeIM creates a new configuration file during installation. With ftp mode enabled the existing file will be owned by "userid" and the new created file is owned by "wwwrun". So you will get an error mesage that the configuration file could not be written. ==================================================================================================== FAQ ==================================================================================================== Community Builder: ---------------------------------------------------------------------------------------------------- Q: Can I use the patched modules and plugins with CB 1.0? A: Don't know. You should contact beat or nant according backward compatibility of these modules. Backup the old files and give it a try. Nevertheless I strongly recomment to update to CB 1.1. Q: I can send messages etc. but I am not notified about new messages. A: You have to configure "cblogin" module (use the patched one when popups are required) or use "mod_uddeim" module for notifications. Q: I've been trying to get a tab to show up in user profiles in CB. In the CB plugin manager I've published PMS uddeIM and unpublished PMS MyPMS and Pro. PMS uddeIM access is set to public. In the CB Tab Manager PMS MyPMS and Pro is unpublished. PMS uddeIM is published, position is set to Main Area, type is set to Tab, and access is set to Everybody. UddeIM itself seems to work just fine, when I link to the main component. I just can't get a tab to show up in my user profile. What am I missing? A: You cannot use the "Quick Message" tab (plug_pms_uddeim) for public messages. This is an important security feature since the "Quick Message" tab does not provide any anti spam features. Please set the plugin to registered users only, since the box do only appear for registered users. You can use the public frontend feature of uddeIM 1.1 when you want public users to contact registered users. Community Builder Enhanced: ---------------------------------------------------------------------------------------------------- Q: How can I integrate uddeIM in CBE? I have CBE and uddeIM installed. In CBE uddeIM is set up as PMS system. When I click on the envelope in the the login box nothing happens. A: You have to create a menu link to the uddeIM component, which can be "unpublished". In CBE select "PM Notification: uddeIM 0.4 or higher". Popup notifications: ---------------------------------------------------------------------------------------------------- Q: Which uddeIM module provides provide popup notifications? A: Following modules contain code for popup notifications: - mod_uddeim - mod_cblogin (patched module) DO ENABLE POPUPS IN ONE MODULE ONLY! I.e. when you use "mod_uddeim" and have enabled popups here, there is no need to install the patched mod_cblogin module. It is recommended to install mod_uddeim for popup notifications (I do not longer support mod_cblogin in upcoming versions). When you do not want any module output (only use popup support), switch of the module title and the module output in the preferences. Email notifications: ---------------------------------------------------------------------------------------------------- Q: uddeIM does not send any email notifications, what's wrong? A: There are a lot of issues which cause this problem: 1. Check if "Email stopp" is still activated in backend (it is activated by default after a fresh installation of uddeIM). 2. Check if you have enabled email notifications in backend (use "yes" when all users should be notified or "admin" when admins should be notified only). 3. Check if you have set "Default email notifications" to "always". This is the default for the users frontend setting. Existing user settings are not changed, this is used for new users only. 4. Check if the user has enabled email notifications in frontend (you can do this using the backend "userlist settings"). 5. Check if the emails are not filtered by your or the recipient's ISP. When you are not using a smarthost sometimes it happens that your email server is on a remote blacklist which means the emails are sent but filtered. 6. Check the mail settings in uddeIM and Joomla. Usually "phpMail" should be the correct setting in uddeIM. This requires that PHP is correctly configured so it can send emails using the PHP command "mail". If you have problems you can try "mosMail" which uses Joomlas library function to send emails. This requires that Joomla is correctly installed and the mail system is configured correctly. Miscellaneous questions: ---------------------------------------------------------------------------------------------------- Q: What is "obfuscate", and what is the difference between obfuscate and encyption? A: All known PMS for Joomla store messages as plain text in the database, so when you backup your database or use phpMyAdmin to access it you can read all messages without any problems. When you "obfuscate" a message, this message is encrypted in the database using a key the admin configures in the backend. It is compareable to ROT13 (see http://en.wikipedia.org/wiki/Rot13 ), so a human user cannot read the massage but since the key is known the admin could decrypt the message with some effort (the PMS user does not recognize the obfuscating of messages). When you "encrypt" a message, this message is encrypted with a key the PMS user enters in the frontend (it is called "password" in the frontend which is actually wrong because it is a key but users usually do not know the difference so it is easier for them to understand what to do). Since this key is only known by the sender and the receiver the admin cannot decrypt the message (with major effort it is still possible because uddeIM does actually not support strong encryption like AES (symmetric encryption) or RSA (asymmetric encryption) used e.g. in PGP). Q: I do only see a blank screen when I call uddeIM. A: You have to create a menu link to the uddeIM component (when you have upgraded uddeIM check if the menu link is still intact, so that it has the correct Itemid). If you do not want a visible link in your menu, anyhow you have to create one but leave it unbublished. Q: How can I change the with of the textarea where the user enters his message? A: Edit the corresponding CSS files. Look for #uddeim-writeform textarea { ... width: 450px; ... } and change the width. Q: I cannot see the "Send" button?!? A: This happens when the main template CSS sets the text and background to the same color. Check "uddeim.css" (and all corresponding browser CSS files) and set the background (or text color) to e.g. blue: #uddeim-writeform input.button { font-family: Arial, Helv, Helvetica, "MS Sans Serif", "Sans Serif"; font-size: 11px; background: blue; border: 1px solid #c0c0c0; } Q: I am getting a "Error 500-Internal server error" when I install uddeIM. A: "Error 500" means a general server (maybe configuration) error. So either the server is misconfigured, there is a problem in your ".htaccess" file(s) or your server has not enough CPU power to complete a script. When it is a overloaded server you can try to remove the template folder from the installation package. Don't forget to remove the corresponding lines from the XML file, too. So the Joomla installer needs lots of less CPU power to install the component. When you have installed the component, ftp the missing templates to \components\com_uddeim\templates. Q: I cannot change uddeIM's CSS files. Seems like I don't have permission to that. The way I try to this is by downloading the CSS file, mod it, and then upload it again. But then I get the message that I can't overwrite the original CSS file. A: When you upload components using ftp the owner of the file is usually the user (e.g. ftpuser), when you use the Joomla components installer the owner is usually the webserver (e.g. wwwrun). So you cannot change these files using ftp. Use JoomlaXplorer to modify the access rights when the owner is wwwrun. ==================================================================================================== APPENDIX A - Folder structure ==================================================================================================== In /components/com_uddeim/ uddeim.php inbox.php outbox.php archive.php trashcan.php userlists.php includes.php blocking.php block.plugin.php.disabled bbparser.php crypt.class.php getpiclink.php cb_extra.php json.php index.html public.php captcha.php captcha15.php monofont.ttf js/* templates/* In /administrator/components/com_uddeim/ admin.uddeim.php admin.shared.php admin.includes.php admin.usersettings.php toolbar.uddeim.php install.uddeim.php uninstall.uddeim.php config.class.php index.html language/* language.utf8/* ==================================================================================================== APPENDIX B - Languages supported ==================================================================================================== ISO-8859-1 (Latin-1) and UTF-8: ------------------------------- brazilian_portuguese.php catalan.php danish.php dutch.php english.php finnish.php french.php germanf.php germani.php italian.php norwegian.php romanian.php spanish.php swedish.php turkish.php UTF-8 only: ----------- hrvatski.php srpski.php simplified_chinese.php traditional_chinese.php ISO-8859-2 and UTF-8: --------------------- polish.php ISO-8859-8 and UTF-8: --------------------- hebrew.php Windows-1251 (CP1251): ---------------------- bulgarian.php russian.php ==================================================================================================== APPENDIX C - Import from other PMS ==================================================================================================== uddeIM can import messages from following PMS: - myPMS II 2.x - Danial Taherzadeh - myPMS Enhanced 2.x - Stefan Klingner - jim 1.x - Laurent Belloeil - Archaic Binary Private Messages 1.x - Wayne Smith - JAM - Joomla Advanced Message 1.x - Cas de Vroom - Clexus 2.0 - Clexus New Media - Missus 1.1 - Barbara Irene Meclazcke - Primezilla 1.0 - Achim Fischer ==================================================================================================== APPENDIX D - How to add more smileys ==================================================================================================== Animated emoticons: ------------------- Currently animated emoticons are available for all themes exept "noir" (maybe someone can convert all emoticons in "/templates/~~~theme~~~/animated" into a gray shades?). Extended animated emoticons: ---------------------------- Extended animated emoticons can be stored in folder "/templates/~~~theme~~~/animated-extended". For the default template about 32 animated emoticons are provided. If you need more you can copy as many emoticons in this folder as you like. The filename is used to identify an emoticon in the message (e.g. "cry.gif" will be entered as ":cry:"). The best source for animated emoticons is http://www.kolobok.us Many thanks to Aiwan who allowed me to use his emoticons in uddeIM. ==================================================================================================== APPENDIX E - Important links ==================================================================================================== - Call settings dialog when "show settings" is off in backend (no menu link is shown in uddeIM). http://yoursite/index.php?option=com_uddeim&task=settings - Open new message dialog to user with userid XX: http://yoursite/index.php?option=com_uddeim&task=new&recip=XX [&nouserlist=Y] Open new message dialog to user with username XX (this is independent from realname/username setting): http://yoursite/index.php?option=com_uddeim&task=new&runame=XX [&nouserlist=Y] 'nouserlist' parameter (optional): 1 = suppress user list, 2 = suppress connection list, 3 = suppress both lists add +4 when the TO field should be disabled e.g. 4 = disable TO field only, 5 = suppress user list AND disable TO field, and so on ==================================================================================================== APPENDIX F - Template CSS ==================================================================================================== Check uddeim.css in the default template to see which CSS IDs and classes are used by uddeIM. uddeIM has a browser switch. So you can use specific CSS for different browsers. If such a specific file is not found, it will try to load uddeim.css from the current template and when this fails uddeIM reverts to uddeim.css from the default template. Recognized filenames are: uddeim-opera.css uddeim-ie4.css uddeim-ie6.css uddeim-ie7.css uddeim-ie5win.css uddeim-ie5mac.css uddeim-ie.css (all Internet Explorer) uddeim-safari100.css uddeim-safari85.css uddeim-safari.css (all Safari) uddeim-konq2.css uddeim-konq3.css uddeim-konq.css (all Konqueror) The test is cascading. For an Internet Explorer 5.5 on Windows, uddeIM will first search for the file uddeim-ie5win.css, then for the file uddeim-ie.css, then for uddeim.css in the current template, and then for uddeim.css in the default template. ==================================================================================================== APPENDIX G - Supported BB code tags ==================================================================================================== uddeIM supports some BB code tags: [b]bold[/b] [i]italic[/i] [u]underline[/i] [color=#000000]coloured text[/color] [size=1][/size] [size=2][/size] [size=4][/size] [size=5][/size] [ul]unordered list[/ul] [ol]ordered list[/ol] [li]list item[/li] [url=http://www.domain.com]Domain[/url] [url]http://www.domain.com[/url] [img]http://www.domain.com/nicepicture.jpg[/img] [img size=120]http://www.domain.com/nicepicture.jpg[/img]