We're updating the issue view to help you get more done. 

Schedule start and end times incorrect migrating from 1.6 to 1.7

Description

Existing installations upgrading to 1.7 from 1.6 may find that:

  • Schedules don't display correctly; and

  • when editing the Schedule from Administration|Organisation it has Start Time and End Time fields like: 365337:00

The Start Time and End Time properties are stored in the database as date/times and must be relative to 1970-1-1.
Existing installations may have later dates. These can be corrected manually, or by running the following script:

1 2 3 4 5 6 7 UPDATE entity_details d, entities e SET d.value = concat("1970-01-01 ", substring(d.value, 12, 5), ":00"), d.type = "sql-timestamp" WHERE substring(d.value, 1, 10) NOT IN ("1970-01-01", "1970-01-02") AND e.arch_short_name = "party.organisationSchedule" AND e.entity_id = d.entity_id AND d.name IN ("startTime", "endTime");

Environment

None

Status

Assignee

Tim Anderson

Reporter

Tim Anderson

Labels

None

Components

Fix versions

Affects versions

1.7

Priority

Minor