nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Content type with thousands of DCRs

Bowker

We are about to create some new content types that will end up being populated with an initial load of 3,000 DCRs. Then over time new items will be added. (about 50 per month to each content type.)

In previous versions (we're on 7.2.1) of TeamSite it was strongly advised to not have folder containing more than 500 files.

Are we going to get into trouble? If we are, any solutions?

Find more posts tagged with

Comments

interDev

We are about to create some new content types that will end up being populated with an initial load of 3,000 DCRs. Then over time new items will be added. (about 50 per month to each content type.)

In previous versions (we're on 7.2.1) of TeamSite it was strongly advised to not have folder containing more than 500 files.

Are we going to get into trouble? If we are, any solutions?

Create some subfolders under the data folder for that content type and split the DCRs in those sub folders.

nipper

Use sub folders. OS's do not like that many files in a folder. FormAPI will become you friend, call servers as well. Have those make the folders (when needed).

Bowker

Well I'll do that. I haven't used templating since version 5.x and back then (at least as I remember it) you couldn't do that.

Thanks.

nipper

ping me off line, I did a TST best practices presentation at GearUp a few years ago, I can give you the slides.