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 howStaticAlias behaves in Django CMS 4+. From what I understand:

• In CMS 4, aliases are treated asstandalone plugin containers, so their editing is now decoupled from the mainPageContent editing view.
• This means you won't see them in the right-hand plugin sidebar during page editing — even if they're rendered on the page — because they're no longer considered part of the local page structure.

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.

✅ Quick Tip: You can still edit the alias content viaStructure > Aliases, and those updates will reflect across all pages using that alias after publish.

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!