File tree Expand file tree Collapse file tree 1 file changed +25
-0
lines changed
Expand file tree Collapse file tree 1 file changed +25
-0
lines changed Original file line number Diff line number Diff line change @@ -75,6 +75,31 @@ Example::
7575 {% static_alias 'footer' %}
7676 </footer>
7777
78+ **New in version 3 **: Static aliases can now be edited directly on any frontend
79+ editable object (such as pages) that includes the ``{% static_alias %} ``
80+ template tag. Static aliases are marked by a pin icon in the structure board to
81+ distinguish them from regular content.
82+
83+ Editing static aliases on the page provides a convenient way to manage alias
84+ content in context. However, when using djangocms-versioning, there are important
85+ considerations:
86+
87+ **Versioning Considerations: **
88+
89+ * **Independent Publishing **: Static aliases must be published independently from
90+ their edit endpoint. Use the edit entry in the alias's burger menu in the structure
91+ board to access the full alias editing interface.
92+
93+ * **Published Content Only **: When objects are viewed on the site (not in edit mode),
94+ only the latest published alias version is displayed. If no published version exists,
95+ nothing will be shown.
96+
97+ * **Draft Creation Required **: Published aliases cannot be edited - neither in the
98+ structure menu nor on their dedicated endpoint. You must create a new draft version
99+ of the alias before editing is possible.
100+
101+ This workflow ensures content consistency and proper version control while providing the flexibility to edit aliases in context when appropriate.
102+
78103Alias plugin
79104============
80105
You can’t perform that action at this time.
0 commit comments