Differences

This shows you the differences between two versions of the page.

--- devzone:releasenotes [2013/08/01 10:01]
menno [Version 1.6.1]
+++ devzone:releasenotes [2020/03/12 12:06] (current)
@@ Line 1: / Line 1: @@
 ====== Release notes ======
+This project is now on GitHub so latest information and release notes can be found there:
+[[https://github.com/GemsTracker/gemstracker-library/releases]]
 ===== Latest commits =====
-{{rss>http://gemstracker.org/websvn/rss.php?repname=GemsTracker&path=%2F&isdir=1&}}
+{{rss>https://github.com/GemsTracker/gemstracker-library/commits/master.atom}}
+===== 1.7.0p1 =====
+-01-30
+  * Appointments can be used to create tracks
+  * Appointments can be linked automatically to track fields
+  * New track field overview
+  * New track fields changed events
+  * Layouts can use bootstrap for styling
+  * Improved security means users may get error warnings when opening the same form in two windows.
+  * Password fields for login to sources, mail servers and security devices are now encrypted reversible
+  * X-frame setting in project.ini allows defense against clickjacking
+  * Project and application programmers can use PHP namespaces instead of Zend FW 1 class names.
+===== 1.6.4 =====
+-06-26
+  * Errors in token events are less likely to cause the application to halt
+  * OpenRosa forms can now handle geopoint (location) fields, has support for displaying uploaded images and provides a datelist to use in tracks
+  * Default track fields can be added to a new track by adapting the TrackModel in your own project and changing the getDefaultFields() method
+  * Projects can define project specific track field types
+  * Added the new track field types: location and caretaker. These fields can be filled automatically using one or more appointments
+  * Export results can now be filtered by round description too
+  * The number of reminders no longer includes the first non-reminder mail
+  * To make use of the configurable Less templates, make sure to update your project.ini and change the .css files to .less when available in your template
+  * Form and table bridges have changed. Perform the following search & replaces on your code:
+<code>
+    MUtil_Model_FormBridge::          => MUtil_Model_Bridge_FormBridge::
+    MUtil_Model_FormBridge            => MUtil_Model_Bridge_FormBridgeInterface
+    MUtil_Model_VerticalTableBridge   => MUtil_Model_Bridge_VerticalTableBridge
+    MUtil_Model_TableBridge           => MUtil_Model_Bridge_TableBridge
+    Gems_Model_ThreeColumnTableBridge => Gems_Model_Bridge_ThreeColumnTableBridge
+</code>
+===== 1.6.3 =====
+-03-06
+  * Menu structure has changed: to avoid nesting problems and issues with bread-crumb navigation edit and delete actions are now children of the show action
+  * Track fields split in fields and appointments: check any code using any track field tables directly, track field id's are no longer integers and getFieldsElements() is no longer in use
+  * GemsEscort->tokenMailFields() no longer exists
+  * Tracks can use appointments instead of date fields: when an appointment is changed then the linked track is changed as well
+  * The token overview can also be filtered on missing or incorrect email addresses and on hover each token shows it's comment
+  * The token mail communication is reset if a new valid until date is later than the last sent email date
+  * Sending emails can be blocked on per respondent or per track
+  * Added a send mails overview for each respondent
+  * Manual token and track date changes are no longer overruled by recalculations
+  * The end date of the track is filled as soon as all tokens in a track are completed or have a valid until date
+  * Logging the respondent in respondent controller restored. Action respondent.show logs without, but respondentShow will log respondent id
+  * A new respondent status overview tracks the intake of new respondents
+  * A required valid until definition for each track round can be set at the project level - for new projects this defaults to ON
+  * Support for LimeSurvey 2.05
+  * Limesurvey fieldtype list with comment no longer appends underscore to the fieldname, this might break existing calculation scripts
+  * The track editor shows more information on the rounds per track
+  * Fixed several bugs, including one that added an extra day to some valid until dates
+===== 1.6.2 =====
+-01-06
+  * Agenda and calendar screens added to version
+  * Mail templates for staff members, respondents, users, etc... possible
+  * Multi language mail templates with wysiwyg editing
+  * Barcharts functionality added
+  * Improved import scalability
+  * Role management has a better display interface
+  * Batch commands now also run from the command line
+  * Core gems css settings moved to shared gems-core.css
 ===== Version 1.6.1 =====
 -08-01
   * Added support for ODK Collect by adding OpenRosa support
-  * Added support for data-mining by enabling the storage of all response data in a separate table with one answer per row
+  * Added support for data-mining by enabling the storage of all response data in a separate table with one answer per row. To use it check the new project.ini responses setting (can be copied from configs/project.example.ini):
+<code ini project.ini>
+;----------------------------------------------------------------------
+; RESPONSES SECTION
+;
+; If responses.adapter is set, then all answers for tokens are stored
+; in the gemsdata__responses table.
+;
+; All params responses fields can be used to overrule the database
+; connection settings specified in application.ini/resources.db.
+;
+; If no adapter settings are specified then the default db adapter is
+; used but the advise is to put this data at the very least in it's
+; own database so the table specific logging and replication settings
+; can be changed.
+;----------------------------------------------------------------------
+;responses.adapter = Mysqli
+;responses.params.charset = utf-8
+;responses.params.host = HOST
+responses.params.dbname = DATABASE "_data"
+;responses.params.username = USER
+;responses.params.password = PASSWD
+</code>
   * Export data now operates in batch mode, allowing bigger exports and combining spss files in one download
   * Import is possible for most data screens, though respondent import is the only one tested thoroughly.

GemsTracker

User Tools

Site Tools

Differences

Page Tools