Database design I hope you can take this critisism/suggestion in good stride. I like what you have done but as I was looking at the database design, I noticed that it could be improved quite a bit. You have numbered fields the some of the tables such as: faq_extra1 story_extra1 This is really bad db design. Although you may only need one of these fields and all the others are empty, the empty fields still take up unnecessary space in the db. Also the "field" table is totally wrong. If you need extra fields for the admin table matching them to a certain admin, then you should just have a field table and in it you should have the fields "field_id", "admin_id" (as the key) and what ever other field you need. I hope you understand what I mean. Another suggestion. If you have a key in a table which is used for relating that table to another, you should use the field name from the other table. For instance, in the story table you have "story_category". As I see it, that should be a relation to the category table, so, it should be called "category_id". I read there is going to be a version 2 soon. I hope you can consider improving the database design for the newer version. It will save you programming time, make programming easier and make your product much more efficient. Scott
Database design Thanks for your suggestions. There are indeed some changes planned for 2.0, including optimizing the database design
Database design awsome news allready is a great product 1 thing that i think will attract more customers is a different forum i.e vBulletin,WBBboard as they look more professional just my 2 cents
Database design I'm sure most people, like me, who want to buy an excellent CMS system don't really care too much about that.....
Database design well i do as i think it makes it look bettter for support etc im talking from the sellers point of view
