Content Fragments not available in a configured folder | Community
Skip to main content
R
RobertSHarper
Level 2
June 19, 2026
Solved

Content Fragments not available in a configured folder

  • June 19, 2026
  • 2 replies
  • 52 views

I have some content fragments defined in a project folder. I then went to the configuration manager and created a policy that enabled content fragments models in the configuration folder then also enabled GraphQL as well. I then applied that policy to my parent folder for assets, where I planned to create the content fragments. I was then unable to see my content fragment models when I tried to create a content fragment in that folder or child folders that were set to the default inheritance. When I moved my models to the global folder (I don’t think this should be the resolution) I could then see my defined models.

I would prefer to do this correctly and use the content fragments in the project folder so they can be added to source control without affecting other configurations.

What could be a reason that I am not able to see the project specific models, but I can if see the models in the global folder. Again, I followed the directions on creating a policy to allow the project models. This is in a local sandbox where I am logged in as the admin so it should not be a user permissions issue.

Best answer by RobertSHarper

I got some help to figure it out. I didn’t realize that I should have created the configuration first then placed the models under the configuration. After I moved the models under the configuration, they were visible in the asset folders.

2 replies

ChitraMadan
Community Advisor
ChitraMadanCommunity Advisor
Community Advisor
June 19, 2026

Hi ​@RobertSHarper ,

 

Can you please check below:

  • Open your parent assets folder → Properties → Policies tab. Is "Allowed Content Fragment Models by Path" populated? If yes, please clear it (let it inherit from Cloud Services config).
  • Same folder → Properties → Cloud Services tab → Configuration. Confirm it's explicitly set to your project's conf path (e.g. /conf/my-project), not blank and not /conf/global.
  • Go to Tools → General → Configuration Browser, select your project configuration (my-project), and confirm "Content Fragment Models" (and GraphQL) are checked there.
  • In CRXDE Lite, check /conf/my-project — confirm jcr:primaryType is sling:Folder, not nt:folder
  • Confirm your models actually live under /conf/my-project/settings/dam/cfm/models and are marked Enabled.

Thanks,

Chitra

R
RobertSHarperAuthor
Level 2
June 19, 2026

As I stated, I created the policy under the configuration browser at the correct project. I enabled content fragments and GraphQL ( also at one time checked every property ). The I went to the root asset folder and added that property to the page. I also checked on a child folder and I could not see my models at any level, even though it showed that the policy was configured and in effect.

R
RobertSHarperAuthorAccepted solution
Level 2
June 22, 2026

I got some help to figure it out. I didn’t realize that I should have created the configuration first then placed the models under the configuration. After I moved the models under the configuration, they were visible in the asset folders.

Terms & ConditionsAccessibility statement

Loading footer...