Version 1.1.10

Adjustments

Adjustments in Helpdezk core

• The pipeTableExists function was previously used, however in some versions of mysql case sensitive problems were reported in the function names. Then, we replace it with a query.

• Version 5.7. * of mysql sets the sql_mode parameter to STRICT_TRANS_TABLES by default. This makes it impossible to use a datetime value of '000-00-00 00:00:00'

  Strict mode affects whether the server permits '0000-00-00' as a valid date: If strict mode is not enabled, '0000-00-00' is permitted and inserts produce in the warning. If strict mode is enabled, '0000-00-00' is not permitted and inserts produce an error, unless IGNORE is given as well. For INSERT IGNORE and UPDATE IGNORE, '0000-00-00' is permitted and inserts produce a warning.

  To solve the problem, just remove the STRICT_TRANS_TABLES from the sql_mode parameter. However, some users do not have access to mysql.ini, or permission to set in real time, so we created a workaround, changing the example record in the bbd_tbmessage table.

Version 1.1.9

Adjustments

Adjustments in Helpdezk core

• Fixed several language issues in the English version.

Version 1.1.8

New features

Created the vocabulary feature:

• Program to register the key names for each language;
• Tables for storage of locales and vocabularies;
• Program for reading the language tables and translating the files used by Smarty in a multi-language environment.

Added new features in Helpdezk core

• Added a token to the operator's link so that he can login to the system even if he is not connected. Several methods were also changed and a table added to the database (hdk_tbviewbyurl);
• Dashboard creation with user statistics.

Adjustments

Adjustments in Helpdezk core

• Added test on line 151 of cronGetEmailController.php for customers using only one user to create email request;
• Create appspec.yml to be used by AWS Code Deploy.

Fixed bugs

• Fixed language issue on user's dashboard;
• Prevention of XSS and Sql Injection in some forms;
• Fixed programs permissions issue;
• Fixed sql injection problems in admin module;
• Fixed method datepickerSettings in system.php;
• Fixed the problem with the user link used in the email template;
• Change in the pipeDateTime class to correct problems with multiple languages.

Version 1.1.7

New features

Added an integration API

In this release an API (Application Programming Interface) is added for integration with other software and/or applications.

Added wiki page

Wiki with instructions for using the API. Available at: https://github.com/albandes/helpdezk/wiki

Version 1.1.6

New features

Added new features in Helpdezk core

This release prepares helpdezk for use in high availability environments.

The app/uploads directory can now be used outside the helpdezk's path, an AWS S3, for example.

3 new entries were introduced in config.php, to set the external storage:

$ config ['external_storage'] = false;
$ config ['external_storage_path'] = " ";
$ config ['external_storage_url'] = " ";

The installer program was alter to attend this new feature.

Version 1.1.5.6

Fixed bugs

Bug in admin module - left menu

Fixed admin logo issue on left menu

Version 1.1.5.5

Fixed bugs

Bug in admin module

Fixed admin logo issue

Version 1.1.5.4

Fixed bugs

Bug in installer

Fixed database installation bug.

Version 1.1.5.3

Fixed bugs

Bug in read version.txt

To define the default state, a session variable is used. When setting session variables, the getHelpdezkVersion() method is used.
File version.txt had a blank line and this was not being tested by the code, so it returned $ this_version = "".
This error caused the getConfigSession() method to not work correctly, as the version number was undefined.
Replaces fopen with file_get_contents and added several tests to mitigate the problem.

Version 1.1.5.2

Fixed bugs

Fixed some bugs detected in version 1.1.5.1

Logos issue

• The logo table (tblogos) of the installer did not have the columns with the sizes of the logos used. With this it was not possible to register a new logo. The dump was fixed and the insert lines were placed;

• The controller also did not provide for the possibility of not having logos registered, when this happens the logos that are in the folder must be used.