| Summary | Typo in DB migration 24 |
| Queue | Kronolith |
| Queue Version | Git master |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | |
| Requester | dix (at) uni-koeln (dot) de |
| Created | 10/25/2019 (2077 days ago) |
| Due | |
| Updated | 10/27/2019 (2075 days ago) |
| Assigned | |
| Resolved | 10/27/2019 (2075 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
This column is changed in the next migration to the current name
of calendar_type. This was a search/replace error.
State ⇒ Resolved
calendar_type is actually the correct name of the attribute, as that
is what kronolith currently uses to access that. The name is
corrected/changed in the following migration. This was probably
inadvertently changed during a search/replace when the field name was
changed.
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Queue ⇒ Kronolith
Summary ⇒ Typo in DB migration 24
Type ⇒ Bug
State ⇒ Unconfirmed
$share->set('calendar_type', Kronolith::SHARE_TYPE_RESOURCE);
Should be:
$share->set('type', Kronolith::SHARE_TYPE_RESOURCE);
DB migration throws error with "QUERY FAILED: Unknown column
'attribute_calendar_type' in 'field list'"