migrator
migrator copied to clipboard
statamic
Migrate from Statamic v2
This pull request adds Statamic 5 support to the v2 Migrator package. ## To Do * [x] Get the tests passing * [x] Migrate `statamic.system.multisite` to `true` when `Site::hasMultiple()` -...
I am getting this error Call to undefined method Statamic\Query\StatusQueryBuilder::toArray() when visiting the frontend after using the migrator to upgrade a v2 to v4. Any idea why?
Just noticed a conditional check wasn't migrated correctly to a boolean value. In v2: ```yaml show_when: schedule: true ``` In v3: ```yaml show_when: schedule: '1' ```
In v2 `allow_time` was default `true`, but in v3 `time_enabled` is default `false` - migration should account for this to prevent loss of data precision.
I upgraded a Statamic website from version 2.11.21 to 3.3.68 using the Statamic migrator. Upon checking the dashboard, I noticed that all elements appear to have been successfully migrated on...
In v2 our `site/settings/system.yaml` has these locales: ```xml locales: da: name: Danish full: da_DK url: "{env:APP_URL}/" en: name: English full: en_US url: "{env:APP_URL}/en/" sv: name: Swedish full: sv_SE url: "{env:APP_URL}/sv/"...
In v2, a localized entry has the same ID as the default language. In v3, each entry has a unique ID. Great. When migrating a multisite, all the localized entries...
When a `sub-folder` is created in a folder like `BlogImages`, the sub-folder is created in a new directory of `blogimages/sub-folder`, apparently causing issues with linked assets after a migration?
If you have custom translations files located in `site/lang` they aren't copied to `resources/lang`.
thanks for this amazing migrator. it helped a lot! i ran into a bug which was hard to track down for me - maybe you can look into it. v2...
