Strange Behavior with CMS Collections

I just ran into an interesting problem when working with CMS collections.

I created a folder with seven MD files in it and assigned the folder to a collection. After playing with it, I decided that some of the MD files needed to be moved into a separate folder. So I created a new folder and then moved the files from the original folder into the new one.

I then created a new collection and assigned this new folder to that collection. When I went to preview it, none of the moved files were displayed. This, even though they worked just fine when they were in the original folder.

Next, I created NEW MD files in the new folder and copied the contents from the moved files into the new files. Bingo, now all of these files are displayed correctly in the collection.

Not sure what is going on here, but it seems that once MD files have been placed in the folder, they cannot be moved to a different folder. Which seems very odd.

I don’t know if this has something to do with the fact that they were rendered from a different folder initially.

Is there some sort of caching going on that could be causing the problem?

Unfortunately, I should have done a quit and restart to see if that fixed the issue, but I did not do that.

This is probably an Elements issue with keeping track of the files (as opposed to the CMS), I believe a restart would have fixed this issue for you.

btw. We have more work to do on file management, so this should improve.

If you run into it again, try a restart of Elements, that should resolve it for you :slight_smile:

1 Like

I did some more testing and it seems to have resolved itself. Because now I can freely move files from one folder to another and the display updates accordingly. Maybe it only occured because I created a new folder and moved the files into it.

I’ll try to keep experimenting to see if I can reproduce the problem.

1 Like