Skip to content
This repository was archived by the owner on Jul 5, 2022. It is now read-only.

Manual

Jump to bottom
drak edited this page Nov 1, 2012 · 3 revisions

Requirements

Zikula Application Framework

Notice: Since Zikula 1.0.3 various Zikula-modules are already working on close cooperation with InterCom. Several module functions and blocks of Members_List and Users consider the existence of InterCom or pnMessages and show the contents (number of mails, links, etc.) properly. Nevertheless it is necessary to use the Zikula Core in version 1.0.3!

Installation

New installation

  • Please unpack the contents of your downloadarchive and transfer them via FTP to your web-server. Your InterCom directory must be located in the modules-directory of Zikula. And don not forget the plugin in /config/plugins.
  • Visit the module list in the Zikula administration panel, refresh and initialize it and activate InterCom.
  • If you want you can activate the Hooks BBCode and BBSmile for InterCom.
  • Notice: The installation of InterCom generates a new hook that will be activated on the Users-module, so that new users will receive a welcome-mail.

Update

Notice: An upgrade to InterCom 2.2 (Zikula) is only possible if you have pnMessages 1.5 installed before.

  • Please backup your database!
  • Delete the directories pnMessages and/or Intercom in your Zikula modules directory. If you don't do this, you will be rewarded with an additional InterCom entry in your module list after each regeneration!
  • Delete the directory /javascript/ajax/themes recursively. These files are not longer needed in InterCom 2.2
  • Copy your files via FTP on your web-server (see above)
  • Visit the modulelist in the Zikula adminsitration panel, refresh, upgrade and activate InterCom.

Permissions

Reading the folders Inbox, Outbox, Archives and existing messages will be ensured by the following access rights:

||'''Group'''||'''Component'''||'''Instance'''||'''Permissions level'''|| ||groupname||InterCom::||::||read||

For creating, replying and forwarding messages the following access rights are needed:

||'''Group'''||'''Component'''||'''Instance'''||'''Permissions level'''|| ||groupname||InterCom::||::||comment||

Block Access

If you want to block access to the module for a specific user group, it can be realized through the following rule:

||'''Group'''||'''Component'''||'''Instance'''||'''Permissions level'''|| ||groupname||InterCom::||::||none||

Message to an entire usergroup

For sending a message to an entire group, please add the following rule:

||'''Group'''||'''Component'''||'''Instance'''||'''Permissions level'''|| ||groupname||InterCom::||MsgToGroups::||comment||

Clone this wiki locally