MODX Staff
In order to make the best use of MODx, each listing would be a document. However MODx is not currently recommended for more than 5,000 documents because the performance suffers. Therefore I think you might be better off creating a custom solution or maybe looking at CMS.
Andy
Hi,
I’d like to build the following project...
Project
=====
Regular business directory (like phpMyDirectory) with... name,address,email,tel,fax,description,categoty,sub-categories,etc.
Features Overview
============
User registration, with email confirmation.
Registered users create/maintain their lisiting.
Admin can edit/block/unblock/suspend listings.
Advanced search capabilities
Friendly URL for each listing (e.g. www.directory.com/category/listing-name-uniqueID.html)
I would really like to use MODx for this project (i’m in love with MODx), but i’m not sure on how to advance with this...
Queries
=====
Should I use the standard MODx document (with TVs) to create each listing or create a different table managed by a module and use MODx APIs to interact with the table.
I am not a programmer (but MODx somehow gives me the confidence I can do it), if the experts here can provide me some direction/best practices, I will be able to pick up and work on this project. I look forward to your advice, guidance and help. I hope, this project, when done, will be of use to many.
Note: This directory is for my school alumni and I expect it to be HUGE (i.e. if all people participate). A conservative figure could be about 30,000 listings (that’s the current email database we have).
Warning: Me being a beginner, may come up with simple (sometimes silly) question. I request you patience
Andy, How much functionality will we lose. If you can shed some light on this issue, I am sure, it will help beginners like me and others to understand MODx much better.
Right, by storing the data in a custom database table and using snippets to display the data for example. But then you lose some functionality, so you have to consider if MODx is right for your needs.
Andy
OpenGeek, will the MODx engine be able to handle more documents in the future. We currently have about 150 content pages and we plan to make the new website more active with regular updates (hopefully, daily). Defenitely, we have a great deal of time to reach the 5000 document mark. After, working with MODx, I dont think I will be as comfortable with any other CMS. I would like to grow with MODx.
Though managing more than 5,000 actual documents might not be practical at this point in the MODx engine, there is absolutely nothing stopping anyone from creating a single page in MODx that produces any number of actual page outputs for this type of publishing. The idea that one document in MODx = one web page is simply not true. It’s limited only by your imagination and web development skills.
☆ A M B ☆
Indeed, consider that one lonely little index.php page is producing every page on your site. It’s just a matter of deciding how the content for a given page is actually produced. Look at ditto; you can use it to display as much as you please of as many documents you please, all on one page.
Though managing more than 5,000 actual documents might not be practical at this point in the MODx engine, there is absolutely nothing stopping anyone from creating a single page in MODx that produces any number of actual page outputs for this type of publishing. The idea that one document in MODx = one web page is simply not true. It’s limited only by your imagination and web development skills.