Replies: 1 comment 1 reply
-
|
Hi @luboSB-47 — we ran into something similar when upgrading from 3.x to 4.x. Yes, this seems to be an intentional change in how
This new design helps enforce better reuse and version control of aliases across multiple pages — but yes, it does feel like a change from earlier behavior.
I’m not sure if there's a setting to restore the old editing behavior, but I’d love to hear from core maintainers if a toggle exists. Hope that helps a bit! |
Beta Was this translation helpful? Give feedback.
-
|
I understand the reuse but since most of the time the alias serves some purpose on the page editing rest of the content without it is suboptimal for the non technical editor users. Similarly when editing alias, it is not optimal to edit it outside of any page context. It would be great to have a functionality okay I am on homepage and editing content but showing everything rendered on the left side, or I switch to alias edit on homepage still seeing everything but showing alias content in the structure menu. That way versioning is clear and at the same time it's practical for content editor. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
After upgrading CMS from 3.11 to 4.1.7, a big change we noticed is StaticAlias not being shown in right-side menu with plugins, when editing PageContent for a page that is using that given StaticAlias (e.g. alias "menu" in a "homepage" PageContent).
We saw that plugins of a StaticAlias object can only be changed in it's separate view.
Also, our homepage contains several aliases that are correctly being rendered, however after changing to Edit mode on the page, they disappear and only PageContent itself is visible while editing it's plugins.
After publishing / exiting Edit mode, aliases are correctly rendered again.
2. Is this expected behavior?
Thank you for any answers or insights in advance.
Beta Was this translation helpful? Give feedback.
All reactions