Check if this happens on date catalogue fields as well

Automated response: CPF and catalogue date and date_time fields do not handle time zones properly

The date and date_time fields used in CPFs and in catalogues did not properly handle time zones. This resulted in some weird conversions and changes to the values when going in to edit an entry (or a profile).

This hotfix applies the following changes:

* The date field no longer respects time zones (we can't because dates are always midnight which causes some weird behaviour)
* The date_time field is now the only date-based field that respects time zones; this is indicated when selecting a field type.
* The date_time field will take input in the user's time zone, save as UTC in the database, and render as whichever time zone the viewer is in.

A hotfix (a TAR of files to upload) has been uploaded to this issue. Only apply this hotfix if you absolutely need it and cannot wait until the next release of Composr (releases are more reliable and strictly tested). As of Composr version 11, the recommended way to apply a hotfix is by following the same steps as an upgrade (https://baseurl/upgrader.php, use the hotfix on the step “Transfer across new/updated files”). The upgrader will automatically skip files belonging to addons you do not have installed or that are newer on disk than in the hotfix. Otherwise, you can manually extract and replace these files (do not replace if your on-disk file is newer than the one in the hotfix). Always take backups of your site or at least files you are replacing before applying a hotfix. Not sure how to extract TAR files to your Windows computer? Try 7-zip (http://www.7-zip.org/).