Setting up a Complex Database - Just looking for approval on structure

[eluser]Gwarrior[/eluser]
Thanks for all the replies.

I couldn't possibly describe how I'm designing this CMS without either writing a book or mangling the legitimacy of the whole thing. By and large, my goal is to create a FULLY customizable CMS where users can upload fieldsets (by uploading fieldset_1.php (or any other #) to a uploaded_views file, which is then pulled out when the users selects that fieldset and tries to add/update data. Essentially, they create the HTML fields and labels, so we don't have to use 'Title' for things other than the Title, which seems to be the way people 'hack' CMS's. This is too confusing for my clients, as I have learned.

The only other CMS I know that does something similar, is Perch (grabaperch.com).

After looking at the database that Wordpress builds upon installation, I think you guys are completely right that I should go down a new path for this one.

The CMS I describe is currently FULLY operational on my server, having spent a couple of work days dedicated directly to it. I don't mind going back and reworking the entire thing, I just want to do it right this time. And what I fear is that the way you guys describe will make me have to remove the 'fieldset upload' portion, because how could a user specify his input fields without knowing that field_1, field_2 already exists, as in

Code:

<input type="text" name="field_1" />

<input type="text" name="field_2" />

If I can figure out how to do this, I could adopt a normal database structure. Any ideas?