Using sudo to resolve issues like this should be discouraged, as you can create other issues such as file permissions etc later on down the line when you try to use mvn again.
Actually, in my case, I had some kind of inheritance override coming from the content/dam folder which was interfering with the Cloud Configuration settings in my content fragments sub folder.Many thanks all for your help and suggestions.
To add further...I can copy a model node from global to <site>.For example, "article" model node copied from /conf/global/settings/dam/cfm/models/ to /conf/<site>/settings/dam/cfm/models/. Article model is now visible.I can also cut & paste previous Content Fragments that were created using the glob...
Re. 1. We are using AEM 6.4. In Tools > Assets > Models. We can see the global models and properties. However, there does not seem to be any UI to disable / enable a model ??Re 2.The configuration browser has allow CFs. As mentioned, we can use Site CFs, but not the global ones.
Hi, I tried adding /content/dam/content-fragments(/.*)?But this did not work. We also have a "twin" AEM instance, which does not have the global CF problem. In there, as well as here, we have set./content/entities(/.*)?
When creating a new Content Fragment (CF), there normally should be a list of Content Fragment Models (in the create CF dialog page) to base your new CF on.In one of our AEM ENVs, we have the peculiar case where, on this creation page, we can see only the "site" content fragment models, but not the ...
For me, this solution did not work. There must have been some kind of install problem with CFP 2.0, and hence I seemed to be "stuck" there. This was eventually solved by uninstalling and deleting CFP 2.0
This here turned out to be the correct path. The advice above is good, and anyone else should follow these steps.For me, the actual solution was "uninstalling" each CFP starting at 4.0, and then deleting the actual CFP package. At the same time, you want to monitor the crx console, namely, /libs/sys...
Could you clarify about this "forced install"???There is a "force upload" when you upload a package. I have downloaded the CFP 6.4.8.4 package again from the server and performed a MD5 checksum. This matches the 6.4.8.4 package which was uploaded.