@@ -7,15 +7,11 @@ and location in which an entity is utilized. Presently, the ReferenceBundle is c
7
7
Media within PHPCR entities such as `pages ` and `snippets `. These references are managed distinctly for the draft
8
8
state within the `admin context ` and the live state within the `website context `.
9
9
10
- |
11
-
12
10
The main reason we need this bundle is that, unlike traditional database references, our content management system
13
11
operates on an unstructured data model. Therefore, we cannot rely solely on database references, which are usually preferred.
14
12
It is essential to note that the ReferenceBundle should only be used for unstructured data, where database relations are
15
13
not feasible.
16
14
17
- |
18
-
19
15
Content maintainers are able to see the references to a specific entity in the `Insights ` tab of an entity like `Snippet `.
20
16
21
17
.. figure :: ../img/snippet-insights.png
@@ -34,7 +30,6 @@ references by executing the `bin/console sulu:references:refresh` command. This
34
30
35
31
bin/console sulu:references:refresh < resource-key>
36
32
37
-
38
33
.. note ::
39
34
40
35
Please note that references are only refreshed for the current context. To refresh the references for both the
@@ -47,8 +42,6 @@ To integrate the ReferenceBundle for custom content-types, you need to implement
47
42
content-type class. The interface requires you to implement the `getReferences ` method. The method already receives the
48
43
`ReferenceCollector ` which you can use to add references to the collector.
49
44
50
- |
51
-
52
45
Example implementation for a custom content-type:
53
46
54
47
.. code-block :: php
@@ -65,4 +58,4 @@ Example implementation for a custom content-type:
65
58
(string) $data['id'],
66
59
$propertyPrefix . $property->getName()
67
60
);
68
- }
61
+ }
0 commit comments