Skip to content

Commit c037147

Browse files
committed
Add docs related to looping ElementalArea relationship
1 parent 47c19ef commit c037147

File tree

1 file changed

+15
-2
lines changed

1 file changed

+15
-2
lines changed

README.md

Lines changed: 15 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ Generate a YAML fixture from DataObjects
1010
- [Set a maximum depth to export](#set-a-maximum-depth-to-export)
1111
- [Excluding relationships from export](#excluding-relationships-from-export)
1212
- [Excluding classes from export](#excluding-classes-from-export)
13-
- [Common errors](#common-errors)
13+
- [Common issues](#common-issues)
1414
- [Supported relationships](#supported-relationships)
1515
- [Unsupported relationships](#unsupported-relationships)
1616
- [Fluent support](#fluent-support)
@@ -156,7 +156,20 @@ App\Models\MyModel:
156156
- FeatureImage
157157
```
158158

159-
## Common errors
159+
## Common issues
160+
161+
### Relationship to ElementalArea missing
162+
163+
TL;DR: There is a looping relationship between `Page` and `ElementalArea` in later versions of Elemental. You can
164+
exclude the `has_one` on `ElementalArea` as follows.
165+
166+
```
167+
DNADesign\Elemental\Models\ElementalArea:
168+
excluded_fixture_relationships:
169+
- TopPage
170+
```
171+
172+
Extra info: [Issue](https://github.com/chrispenny/silverstripe-data-object-to-fixture/issues/13).
160173
161174
### Nesting level of '256' reached
162175

0 commit comments

Comments
 (0)