max resource limit for MODx

Hi,

is there a limitation for resources in MODx?

• I will not generate a list of all resources at the frontend.
• i will use collections extra to keep the tree at the backend small

The plan is to have one Context with multiple publications. Each with chapters > subchapters > articles. The number of Publications is not known at the moment. But could be a LOT.

I have to decide now, which CMS we use for this project.

i think:

your database set the limitation for resources, not MODx. But thats only my opinion, i dont know exactly...

I would put all the data, in this case, your articles into a custom-table, not into resources, if you plan to have a LOT of them.

Quote from: joe-petts at Nov 27, 2017, 04:55 AM

i think:

your database set the limitation for resources, not MODx. But thats only my opinion, i dont know exactly...

Thought so too, but hoped that someone who made some experiences with it tells me more

Quote from: Bruno17 at Nov 27, 2017, 05:20 AM

I would put all the data, in this case, your articles into a custom-table, not into resources, if you plan to have a LOT of them.

A LOT means 350.000 and more.

The categories are not like a shop or a blog category. We need a resource for it too.

How could it work if i use a own table. Sounds like i have to modify the manager and could not use the extras?

chapters, subchapters could be resources. Then have a table with all the articles and a resource_id, which points to the chapters or subchapters - resource.

much like this:
https://docs.modx.com/extras/revo/migxdb/migxdb.tutorials/migxdb.create-a-basic-gallery-management-from-scratch-with-migxdb/

articles instead of images in your case.

Which Extras are you talking about?
You would still use pdoMenu or wayfinder for the navigation, instead of getResources for the articles, you would use migxLoopCollection.

To manage the articles, this is possible with a MIGXdb - TV, or with a MIGXdb - CMP, or both in Combination.

Thanks Bruno. I will have a look at it.

One more thing
Each article has migxTVs. Some of them have Migx TVs which also includes a migx tv.
But should not be a problem if I understood it right. Right?

you can have MIGX - TV-fields also inside a MIGXdb - TV or CMP, or could also be another MIGXdb - TV and another related custom-table instead of the MIGX-field.