Page 1 of 1

double check function before being published to web

Posted: Sat Dec 26, 2009 10:28 am
by TileGuy
Hello everyone,

I'm designing a website for a porcelain tile wholesaler. I would like the information on the site to be easily updated (through forms by non-web designer employees) and then double checked by a manager before being published to the eyes of the public.

My first thought was to have a field for all series/items/pictures/etc for a numeric code of 1 for unapproved and 2 for approved. Then have the recordsets run a querry for results with a #2. It would be the easiest to make but I'm thinking it may use up too much resources.

My second thought was 2 sets of tables, one for public eyes, and one a duplicate system of tables that is for non-approved series/items/pictures/etc. However, wouldn't i then have to combine 2 tables into a single report querry? Is that possible?

My monthly traffic isn't very high at the moment but I'm wanting to obviously increase the traffic dramatically. I'm doing my bulk of my programing with Dreamweaver CS3. I've read a PHP and MySQL book by Larry Ullman which laid out what knowledge I have of the programing language. Well... that book and w3schools.

What method would you use?

Any opinions of 110mb for a hosting server?

Can you tell I'm still wet behind the ears?

Thanks

TileGuy

Re: double check function before being published to web

Posted: Sat Dec 26, 2009 12:34 pm
by dannyboyonline
This is pretty simple all u have to do is have some sort of verified_flag field in each record.

What you do is, you set this flag as 1 when the employees key in the data.

Then for the admin interface all you would do is simply populate the admin's "Awaiting approval" section with an SQL statement like
SELECT * FROM some_table WHERE verified_flag = 1

When the admin approves each post update the verified_flag = 2

The site's visitors would then see only those entries with verified_flag = 2
SELECT * FROM some_table WHERE verified_flag = 2

I can't see any performance issue u might come across.

Re: double check function before being published to web

Posted: Sat Dec 26, 2009 2:01 pm
by josh
The approach discussed would work for moderating *new* content. if you want to allow people to make edits without them going live a more sophisticated approach would be needed. One concept I am working on is vehicle-data.com where people suggest changes, and then changes can be voted up/down, and eventually accepted or rejected by a moderator. In this kind of setup all edits are just recorded in a table of "proposed changes". Upon accepting the change the change would be applied to the live record.

I see it as a hybrid type of wiki.

Re: double check function before being published to web

Posted: Sat Dec 26, 2009 4:45 pm
by TileGuy
awesome.

thank you very much