You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since Statamic uses UUIDs within content files by default, we provide two solutions depending on whether you need to use existing content.
21
21
22
22
23
-
### Fresh install of [statamic/statamic](https://github.com/statamic/statamic)
23
+
### Fresh install of [statamic/statamic](https://github.com/statamic/statamic) (using incrementing ids)
24
24
25
25
If you're starting from scratch, we can use traditional incrementing integers for IDs.
26
26
@@ -29,7 +29,7 @@ If you're starting from scratch, we can use traditional incrementing integers fo
29
29
- Copy the `create_entries_table` migration into `database/migrations`.
30
30
- Run `php artisan migrate`.
31
31
32
-
### Starting from an existing site
32
+
### Starting from an existing site (using UUIDs)
33
33
34
34
If you're planning to use existing content, we can use the existing UUIDs. This will prevent you from needing to update any data or relationships.
35
35
@@ -41,4 +41,4 @@ If you're planning to use existing content, we can use the existing UUIDs. This
41
41
42
42
## Known issues
43
43
44
-
When saving a collection or reordering entries, the URIs of all entries in the collection will be updated, even if they haven't changed. This is an intensive operation and will be addressed in a [future version](https://github.com/statamic/cms/pull/2768) of Statamic.
44
+
When saving a collection or reordering entries, the URIs of all entries in the collection will be updated, even if they haven't changed. This is an intensive operation and is being addressed in a [future version](https://github.com/statamic/cms/pull/2768) of Statamic core.
0 commit comments