A few weeks ago we released the 1.7.2 version of GemsTracker. We moved from SourceForge to GitHub and instead of subversion externals we now use composer to handle dependencies. Because of this we decided to split the project in different sub projects. Upgrading will be a little bit different than before so make sure to read the changelog before you start. Since a lot of changes were made to the config files, starting with a fresh installation and copying over your own code is the easiest way to do an upgrade.
A special warning about our template system: we will probably stop supporting templates that do not make use of the bootstrap layouts. Keep an eye on the new-project on GitHub to see what we are doing.
The full list of issues solved with this release can be found on our BugTracker where you can also report issues you find with this release. Due to some issues found after release we are considering to release the first patched version soon. Keep an eye on our releases page on GitHub to see what is the latest version.
A long time has passed since the last update. We did a few releases but did not take the time to write a message about it. Today the demo site was updated to have the last released version (1.7.1p4), and we updated the download section to provide this latest release. An overview of what has changed can be found in the changelog.
Starting with the next version we will be moving our code to GitHub to make it easier to contribute to the project.
When you find bugs or encounter problems, please file a report in our bugtracker. Contributions to the documentation are greatly appreciated and we are more than happy to review your proposed changes!
After the official 1.6.4 release we fixed a lot of bugs and also fixed some security issues. Because of this we did a silent release of 1.6.4+ to indicate that the features are all the same but it is improved over 1.6.4
We are now thinking of a better naming scheme for this patched versions and for now this resulted in 1.7.0p1 for patchlevel 1 that is available for immediate download at SourceForge. We decided to go from 1.6.4 to 1.7.0 because of some major changes. Read more about that in the release notes.
On a side note we found out that Zend Framework 1.12.8 broke compatibility with some of our SQL statements. So if you upgraded to a newer Zend Framework version and encountered problems, all should be fixed by now in 1.7.0p1
And as always: when you find bugs or encounter problems, please file a report in our bugtracker. Contributions to the documentation are greatly appreciated and we are more than happy to review your proposed changes!
Yesterday we made the library and new project file for 1.6.4 available for download at SourceForge. It took a while but we have some great new features for you:
- Import functionality for Respondents, Appointments and Answers
- A project can define default track fields to be added to all new tracks
- Two new track field types were added: caregiver and treatment, both linked to appointments
- It was made easier to add other track field types at project level
- Easy customization of site template using Less
- OpenRosa surveys now can use geopoints, images and one repeating group
- And of course some bugfixes
Because of code changes in the library existing projects need to be careful when upgrading. Check the release notes carefully before upgrading and perform the search and replace code edits described there. If you find any problems, please report them in our bugtracker.
As always: we try to do out best to keep things understandable but if you get lost or feel information is lacking in the documentation please feel free to give us a shout or (preferably) add some information to the wiki yourself!