I understand that. I am checking FOLDER properties and the policies tab,
where you select if the policies are inherited from the parent and if
you are overriding them, which content fragments are allowed.
I could but I don't think it is caused by my code. It was working great
in my previous instance and I don't have any custom overlays that should
come into play.Checking properties on the We-Retail sample pages, the
properties tab isn't there either.
The policy tab is not listed when I select the folder properties. I had
this ability in the old instance on a VDI that crashed. Now I no longer
see the properties tab to set which content fragment models are allowed.
Also, I had an old package with the content fragment definitions in it
and there were policy nodes on the folders that specified which content
fragments to allow. This doesn't seem to be working because the
specified models are not shown when I try to create a new fragment.
I had an instance that crashed. I was working on content fragments and
had set policies to only allow certain content fragment models to be
under some folders to organize data. I have stood up a new instance but
the policies tab does not show in the folder configurations so I can
change which content fragment models may be seen. If I apply a package
that had the old settings, clicking on the folder causes errors. What do
I need to set to enable the policies tab on folders?
Yes. I've already read this and have it bookmarked. What I was hoping
for is a more detailed dive into the structures and how to override the
edit pages. I've been able to resolve the issue on my own. It just took
a bit longer than I would have liked.
I think I have it sorted now. There was an overlay of the menu that
wasn't working. I deleted it from the project and now the default menu
works fine. I'd still like to see the full documentation at some point