In this chapter you'll learn how to get activeCollab up and running on your own server. First, we'll describe all the server requirements necessary to run activeCollab nice and smoothly. Then, we will lead you through the installation process, one step at a time. Finally, we give some advice to help you make sure your copy of activeCollab is totally secure.
Let's get started!
activeCollab is a PHP-based application that must be downloaded and installed on a server in order to run (after purchasing a licence). Currently it is not available as a hosted service. The minimum system requirements that your web server must meet to run activeCollab are:
There is no need for you to use commercial MySQL editions, free MySQL Community edition database will work just fine with your activeCollab. If you don't already have one, you can download your MySQL Community Server here.
We recommend the following system configuration:
The following PHP extensions are required for some optional features to work, but they are not required for the system itself to operate:
To access and use activeCollab, your users will need to have a web browser (Microsoft Internet Explorer 6+, Mozilla Firefox 2+, Apple Safari 3+, Google Chrome) with JavaScript enabled. activeCollab is optimized for 1024x768px or higher screen resolution.
*Logos and product names used on this page are trademarks or registered trademarks of their rightful owners.
To see if your system meets the system requirements, you can use the probe.php script, designed specifically for this purpose.
Here's how:
It will run a check of your platform and additionally try to connect to the database and see if it meets the system requirements.
The activeCollab installation can be completed in six simple steps:
Read on to learn more about each of these steps.
Before you start the installation, please make sure that your server meets the activeCollab System Requirements. activeCollab works well on most platforms which have a web server with PHP support and MySQL database.
To see if your system meets the system requirements, use the probe.php script, designed specifically for this purpose.
Here's how:
activeCollab installer will not created a database for you, so please make sure that you have a database available for your activeCollab installation before continuing with the install process. If you don't have a database, you can create it by using your favorite MySQL administration tool (phpMyAdmin, for instance) or contact your system administrator to create a database for you:
After creating the database, write down the following details:
activeCollab installer will ask for the same details later and you won't be able to perform the installation without them.
Before you can install activeCollab, you'll need to download two files from your profile page on the www.activeCollab.com website, both the:
Both files are available in your www.activeCollab.com profile. To access the installation and license files, please login with the same account you used to purchase the license and, once logged in, click My Profile in the top right corner of the page:
All your licenses (you can have more than one license purchased from the same account) will be listed on here. Both the installation package and license file download links are available in the license details block:
Once you have downloaded and unpacked the installation package using your favorite ZIP utility, you will see the following files and folders:
You do not need to upload all these files to your server. Instead, you should upload only the contents of the /for-upload folder:
Once you have uploaded files from the /for-upload folder to your server, you can run the activeCollab installer. The installer tool can be run with any web browser. In fact, if you try to open any of the activeCollab pages at this point, the system will inform you that activeCollab is not yet installed and will offer you a link to the installer tool instead.
Click on that link to start the installer:
The installer will then ask you to provide the:
If the installation is run properly, the system will display several OK messages and provide you with a link to the login screen, where you can use the administrator email address and password (which you defined earlier) to login:
After you have completed the activeCollab installation, you should delete the /public/installer folder from your server for security reasons.
After you have run the Installation tool and deleted the /public/installer folder, you can visit your new activeCollab setup. If everything has gone well, the system will display a simple login screen where you can login using the administrator username and password, which you provided during the installation:
If you don't see the login screen or see an error message or blank page instead, please consult the Troubleshooting guide or contact our support team.
If you were evaluating activeCollab before you have decided to purchase the license, you can have exactly the same setup as you created in the Hosted Demo in your installed activeCollab. All you need to do is to import your demo database into your hosted activeCollab.
Before making the actual import you have to get the demo data. They are available on your www.activeCollab.com profile page under the Export data link.
Please note that our Hosted Demo is a fully featured activeCollab Corporate. If you have purchased activeCollab Small Biz license you will not be able to export your demo data. What you should do in this case is to contact us and let us know about the issue. We will help you set your demo to match the activeCollab Small Biz features, export the data afterwords and send it to you via email.
Now that you have the exported archive here's what you need to do to import it into your activeCollab:
After completing all of these steps, you should be able to see all your data from the Hosted Demo in your installed activeCollab.
If you have any difficulties, feel free to contact us, and we'll help you set your activeCollab.
activeCollab application is secure right out of the box, but there are still a couple of things that you can do to make your own setup of it as secure as possible:
Installing the system above the site root ensures that only files from the /public folder are publicly available, while all other files are not accessible on the web. Even though the system encodes file names and comes with .htaccess rotection by default for folders with sensitive data (/upload, /thumbnails and other), the very best approach is to have them installed above the site root.
Instructions on how to set up the activeCollab in this way are available here: /public Folder as Document Root.
activeCollab is protocol agnostic, so if your server supports SSL and has proper certificates installed, it will work on HTTPS as well as on HTTP. All you need to do is to run the Installer on the proper protocol and it will use the HTTPS URL automatically.
If you have activeCollab already installed on HTTP, and then decide to add a certificate later so it can work over HTTPS, you can change the protocol in the config/config.php file:
define('ROOT_URL', 'http://example.com/public')
All you need to do is to use https:// instead of http:// protocol in ROOT_URL value:
define('ROOT_URL', 'https://example.com/public')
After you have updated the ROOT_URL don't forget to delete files with "cch_" in the beginning in your /cache folder and files with "%%" from the /compile folder.
When you use the system over SSL, browsers will not cache CSS, JavaScript or image files. This may have a significant impact on how quickly pages are loaded. Due to this, we recommend using SSL only when you are working with sensitive data.
In this section, you'll learn how to configure activeCollab the way you want it and get the best out of all the different features available to you.
You can configure many of the general options in activeCollab from the General Settings page. To access it, select the General tool in the Administration area:
From here you can configure the following settings:
You can make changes to the time and date format in activeCollab (for example, changing the time zone) via the Date and Time settings page. To access this, just click on the Date and Time icon in the Administration area:
The following options are available:
All of the options on the Date and Time Settings page will also be set as default settings for other users, however each user may change these settings to suit their own preferences via their profile page.
The Mailing settings page enables you to configure how activeCollab will send emails. To access this page, click the Mailing icon from the Administration area:
There are two ways in which activeCollab sends emails:
After a successful installation, the Native Mailer is selected by default and emails should work properly, if it is configured in php.ini. If it is not configured, you'll need to provide some SMTP connection parameters. To check if the SMTP parameters you provided are working and activeCollab can connect to the server, use the Test Connection button on the Mailing page.
When you've finished configuring your email settings, please take a look at this article to learn how you can test if activeCollab is sending email messages correctly.
activeCollab lets you set the email address and name that users will see as the From address when they receive email notifications.
By default, activeCollab will use the email address provided by the administrator when it was installed. To change it to something else, just go to the Administration > Mailing page and in the Notifications From section and set a new name and email:
Many SMTP servers do not allow Relaying of messages (i.e, emails sent to the server from other locations) when the sending email address is not the same domain as the SMTP server. In this case, make sure that the From Notifications address is from the same domain as the SMTP server.
Roles enable you to define what people can and cannot do in your activeCollab installation. You can set-up and manage roles in the Roles section of the administration area:
ou should also be aware that there are two type of roles in activeCollab: System Roles and Project Roles.
System Roles define which permissions users have across the whole of activeCollab (such as ability to log in and use the system, access the administration area or manage projects etc.).
activeCollab comes with five predefined roles that you can start using immediately. The first three of which are intended for members of your own company:
The fourth and fifth roles are designed for people who are not included in your company (mostly clients). These people can only see projects they are involved with and can't see objects marked as private. Administrators, Project Managers and Project Leaders can control their access with Project Roles or even defining custom permissions. They cannot create new projects, use assignments filters or use the time report functionality.
There's only one difference between Client Company Member and Client Company Manager: the Client Company Manager can update contact information for his company and add new people to it in your activeCollab setup. With this functionality you can let clients handle some basic company and user administration on your behalf.
If none of the predefined Roles look right for you, you can create new roles or change existing ones to fit your needs:
Every System Role has the following permissions that you can grant or forbid:
| Permission | Description |
Module |
| system_access | This permission sets whether a user can access activeCollab. Set this to No if you don't want to delete a specific user accounts but you want to restrict them from accessing the system for the moment. | System |
| admin_access | Set this permission to Yes if you want to give administration permissions to users in a selected role. This permission overrides every other permissions and additionally gives users access to the Admin panel. | System |
| project_management | Project managers have full permission for everything relating to projects in activeCollab. They can see and access any project and have complete access inside each one. Project managers can create projects even if add_project permission is set to No! |
System |
| people_management | People managers have all permissions regarding account management in the People section. They can create new users or manage existing users and companies without any restrictions. |
System |
| add_project | Sets whether user can create new projects or not. When creating a project, members of client companies will see only people and companies they have previously worked with. They will not see everyone! Administrators and project managers can always create new projects no matter what is set here! | System |
| manage_company_details | Set to Yes if you want to allow a user to manage company details. The user will then be able to change the company information of the company that they already belongs to, as well as being able to add new people and receive/access Invoices issued to it. Please note, if no-one from a company has the correct permission, you won't be able to send email notifications for new invoices to anyone in it, because there will be no eligible recipient for such an email! | System |
| can_see_private_objects | Set to Yes for roles that must be able to see objects in activeCollab marked as private. Usually, this permission is set to Yes only for members of your own company and to No for the client roles. This makes it easy to hide internal discussions or other confidential information that should be kept in-house. | System |
| manage_trash | If set to Yes this role will enable users to manage items that has been trashed by any other user: delete them premaritally or restore them from the trash. When set to No this role will enable user to trash the item, but not to see the Trash icon, or to manipulate further with trashed data. | System |
| manage_assignment_filters | Set to Yes only for roles that should be allowed to either create new or manage existing assignment filters. If set to No, users will be able only to use existing filters, but not create new or change the settings of existing ones. | Resources |
| use_time_reports | This permission determines whether a user can use the time reports functionality or not. Time reports are available both globally and per project. If this permission is set to No, the user will not be able to see or use any time reports. | Time Tracking |
| manage_time_reports | Set to Yes for roles you want to be able to create or manage time reports. | Time Tracking |
| can_use_status_updates | Set to Yes to allow a user to use the Status Update tool. | Status |
| can_use_incoming_mail_frontend | When this permission is set to Yes, users will be able to access email conflict resolution tool and resolve any potential issues with incoming emails. | Incoming Mail |
| can_use_documents | This permission enables users to access the optional global Documents section. When they have access to this section, users will be able to see the Docs icon in the toolbar and view all files placed there. | Documents |
| can_add_documents | This permission enables users to upload new files and post new text documents in the global Documents section. Please note that this permission is ignored if the role does not also have the can_use_documents permission set to Yes. | Documents |
| can_manage_invoices | When set to Yes, person with this permission will be able to create new Invoices, issue existing invoice drafts, mark them as billed or canceled, and to delete Invoices. | Invoice |
Project Roles are re-usable sets of project permissions that define what a user can see and access within a specific project. As project roles are defined on a project-by-project basis, users can have several Project Roles, different for each project they are involved with. When adding a user to a project you can select one of the earlier defined project roles or create a custom set of permissions for that particular project:
Administrators, Project Managers and person set as the Project Leader will automatically have all permissions for that project, as their System Role overrides their Project Role in this case.
Project Role permissions are set for each type of project object (eg. ticket, milestone) and can have four levels:
If a project object (Ticket, Milestone or Task) is not assigned, then all users who have 'Has Access', 'Can Create' or 'Can Manage' project permissions set to Yes will be able to manage that project object. This is a default system behavior that enables users to access and assign themselves to project objects such as Tickets, Milestones or Tasks. If someone os already assigned to a ticket, milestone or task permissions will work as expected.
activeCollab is a flexible system which can be extended with optional extra modules. Administrators can manage these modules using the Modules section in the Administration panel. Two lists are displayed on this page:
To install a module, find the one you're interested in from the Available Modules list and click the Install button. The module will then be available for use in just a few seconds.
If the module you wish to use is not listed in the Available Modules list, then you will need to upload its files to your activeCollab setup. Modules are usually come as in two archived files:
Unpack and upload these files to your activeCollab setup in the following way:
Once the files are uploaded, refresh the Modules page and the new module will appear in the Available Modules list. One click on its Install button will do the rest.
To uninstall a module go to ** Administration > Modules**, and click the name of the module you wish to remove from the Installed Modules list. A new page with all the Module's details will appear. Now simply click the Uninstall button, and that module will be removed from your activeCollab setup. It will not be completely deleted, but instead moved to the Available Modules list where you can install it again in future if you wish.
If for some reason your activeCollab setup is not working correctly because of a broken module and you can't access the administration panel, then you can uninstall the plugin manually:
Master Categories enables you to create a single classification system for your data that you can use across all your projects. In this way, you can set how your information is grouped once and use those classifications across the whole of activeCollab.
From a freshly installed copy of activeCollab you’ll only get a single defined category - General. To add new ones, visit the Administration > Master Categories area, where you can set up all the categories you want. You are also free to remove the General category by clicking the delete icon. However if you don’t create a new category in it's place, activeCollab will retain the General category so there is always at least one category. That's why you may still see the General category in your projects (but not in the Master Categories list) as activeCollab must always have at least one category defined. On the other hand, if you remove General and create a new category, the newly created category will be displayed.
In the Master Category setup you are free to create as many categories as you wish and there is no limit to the number of categories allowed by activeCollab.
Items that can be placed in Categories in activeCollab are Pages, Tickets, Files and Discussions. In the Master Category section you can also create different sets of categories for each type of project item. You can learn how to create such setup in this tutorial.
Newly created Categories are applied only to new projects. They will not work retrospectively, and will not be included in any existing projects in activeCollab, which is why you may wish to define all your major categories when first using the system.
activeCollab 1.1 and later versions come with localization support. This enables you to translate the interface into any language you want; to set the date and time formatting; and much more.
By default, localization support is disabled. In order to enable it, open the config/config.php file and find the following line:
define('LOCALIZATION_ENABLED', false);
Then change the value from false to true. If this line is not present, then add the following line into the config/conifg.php file:
define('LOCALIZATION_ENABLED', true);
Also, make sure that the /custom/localization directory is writable (chmod-ed to 777).
When localization is enabled, the Languages tool will automatically become available in the Administration area:
Another feature will also be made available after enabling Localization - allowing each user to choose any of the installed languages (that you have set-up in the system) as their default language when visiting activeCollab. They option can be found on their profile pages.
When localization is enabled, you'll have an opportunity to add a new language yourself. To do this, insert the language name and language code into the New Language form on the Languages page and click submit:
After the language file is created, you will be able to create a translation file based on dictionaries. A Dictionary is the index of words used in a particular activeCollab module. In order to make a translation you will need to create a new file and to provide a translation for every phrase used in a dictionary. If you don't translate some of the phrases then activeCollab will use the default, English version:
All of your translations will be available in the /custom/localization folder, so you can back them up. If you wish, you can also upload them to the activeCollab Downloads section and share your translation with the rest of the activeCollab Community.
Members of the activeCollab community often share the translations they create with others. These translations are distributed in two formats:
To export a translation, click on the little Export icon next to the language on the Administration > Languages page:
the XML Import / Export feature was added in activeCollab 2 and is not available in previous versions.
For this feature to function properly, XML extension needs to be available to PHP. If XML extension is not installed, the Import Language button will not be available and Languages and page and a warning will be displayed.
The standard way of distributing translations since activeCollab 2 is by packaging them in a single XML file. To import one of these files, go to the Languages page in the Administration area and click on the Import Language button in the top-right of the page:
In the following page, select the XML file and upload it. activeCollab will then scan all the information in the file and provide you with all relevant details, including any possible incompatibilities:
If, after reviewing the information in the file, you'd like to continue, just click the **Finalize Import" button to finish the process. The new language option will be available in the Languages list once the Import procedure is complete.
In activeCollab 1.1 translation files were distributed in the form of multiple PHP files, where each file had the translations for a single activeCollab module. This type of translation package can still be imported in activeCollab 2 and later though.
To do this, first create a new language:
Then check your /custom/localization folder where a new folder should have been created with the name of the locale you used. That is the folder where all the PHP files from translation package should be placed:
Once a localization is enabled, it can also be used to translate the templates used by activeCollab's notification emails. If a user has chosen a different default language for their activeCollab set-up then they will receive emails in that language (should a translation be available). If a translation is not available, emails will be sent in English.
activeCollab does not support tools that allow you to change the names of different system features or project sections but, if you really need that functionality, you can use the Language tool to achieve this:
When creating a new language, please don't use the en_US or e_n_US.UTF-8_ locale. That locale is reserved for the default language only and if you try to use it for a custom language, any translations you make will be ignored by default.
Since activeCollab 2.0, activeCollab can be put into a special Maintenance mode. When activeCollab is in maintenance mode, only people set as Administrators will be able to use it. All the other users will receive a Service Unavailable message.
To enable Maintenance Mode, please click the Maintenance Mode icon in the Administration section:
Set Enable Maintenance Mode to Yes and click Submit, to instantly make the system unavailable to all non-administrative users. Additionally, you can provide maintenance message to users by setting a Maintenance Message value. This message is used to explain why the system is unavailable and when it will be back online. HTML is not supported, but activeCollab will preserve line breaks and automatically detect links.
On top of the regular Maintenance Mode, activeCollab also has a System Maintenance Mode:
The System Maintenance Mode is a specific mode used when you want to block access to the entire system and don't want anyone to be able to log in, even administrators.
This mode is useful when you are upgrading activeCollab, for example. Because this mode is dependent on a single file, activeCollab will display whatever message you set while other files are being upgraded.
The System Maintenance Mode mode can be turned on by setting the MAINTENANCE_MESSAGE option in the config/config.php file to whatever message you want to display to your users. For example:
define('MAINTENANCE_MESSAGE', "We are upgrading the system to the latest version. It'll be back online in the next couple of hours.");
When you want to turn it off, simply remove MAINTENANCE_MESSAGE declaration from the configuration file.
Some activeCollab modules need to be run periodically in order to perform their tasks and functionality. For instance, the Backup module should be run daily if you wish to create daily backups.
All of these events are executed by periodically making a web request on specific activeCollab URL/URLs or executing specific PHP files through command lines (check this article for details). There are three time periods which activeCollab supports:
Command examples with exact paths and URL/URLs that need to be triggered are available on the Administration > Scheduled Tasks page:
activeCollab has three different waysfor generating URLs. Because of that, URLs in your system may look a bit different to the URLs displayed in a screenshot or used in other examples.
Scheduled Tasks page in Administration is also used to check when was the last time these events were triggered, so it's useful for troubleshooting actions that are executed on events triggered by scheduled tasks.
Scheduled tasks in activeCollab can be triggered in two ways:
Both of these approaches have advantages and disadvantages. For example, using PHP to trigger files skips the web server and the overhead that it adds, but you will need to have the PHP command line utility configured on your server. On the other hand, triggering a URL always works when activeCollab is properly configured, but it's a little slower because the web server is added to the mix.
Examples:
/usr/bin/curl -s "http://url/of/hourly/task" > /dev/null
/usr/bin/php "/path/to/activecollab/tasks/hourly.php" > /dev/null
The exact commands you need to execute are listed on the Administration > Scheduled Tasks page of your activeCollab installation.
Scheduled Task URLs can be protected from direct visits by adding the first five letters of your license key as a code parameter:
http://example.com/collab/public/index.php?path_info=frequently&code=QGNig
Protection is automatically turned on for all new installations since activeCollab 2.1. If you upgraded from a version older than 2.1 to the latest version, please add the following code to your config/config.php file in order to enable it:
define("PROTECT_SCHEDULED_TASKS", true);
Note that you'll need to update your cron configuration once you have done so because this changes the URLs that need to be pinged.
In order for events to work you'll need to set-up some kind of scheduling software to execute task scripts or ping specific activeCollab URLs at specific times.
For example, on UNIX you can use cron and PHP or curl to achieve this. Open crontab for editing by executing:
crontab -e
in your command line. Then insert the following text into the field:
*/3 * * * * php "/path/to/activecollab/tasks/frequently.php" > /dev/null 0 * * * * php "/path/to/activecollab/tasks/hourly.php" > /dev/null 0 12 * * * php "/path/to/activecollab/tasks/daily.php" > /dev/null
and save it. This will tell PHP to execute task files:
If the PHP command line interface is not available on your server, you can use curl to request specific URLs to trigger events. activeCollab behaves the same way as task files, but instead of using a PHP command line utility, tasks are invoked by the web server. Here are the commands that you'll need to set in the crontab file:
*/3 * * * * /usr/bin/curl -s "http://url/of/frequently/task" > /dev/null 0 * * * * /usr/bin/curl -s "http://url/of/hourly/task" > /dev/null 0 12 * * * /usr/bin/curl -s "http://url/of/daily/task" > /dev/null
On Windows you can also use Scheduled Tasks to trigger scheduled tasks in activeCollab. To set-up Scheduled Tasks on Windows XP, Vista and Windows 7 (as well as Windows 2003 Server or later) you can use schtasks.exe. To do so, open the command line and type in the following commands:
schtasks /create /ru "System" /sc minute /mo 3 /tn "activeCollab frequently job" /tr "C:\php\php.exe C:\activecollab\tasks\frequently.php -f" schtasks /create /ru "System" /sc hourly /st 12:00:00 /tn "activeCollab hourly job" /tr "C:\php\php.exe C:\activecollab\tasks\hourly.php -f" schtasks /create /ru "System" /sc daily /st 12:00:00 /tn "activeCollab daily job" /tr "C:\php\php.exe C:\activecollab\tasks\daily.php -f"
On Mac OS 10.4 Tiger or later, Apple recommends that you use launchd instead of cron, xinetd, mach_init, and init. Tasks are defined as XML files that tell launchd what to do and when.
To define the three scheduled tasks that activeCollab requires, please create the following files in the /Library/LaunchAgents folder and make sure that you set the correct task URLs (you can find them on the Administration > Scheduled Tasks page of your activeCollab setup):
1. com.a51.activeCollabFrequently.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>com.a51.activeCollabFrequently</string>
<key>ProgramArguments</key>
<array>
<string>/usr/bin/curl</string>
<string>-s</string>
<string>"http://activecollab.dev/public/index.php?path_info=frequently&code=CODE"</string>
<string> ></string>
<string>/dev/null</string>
</array>
<key>RunAtLoad</key>
<false/>
<key>StartInterval</key>
<integer>180</integer>
</dict>
</plist>
2. com.a51.activeCollabHourly.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>com.a51.activeCollabHourly</string>
<key>ProgramArguments</key>
<array>
<string>/usr/bin/curl</string>
<string>-s</string>
<string>"http://activecollab.dev/public/index.php?path_info=hourly&code=CODE"</string>
<string> ></string>
<string>/dev/null</string>
</array>
<key>StartCalendarInterval</key>
<dict>
<key>Minute</key>
<integer>0</integer>
</dict>
</dict>
</plist>
3. com.a51.activeCollabDaily.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>com.a51.activeCollabDaily</string>
<key>ProgramArguments</key>
<array>
<string>/usr/bin/curl</string>
<string>-s</string>
<string>"http://activecollab.dev/public/index.php?path_info=daily&code=CODE"</string>
<string> ></string>
<string>/dev/null</string>
</array>
<key>StartCalendarInterval</key>
<dict>
<key>Hour</key>
<integer>12</integer>
<key>Minute</key>
<integer>0</integer>
</dict>
</dict>
</plist>
These settings will define following tasks:
To see if everything is working properly, periodically check the Administration > Scheduled Tasks page to check the last time tasks were executed successfully.
The following modules are dependent on Scheduled Tasks:
This list applies to activeCollab 2.3. Custom modules may require any of the three events triggered by Scheduled Tasks to work properly.
Incoming email functionality was introduced in activeCollab 2.1 and it enables the system to check any number of POP3 or IMAP mailboxes and read emails from there. Messages that are found in these mailboxes are then imported into activeCollab and sorted into the correct part of the system.
When a message is imported from the mail server, activeCollab does the following:
For incoming mail to work properly, the following conditions needs to be met:
You can learn how to setup Incoming mail from the scratch in How to setup Incoming Mail tutorial.
activeCollab can check any number of POP3 and IMAP mailboxes. To define them, go to the Administration area and from the Mailing section click on the Incoming Mail icon:
On the following page, you will see a list of all defined mailboxes. Click the Add Mailbox button to define a new mailbox:
On the New Mailbox form you'll be able to define:
When activeCollab receives a message that is not a reply to a previous notification, it will use the default mailbox action configured when the mailbox was defined to process the email:
These settings tell activeCollab to either create a ticket or a discussion in the given project.
A single mailbox can create tickets or discussions in only one project, but this does not limit notification replies. When a user replies to a notification, comments will be created in the appropriate project and attached to the relevant item.
One important thing to note is that is that the mailbox enforces project permissions by default. This means that all messages sent by people who are not part of that project can result in a conflict that will need to be resolved by an administrator. If you don't wish project permissions to be enforced, you can enable the following options:
If, for any reason, activeCollab is not able to process an email message automatically, it will not discard it (like some other applications!). Instead, it will create a conflict notification to let an administrator resolve the problem. When there is such a conflict, the Inbox icon will show up in the toolbar and display the exact number of conflicts:
Click the Inbox icon to open the Conflicts page. This page lists all conflicts that need to be resolved and shows the reason why activeCollab was not able to handle the messsage automatically:
Click the Resolve icon on the right to open the conflict resolution tool and see message properties. activeCollab will pre-load fields based on the mailbox rules and let you change them:
The administrator has the final word regarding conflict resolutions. Once he or she submits the form, activeCollab will accept all the properties that are submitted regardless of permissions or restrictions.
Massages that resulted in conflict can also be deleted. To delete a message and remove it from Conflicts page, click on the Remove icon on the right.
The invoicing module allows you to prepare and issue invoices, as well as track payments in activeCollab. It is also designed to integrate well with activeCollab's time tracking and enables users to create invoices based on the time entries they have logged. The invoicing module will also update the status of the appropriate time record automatically whenever a client makes a payment for completed work.
The Invoicing module is not installed by default. To install it, go to Administration > Modules where you can see it in the list of Available Modules:
Click on the Install button and follow the on-screen instructions.
Now that you have installed the Invoicing Module, make sure to give access to the Invoice module only to the people you wish. This module restricts invoice management for all roles by default. Only people who have can_manage_invoices permission set to 'yes' will be able to use this module.
All adjustments to the Invoicing Module can be made within the Invoicing section, which can be found in the Admin pannel after installation of the module is completed.
The following options are available:
The Public Submit module allows people who don't have an activeCollab account to post Tickets in one of your projects using a simple web form available on your website.
activeCollab 1.1 Corporate or later. In order to enable CAPTCHA protection you will need to have the GD extension enabled with FreeType support. CAPTCHA protection is optional, but recommended.
The Public Submit module is not installed in activeCollab by default. To activate it, go to Administration > Modules and install it from the list of Available Modules.
Even after installation, the Public Submit Module needs to be enabled before it can be used. To do this go to the Administration section and click the Public Submit icon in the Tools section:
Once on the configuration page you can set whether Public Submit is enabled or disabled; select a project where the newly created Tickets will be posted to; and turn the CAPTCHA spam protection on or off:
Public Submit can be used to create Tickets in only one, selected project. Since Tickets can have different categories within a project, anyone using the Public Submit Module will be able to choose from these categories. To define these categories use the Manage Categories tab on the Tickets page (of the defined project) or click the New Category... option on the Public Submit page of your website and create a new category from there (though you will need to be logged in to activeCollab to do so).
Once the Public Submit Module is set-up, you can refer users to a publicly available webpage where they can submit a Ticket by entering their name, email address and name of the issue.
The user may also add optional extra information to the ticket by choosing a ticket category and priority; as well as being able to add a longer description or include an attachment.
Here's an example:
activeCollab is shipped with a Backup module, designed to make daily backups of your data automatically. As well as backing up all data from your database, it will also backup all files that have been uploaded to the /work/backup folder.
Once a backup is created, the module will also create a file that explains how you can restore the backup easily.
The Backup Module uses a daily task to create backups. In order for it to work correctly then, Scheduled Tasks need to be properly configured.
The Backup Module is not installed in activeCollab by default, but can be installed from the Administration > Modules page where it can be found on the Available Modules list.
After installation, backups will still need to be enabled. To do so, go to the Backup Settings page by clicking on the Backup link in Tools section of the Administration area:
You can also configure the number of daily backups which should be kept. We recommend keeping at least the last five backups:
activeCollab supports version control integration through the Source Module. Currently the Source Module only supports integration with the Subversion version control system.
The Source module is not installed by default. To install it, go to the Administration > Modules page and select Source module from list of Available Modules:
The Source Module uses a command line Subversion client to interact with repositories. Once the Source Module is installed, you'll need to configure the path to the Subversion command line client. To do that, go to the Administration page and click the Source Settings icon in the Tools section:
You must then provide a path to the folder where your svn client binary is located:
The settings page has a simple tool that lets you check whether the path you have inserted is valid and if activeCollab can interact with the command line tool. When a valid path to the Subversion command line client is provided, you'll be able to add SVN repositories to all of your projects.
More details on this issue are available in How to configure Source Module Tutorial.
The WebDAV module in activeCollab will give you access to activeCollab projects, categories and files in the Files module through a WebDAV client.
Here are the instructions on how to configure it and use it with your favorite WebDAV Client.
WebDAV Module is in the Beta testing phase at the moment, and it is not shipped with activeCollab package.
In order to use the WebDAV module you will need to install it first. If you haven't downloaded it before, you can do so here.
Upon downloading the module, you will need to extract the files in it and copy the folders to the respective parts of the activeCollab root folder. If you are prompted to overwrite any files, please do so. After copying the files, open activeCollab and go to the Admin > Modules section and find the WebDAV Module in the list of Available Modules.
Click the install button and follow the on-screen instructions.
Once installed, you need to enable it. This can be done on the WebDAV configuration page of the Admin section.
After you have enabled the module, you can also make some additional adjustments, such as:
In order to connect to activeCollab via WebDAV you will need to use a WebDAV client (program). Two of the most common clients are OSX Finder and Windows Explorer. In addition any FTP program can also be used as a WebDAV client.
The connection settings you will need are:
Connect with OSX Finder
Insert the URL and click connect. When prompted, insert your activeCollab email and password.
Connecting with Windows Explorer
Important note: Windows Server 2008, Windows 7 and Windows Vista will all fail to connect to the WebDAV server when using basic authentication. Since the WebDAV module uses basic authentication as standard, in order to use it on these operating systems you will need to apply the following workaround.
Here's how you can connect to WebDAV by using:
When prompted, insert your email and password credentials.
Using WebDAV module on PHP CGI Server API
If your PHP server runs on CGI Server API you will need to insert this code into .htaccess file in /public/ folder (if there is no such file, you will need to create it):
<IfModule mod_rewrite.c>
RewriteEngine on
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization},L]
</IfModule>
To check if your PHP server runs on CGI, please run this PHP code:
<?php phpinfo(); ?>
Search for Server API column:
If you see “Apache” right next to “Server API” that means your PHP is running as an Apache Module, if you see “CGI” right next to “Server API” that means your PHP is running as a CGI module.
In this section you can learn how to upgrade your copy of activeCollab to the latest release.
Upgrading from activeCollab Small Biz to activeCollab Corporate can be done at any time. Once you're ready to upgrade, just carry out the following steps:
1. Upgrade to the latest version of activeCollab
If you are not already running the latest version of activeCollab, please upgrade your setup by following these instructions. In case you are having difficulties finding the version you are running, check this article.
2. Update License File
Download the License file from your activeCollab.com profile (the Download License button is next to the Download activeCollab button) and upload it to your /config folder. There should already be one license.php document. Just overwrite it with the new license file.
3. Get activeCollab Corporate and upload new modules
Visit your profile page on activeCollab.com and download the installation package:
Unpack the installation package and upload new modules to your activeCollab installation. Modules that need to be uploaded are these:
After you upload the new modules, they will be available for installation on the Administration > Modules page.
4. Clear /cache folder
Remove all files with names beginning with cch_ from /cache folder.
In case of any problems, please contact activeCollab support by emailing support@a51dev.com.
Thank you for upgrading!
Please use the following instructions when upgrading activeCollab to the latest release, to keep system downtime to a minimum:
/activecollab and /public/assets are the largest folders and can take a while to upload. That is why we recommended uploading them separately, and later renaming them, instead of overwriting the existing files.
When you've finished the upgrade process, be sure to check everything is working as expected. Once you've verified that everything is up and running, you can delete the old versions of the/activecollab and /public/assets folders, , or keep them for backup, just in case.
This approach was proven to work the best. We also use it when we upgrade activeCollab installations for our customers (as part of our Professional Installation and Upgrade service).
1. Download the latest activeCollab 2.3 release
The latest release or activeCollab can be found on your activeCollab.com profile page. To access this, simply click the My Profile link on the main website administration page after logging in.
The installation package with all the latest files is available by clicking the "Download activeCollab" button below your license details:
2. Upload New Files
Upload all new files that exist in the installation archive, but not in your activeCollab. If any files or folders from the list below already exist on your server, you should replace them:
Please check out this short article to learn how to upload files without making system unusable.
If you are upgrading from a version older than activeCollab 2, you should:
3. Clear Cache
To clear the cache, please delete all cch_ files from /cache and all %% files from /compile folder.
4. Run the Upgrade Script
Go to the /public/upgrade link in your setup (for example, if you have installed activeCollab on www.example.com/projects upgrade script will be located in www.example.com/projects/public/upgrade) and follow the on=screen instructions. In this step, activeCollab upgrade utility will upgrade your database to the latest version.
Please remember this step!
1. Download the latest activeCollab 2.1 release
The latest activeCollab release can be downloaded from your profile page on www.activeCollab.com. To access this page, just click the My Profile link from the main website administration area when you are logged in.
To get the installation package, with all the latest files, just click the Download activeCollab button, below your license information:
2. Upload New Files
Upload all new files. If any files or folders from the list below already exist, just replace them with the new ones:
Please check out this short article to learn how to upload files without making the system unusable.
If you are upgrading from a version prior to activeCollab 2, you should:
3. Clear Cache
To clear the cache, please delete all cch_ files from the /cache folder and all %% files from /compile folder.
4. Run the Upgrade Script
Go to the /public/upgrade link in your setup (for example, if you have installed activeCollab on www.example.com/projects the upgrade script will be located at www.example.com/projects/public/upgrade) and follow the on-screen instructions. During this step, the activeCollab upgrade utility will upgrade your database to the latest version.
Please remember this step!
1. Download the latest activeCollab release
The latest release is available to download from your activeCollab.com profile page:
2. Upload new files
Files and folders that need to be uploaded are:
Please check out this short article to learn how to upload files without making the system unusable.
3. Create new folders
If one of these folders is missing, please created them and make sure that they are writable:
4. Clear Cache
To clear the cache, please delete all cch_ files from the /cache and remove all %% files from the /compile folder.
5. Update Clean URL-s Tweak
If you are using the .htaccess tweak to have clean URLs please update your .htaccess and config files to include rules from this page (thumb.php rule is added).
6. Run the Upgrade Script
Go to the /upgrade link in your setup (for example, if you have installed activeCollab on www.example.com/projects the upgrade script will be located at www.example.com/projects/public/upgrade) and follow the on-screen instructions. In this step, the activeCollab upgrade utility will upgrade your database to the latest version.
Please remember this step!
If you are getting a "System configuration option 'format_datetime' does not exist" error, than your upgrade script is most probably located in /public/upgrade instead of just /upgrade!
activeCollab 0.7.1 and activeCollab v2.x are entirely different systems and so a direct upgrade is not possible. Due to the incompatibility of the Importer module with activeCollab v2.x, the data from activeCollab v0.7.1 first needs to be imported into v1.0.6. After you have import your data into this version of activeCollab, you can then upgrade to the latest release.
Here's what you need to do to get from activeCollab 0.7.1 to activeCollab 2.x:
Move Files from the Database to the File System
By default, activeCollab 0.7.1 stores files in the database. In order to move them to activeCollab 1.0, they need to be available on the file system. We have provided a script that can move them for you, just follow these steps:
blob2fs.php tool moves 1 file per second. When a file is moved, the page will refresh and start moving the next file. This way the large files can be moved without causing memory problems.
Download and Install activeCollab v1.0.6
You can download activeCollab v1.0.6 from your www.activeCollab.com profile page, it will be available in the Additional Downloads section:
Once you've downloaded it you can install it using the installation instructions in this article.
Install Importer Module
Download the Importer module and install it as follows:
Import Companies and Users
Once the Importer Module is installed, you will find it under Administration > Tools. Start by importing Companies and Users. Click the Companies and Users icon, insert connection parameters for the activeCollab 0.7.1 database and click the Submit button.
Import Project Data
After you have imported Companies and Users, you can start moving your project data from the old setup. To do this click the Projects, Milestones, Tasks... link and provide connection parameters for the old activeCollab database.
Note: You will need to provide the full path to the folder where the old activeCollab files are located. To find out the exact location of the /upload folder in the activeCollab 0.7.1 setup, create a path.php file with the following content:
<?php print dirname(__FILE__); ?>
and save it to the /uploads folder. Then, open it using your web browser and the exact path will be displayed.
The import process can consume a lot of resources, so we don't recommend importing all your projects at once. Instead of importing all of them at the same time, try to import five or less projects at a time. If you receive 'max execution time' or 'memory limit' errors, try importing fewer projects per cycle.
Importer does not remember which projects were imported and so it always shows the full list of available projects.
Uninstall Importer Module
After you finish importing data from the old setup, uninstall and remove the Importer Module because it will cause errors when you upgrade to v2.x.
Upgrade to activeCollab v2.x
Upgrading to the latest release is the final step and the whole process is described at this article.
The tips and advice described in this section will help you to set-up activeCollab in any way you wish.
activeCollab can use three different ways to generate URL-s:
By default, activeCollab uses URLs containing /public/index.php in order to avoid having mod_rewrite as a system requirement. If, from some reason, this system does not work (you get a "No input file specified error", for example) or you just want to have a 100% clean URL, then please follow the instructions bellow:
Options -Indexes
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^(.+) - [PT,L]
RewriteRule ^projects_icons/(.*)$ public/projects_icons/$1 [L]
RewriteRule ^avatars/(.*)$ public/avatars/$1 [L]
RewriteRule ^logos/(.*)$ public/logos/$1 [L]
RewriteRule ^thumb.php$ public/thumb.php [L]
RewriteRule ^captcha.php$ public/captcha.php [L]
RewriteRule ^$ public/index.php [L]
RewriteRule ^(.*) public/index.php?path_info=$1 [L]
</IfModule>
define('ROOT_URL', 'http://projects.example.com/public');
make it:
define('ROOT_URL', 'http://projects.example.com');
define('URL_BASE', ROOT_URL . '/');
define('ASSETS_URL', ROOT_URL . '/public/assets');
define('PATH_INFO_THROUGH_QUERY_STRING', true);
and remove or comment it. To comment a line in the PHP configuration file, just add // in front of it:
// define('PATH_INFO_THROUGH_QUERY_STRING', true);
IIS7 rewrite module features a tool that lets you easily import Apache mod_rewrite rules. Please check this article for details:
http://learn.iis.net/page.aspx/470/importing-apache-modrewrite-rules/
Adam Michel sent us set of rules for nginx web server that you might find useful:
if (!-e $request_filename) {
rewrite ^projects_icons/(.*)$ /public/projects_icons/$1 last;
rewrite ^avatars/(.*)$ /public/avatars/$1 last;
rewrite ^logos/(.*)$ /public/logos/$1 last;
rewrite ^thumb.php$ /public/thumb.php last;
rewrite ^captcha.php$ /public/captcha.php last;
rewrite ^$ /public/index.php last;
rewrite ^(.*) /public/index.php?path_info=$1 last;
}
This works with activeCollab 2.1 or newer, so please make sure that you have the latest version running on your server.
activeCollab is designed to be simply dropped in a subfolder and installed. On the other hand, you can have a more advanced setup where only the content of the /public folder is publicly available while everything else is behind the document root and inaccessible (ie. inaccessible).
To show you how this other type of setup works, we'll define a virtual host that maps http://intranet to the public folder of our activeCollab setup:
<VirtualHost *> ServerName intranet DocumentRoot /Library/WebServer/Documents/intranet/public </VirtualHost>
The content of the /intranet folder should look like this:
In order to install activeCollab, we'll run http://intranet/installer. Note that the installer will not let us use http://installer as an absolute URL. Instead, we'll use http://intranet.site and change that value when the installation was successful in config/config.php.
When the installer shows us that activeCollab is successfully installed, we should delete the /installer folder from the /public folder and then check our setup. Everything should be working fine, even if only the /public folder is publicly available.
When you're applying this method, please note that:
activeCollab does not set any limit on the size of files that you can upload, but limitations are enforced by your web server. The "Max total size of files you can upload..." message in your edition of activeCollab (below the File and Attachment upload forms) displays the current limit enforced by the web server you're using:
To increase the max upload size, open php.ini file and change values of upload_max_filesize and post_max_size directives to value that suits your needs. For example:
upload_max_filesize = 64M post_max_size = 64M
Save php.ini and restart your web server. If you don't have access to php.ini, contact your system administrator or hosting provider to increase these values for you and point out that they need to be applied to the /public folder.
Apache has a LimitRequestBody configuration directive. It restricts the size of all POST data regardless of the web scripting language in use. You might need to update this value, too.
By default, activeCollab uses the MySQL FULLTEXT index for search, which works well, but in some cases MySQL can be configured not to index words shorter than 4 characters. To correct this and configure MySQL to index three-letter words (it's not recommended to go shorter than three characters), you will need to set the value of ft_min_word_len directive in your my.cnf file:
[mysqld] ft_min_word_len=3
After you're finished, restart your MySQL server and rebuild the FULLTEXT index by dropping and creating the index on the content field in the search_index table:
ALTER TABLE `acx_search_index` DROP INDEX `content`); ALTER TABLE `acx_search_index` ADD FULLTEXT ( `content`);
If you wish to find our more information about the fine-tuning MySQL FULLTEXT search, you can found it at this section of the MySQL documentation.
You are free to move your installation of activeCollab from it's original server to a new one at anytime.
To do so, just follow this step-by-step guide to make the moving process as fast and as easy as possible:
First, you will need to ask for URL change approval from your activeCollab.com profile page. To do that you need to:
The approval of your new URL will be made automatically. In case you wish to change your URL more than once in 24h, the system will notify our team, and they will approve it manually as soon as possible. In any case, you will get the notification that your request has been processed.
Once a URL change is approved, you should install a new copy of activeCollab on your new server. The best way to do this is to install a completely fresh version of activeCollab using a new license downloaded from your www.activeCollab.com profile page.
Make sure that you use the same table prefix that you used for your original setup (usually it is "acx_").
When your installation URL change is approved and you have a fresh copy of activeCollab running on your new server, you are ready to move the data from your old setup.
First, drop all activeCollab tables that the installer has created on your new database. Now export the tables and data from the old setup, and then import it into a new database. You can do this by using your favorite MySQL administration tool (phpMyAdmin, command line MySQL client, Navicat, etc).
This short video (QuickTime Movie, 2MB) shows how you can do this in a three simple steps using phpMyAdmin: select a database, on the export tab make sure that all activeCollab tables are selected, and save them as a file.
When you have migrated database tables from old setup to the new one, move content of the following folders to the new server:
activeCollab stores your binary data in those folders - images, uploads, etc, so don't forget to move them, too.
When uploading images, avatars etc from your old setup, make sure that you use Binary transfer mode in your FTP client. Using ASCII mode may result in corrupt files afterwards.
Now that the files are moved, please check the permissions and make sure that all existing files are writable by PHP. If these files are read only, you'll not be able to update them.
That should be it. If you have any questions or you have experienced any problems with moving your activeCollab, please do not hesitate to contact our support at support@a51dev.com.
If you have any problems with your everyday work on activeCollab, you may find a solution using one of these articles. We have described some of the most common issues and their solutions here to save you time if you experience any difficulties. For everything else, feel free to contact our support team on support@activecollab.com and we will help you as soon as possible..
activeCollab can run in three different modes, based on the value of the DEBUG directive. Possible values are:
When troubleshooting, you should raise the debug level to 2. Open the config/config.php and change the value of the DEBUG directive to 2. If the DEBUG directive is not present in config/config.php, then you can add it yourself by adding the following line to the file:
define('DEBUG', 2);
It is strongly recommended that you use debug mode only for debugging. When you are done debuggin, revert the value back to 1 to avoid revealing any sensitive information to the users within your activeCollab.
Mailing is one of the most important features of activeCollab. In this article you'll find instructions on how to check if mailing is working properly and how emails sent by the system look like.
Firstly you should check if activeCollab can connect to the server and send out an email.
There are two ways for activeCollab to send an email:
After a successful installation, Native Mailer is selected by default, so mailing should work properly if it is configured in php.ini. On the other hand, if it is not configured, you'll need to provide SMTP connection parameters. To check if the SMTP parameters you have provided are good and the system can connect to the server, use the Test Connection button on the Mailing page.
Once you have configured email settings on the Administration > Mailing page, the next thing you should do is to send out test emails. There is a tool available in Administration called Test Mailing Settings. Using this tool, you can write a message and send it to a specified email address.
If everything works properly, you have successfully set-up mailing.
When email is properly configured and messages are successfully sent using the Test Mailing Settings tool, you may wish to see how notifications sent by activeCollab look like. To do this, you'll need two separate user accounts. This is because activeCollab never sends notifications to the same person who executes the action.
If, for example, you post a comment to a ticket you'll not receive a notification about it even though you are subscribed. As it was you that posted the comment, there's no need for activeCollab to notify you. On the other hand, all other subscribers will receive email notifications about the new comment.
To test email notifications, create a new ticket and select another account for you to use as a test assignee. Once the ticket is created, an email with the details about the ticket should be sent to the other user account you used for testing.
If activeCollab behaves differently to anything described above, please contact us at support@activecollab.com. and we'll help you find a solution as soon as posible.
The most common cause of problems within activeCollab is file and folder permissions. Improperly set permissions can result in various issues:
To resolve these issues, please make sure that PHP can write to all the folders listed below. These folders need to be writable for activeCollab to work properly:
PHP limits the amount of memory available for execution of a script. This is controled by memory_limit configuration option.
By default, memory_limit is set to 8MB. If the script tries to allocate more memory, PHP will display a fatal error that looks something like this:
Fatal error: Allowed memory size of N bytes exhausted (tried to allocate M bytes) in FILE on line #.
To get around this error, you will need to increase the PHP memory limit and make more room for executing the application.
To do that open php.ini file, find a line where memory_limit option is defined and change it to a higher value. Although 8MB is enough for most activeCollab requests, in some cases activeCollab will need more memory, especially when working with images. Because of that, we recommend memory limit to be set to 64MB.
The line where memory limit is defined will look like this:
memory_limit = 64M
Once you have made the change, save the php.ini file and restart your web server.
On some servers you will not be able to change php.ini file by yourself. In that case, please contact your system administrator or hosting provider in order to make this change for you.
Thumbnail creation for images was introduced in activeCollab 1.1. It is enabled by default. It automatically resizes images (JPG, GIF and PNG) smaller than 1MB and enables users to see a preview without downloading the original file. This caused problems on some setups where the recommended 64MB memory limit was not high enough for the resize operation to be performed.
The fix for this issue was introduced in activeCollab 1.1.1. From this release you can set the max size of images that will be resized (default is 500kb) or completely turn off thumbnail creation.
Now, in config/config.php you can define two new configuration options:
define('CREATE_THUMBNAILS', true);
define('RESIZE_SMALLER_THAN', 1048576);
Login problems are usually caused by one of the following reasons:
Please read the following for more details on each of the possible reasons.
If activeCollab is persistently stating that your login data are not valid, then they most probably are not. Use the Forgot Password utility to have your password emailed back to you.
If the email address provided in the Forgot Password form does not exist in the system though a notification is displayed by the system explaining that you have input the wrong email address.
Since version 2.1.4, activeCollab uses only cookies to track user's session data. In some instances, especially in situations when activeCollab is hosted on your own computer (on localhost or other virtual host), this can cause some difficulties.
The problem is that the system accepts your user credentials, but returns you back to login page without displaying any error message. To work around this, open config/config.php and add the following line in the section where all the other configuration options are defined:
define('COOKIE_DOMAIN', '');
Then save and close config/config.php file and try to login again. If that does not help, please contact support by sending an email to support@a51dev.com.
If activeCollab does not log you in, but instead keeps redirecting you back to the login page (without displaying any errors), then it also could be a problem with your PHP session handling. These issues are easiest to resolve by switching to debug mode and looking for PHP errors in the logs or on the screen.
If you can't solve the issues highlighted in the error messages, feel free to contact our support team at support@a51dev.com. and send us the error reports, and we'll help you as soon as possible.
Usually, two situations may lead to a problem with Remember me functionality:
activeCollab uses file system on your server to store uploaded files, as well as to cache data. Usual indicator of your disk being full (or upload quota of your hosting package reached) is this error:
Owner company is not defined
System throws this error when it cannot load or write cache file when it tries to catch owner company information. This does not mean that data in the database is not present, or that it is corrupt, just that activeCollab is not able to work with cache because there's not enough free space.
Solution for this problem is to free up some space on your server.
Apart from removing files that are not activeCollab related, but take up space, you can also remove:
In case you confirmed that you have enough free space on your server or hosting package, but still receive the same error, please submit a support request, and our support team will take a look.
activeCollab is dependent on database which stores your project data. If it fails to connect to the database, it will send a crash report to the Administrator or display an error message when it is in Debug mode.
Although it happens rarely, your first option that should be check is if your database connection parameters or database name has been changed since you set-up the system. To resolve this, open config/config.php and update the connection parameters:
define('DB_HOST', ''); // MySQL server hostname, usually localhost
define('DB_USER', ''); // User that you're using to connect to database
define('DB_PASS', ''); // User's password
define('DB_NAME', ''); // Name of the database where activeCollab is installed
But ut is more likely that your database is just temporally unavailable, , and this issue will be solved eventually by your hosting provider.
The database may be unreachable for many reasons: MySQL server is down or restarting; maximum number of open database connections is reached and activeCollab's request to connect was rejected; etc. All of these situations are outside of application's control and can't be fixed by activeCollab, and that's why it simply stops running and sends or displays a crash report.
If you are receiving these crash reports frequently, we recommend that you contact your hosting provider and ask for assistance.
MySQL is like any other software running in a complex environment. It is known for its stability, but sometimes database tables may crash or get corrupted because of a number of reasons.
When something like this happens, you will get crash reports with information that a query failed because of a missing file or because of invalid information in one of the files. Exact error messages may vary and the following is just one example:
Query failed with message 'Incorrect information in file: './db_name/ac_user_sessions.frm''
The first step that you should take if you start receiving such crash reports is to try to repair the table. Here's how you can do that with phpMyAdmin:
If the Repair command fails to resolve the problem, you should contact your hosting provider or system administrator for assistance.
activeCollab works on MySQL5, but you may experience problems on some rare situations if you have it running in strict SQL mode. It is advised to use a less strict SQL mode (MYSQL40 mode is recommended).
There are two ways to change the value of SQL mode preference:
SET @@global.sql_mode='MYSQL40'
sql-mode="MYSQL40"
You should then save the my.cnf file and restart the MySQL server.
To verify that the SQL mode has been updated, execute the following command:
SELECT @@global.sql_mode;
MySQL should then return something like this:
NO_FIELD_OPTIONS,MYSQL40,HIGH_NOT_PRECEDENCE
Licensing:
Enhancements:
Bug Fixes:
Enhancements:
Bug Fixes:
Enhancements:
Bug Fixes:
Bug Fixes:
Enhancements:
Bug Fixes:
Bug Fixes:
Enhancements:
Bug Fixes:
Enhancements:
Bug Fixes:
Security:
API Changes:
Enhancements:
Bug Fixes:
Enhancements:
Bug Fixes:
Enhancements:
Bug Fixes:
Enhancements:
Bug Fixes:
Enhancements:
Bug Fixes:
API Changes:
Enhancements:
Bug Fixes:
Enhancements:
Bug Fixes:
Enhancements:
Security:
Bug Fixes:
Enhancements:
Security:
Bug Fixes:
API Changes:
New Module - Incoming mail
Read more about Incoming Module module in this blog entry.
New Module - Documents
Read more about Documents module in this blog entry.
Pages Module Overhaul
Read more about Pages module improvements in this blog entry.
Improved tasks and checklists
Improved Dashboard and Project Overview
Improved people section
Other system improvements
and many, many more changes.
Enhancements:
Bug Fixes:
API Changes:
Enhancements:
Bug fixes:
API improvements:
Enhancements:
Bug fixes:
AP I improvements:
Enhancements:
Bug fixes:
API improvements:
Enhancements:
Bug fixes:
New modules:
Time tracking improvements:
Improved assignments page:
Calendar improvements:
Improved search:
Localization support:
New permissions and roles:
File module improvements:
API improvements:
Reminders:
Other changes:
Plus many many more fixes and improvements.
Enhancements:
Bug fixes:
Bugs fixed:
Features and Improvements:
Bug fixes:
Bug fixes:
Features and Improvements:
Bug fixes: