A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More.
AI OnAI Off
Multisite asset panel for this page is now for this site {0}
When this issue happens, are you editing content from a content type that is not inheriting from BlockData, PageData or any other primary base class? I've had this issue for ages with custom content types inheriting from StandardContentBase and I finally took the time to investigate and write an article about it. If you have the same scenario then it might help you:
https://ynze.hashnode.dev/solving-the-for-this-0-issue-in-optimizely
Edited,
Mar 06, 2022 2:26
In a multisite DXP hosted environment, the for this page folder is now showing for this {0}. Is there any way to change this back ?