I am running 6.5.0.I also imported the same package I deployed to develop into a new instance on my local and see the same issue. When I click on the folders that contain the content fragments, there is a popup error that just says it failed to load the data. If I create a new folder, the new folder opens and new content fragment instances created under the newly created folder work and are editable.If I drop down and manually change to one of the imported folders by appending the folder name to...

In all cases I was logged in with the administrator account. Also, I had to rebuild my local instance and when I installed the package on my local, I am now experiencing the same issue there as well. I don't think the ACL is the issue.

The issue is that I created some content fragments on my local. I then created a package using the package manager and uploaded them to the develop instance. I then installed them and when I attempt to edit them in the develop instance, the UI errors. There were no extra versions, no other renditions, just the initial content. I also had to rebuild my local instance and used the saved version of the content fragments to recover them and I have the same issue in my local instance now.I did create...

Hopefully to clarify. I am having issues with content fragments that I create on one host and then using the package manager, create packages to transfer them to another host. I have used a package to update the target host with the content fragment models and enabled them in an asset folder. Next I create a package of the content fragment assets and use that package to upload the content fragments to the new host. Then when I attempt to edit the newly installed content fragments. the content fr...

Okay. In attempt to be very clear. I create an instance of a content fragment. Content fragments are versioned. I don't create any new versions of any of the content fragments. There are UUIDs stored in the content fragment's metadata that point to elements under the /jcr:system/jcr:versionStorage root that are not automatically included in a package of the content.Then when the package is uploaded to another host, I think the editor is attempting to reference the version UUID's in the metadata ...

I don't think you fully understand the issue. I know the variations are stored as children under the master. The issue is that there are version UUIDs and some other links to data that is stored in /var that doesn't get packaged when I set the filter to build the package on the original content fragments. Also, the information in /var is not organized by a path based on the master content but it is mixed in with all of the other version information for other assets.

I see that this hasn't gotten any traction on recommendations. I think I have it understood now. I was used to using the older classic UI for creating models and it was easier to find the new touch UI version but I didn't see a save button and noticed that the model saved under /conf/global/settings/workflow/models was saving automatically by the UI. It isn't easily visible that this is only a temporary configuration and that the version in /var/workflows is what actually runs. The fix is to cli...