This is one of most asked questions for a new user using Concrete5 (and some other systems as well).

It took me a bit at first but it is actually quite simple.

1. All the core files of Concrete5 are in the the /yoursiteroot.com/concrete. Those are the files you don't want to change unless you absolutely need too. When you do an upgrade, all you have to do is either use the new upgrade feature OR get the latest download and copy your /concrete folder to your site and replace ONLY the new version of Concrete5 not the entire folder structure. Your custom items remain where they are and Concrete5 is updated.

2. If you are using and developing other packages, blocks, themes, etc, you will place these files in the other folders off your siteroot. The system will look at these folders first when it is looking for stuff.

Hope this helps
Bill

Hi Bill,

Thanks for your reply - I understand the separation of core files from customized files etc., my question is more about the files that are uploaded via the file manager. It seems that lots of subdirectories are produced in the folder /files/ such that a directory structure like /files/123/26326 and /files/754/4884 start to appear in large numbers.

I assume this is related to the versioning system used by C5, but I'm just wondering why it's set up like that?

Thanks

OSU that would be a Franz and/or Andrew question then. I agree with you on how it the versioning system is involved along with the way the data is stored in the database. This allows for accurate versioning and data management. I could be completely wrong, but that is how it appears to me.

1. Database entry
2. Versioning

These then equates to how the data structure is created in the Site Map. All driven by your database tables.

Bill

Great, makes sense.

Thanks