Error: WEB-INF/config.php File Does Not Start with a PHP Opening Tag
For Time Tracker to function properly, its configuration file WEB-INF/config.php must exist and start with a PHP opening tag without any white space or hidden characters in front of the tag.
If you are using a Unicode text editor to create the file by copying it from WEB-INF/config.php.dist, it may insert an invisible byte order mark (BOM, a Unicode character U+FEFF) at the beginning of the file. The file looks normal in the editor and shows that it starts with <?php, but there is actually something in front of the tag, which breaks things.
An environment check on top of dbinstall.php page may show an error like this. Environment check in Time Tracker showing PHP opening tag error
Using such configuration file has the following effect:
BOM is printed as white space on pages.
It may break PHP redirects, depending on server settings. For example, after a successful login you are redirected to time.php to work with the system. Redirects are also used in other places in Time Tracker. When redirects are not working, Time Tracker is not usable. You may see blank pages.
It will break PDF reports and attachment downloads. Downloaded files, generated with extra white space, are not usable (you cannot open such files).
How to Fix
Either examine the beginning of the config file with a binary (hex) editor and remove any leading characters before <?php tag or use another, non-Unicode editor to create the file.
MDB2 Error: Connect Failed
If you see the MDB2 Error: connect failed error in Time Tracker it means that it cannot connect to the database. To troubleshoot and fix the connection problem, make sure that:
MySQL or MariaDB is installed and working properly.
The DSN value in WEB-INF/config.php file is correct.
Error: Database Schema Version Query Failed
This error shows up on Time Tracker dbinstall.php page in the Environment Checks section when it cannot determine database schema version. Technically, it is done by querying the version_db parameter in tt_site_config table. You would see this error if either the table, or the parameter do not exist. Most likely scenarios for seeing this error are:
You have a brand new database without any tables in it at all. To fix it: create the database structure by executing the Create database structure step in dbinstall.php.
This error may show up on Time Tracker when it tries to query a certain table in database while it does not exist. There are two most common scenarios for seeing this error.
The existing database structure is out of sync with Time Tracker code. For example, you attempted an upgrade, upgraded the application code but did not update the database structure. New code operates with a new table that does not exist in the old database. This can be fixed by running database update steps in dbinstall.php that apply to your old application version.
The database is completely empty without any tables in it. For example: you have created the database but did not run database population script that creates database structure in dbinstall.php. This can be fixed by running the Create database structure step in dbinstall.php.
Your Database Is Empty
The error Your database is empty. Login as admin and create a new group. shows up on the Login page in Time Tracker when MULTIORG_MODE is disabled in config.php and there are no user accounts in the database. Your database is empty error in Time Tracker
This error means that nobody but site admin can login.
Note that when MULTIORG_MODE is enabled then users can self-register (create new groups and user accounts) with Time Tracker. But when it is disabled it is up to site administrator to do so.
How to Fix
There are 2 ways to fix Your database is empty error.
Login as site administrator and create a new group.
Enable MULTIORG_MODE temporarily. Let users to self-register using the Register link in menu. Then disable MULTIORG_MODE.
PHP Extension 'mysql' Is Required but Is Not Loaded
This error is likely to show up when your DSN in config.php file uses mysql prefix but php is not configured to use mysql extension. One of potential scenarios leading to this error is migrating from older Time Tracker installations that was relying on mysql instead of mysqli without updating your DSN.
How to Fix
Try to change mysql prefix in DSN to mysqli and make sure that mysqli extension is enabled in php.
