RE: Remote administration
This WebDNA talk-list message is from 1998
It keeps the original formatting.
numero = 19516
interpreted = N
texte = This is a walk in the park for webcat! Just make two databases: approved and pendingThe record format should be identical and one should be used to populate the public display. Make an administration page to view the pending records. For convenience, I'd make sure to make every field of every record quickly editable, along with a quick delete button to blow away nonsense posts.Couple of other tips: [protect] your admin pages, and keep public and administration pages in separate directories to ease confusion. All dbs should be in one db folder because there aren't that many. Images in one folder with subfolders for types if necessary (buttons, banners, etc.) is also helpful.Almost every one of the sites I have has a set of adnmin pages in an adminhtml folder which allow non-HTML folks the ability to completely maintain their sites. It seems to happen with every site when using WebCatGood Luck! Pat> -----Original Message----- > From: charles kline [mailto:ckline@webtown.com] > Sent: Tuesday, August 18, 1998 9:05 AM > To: WebDNA-Talk@smithmicro.com > Subject: Remote administration > > > I am setting up a website for a client who wants to have a section where > people in the community can post items for sale or services available i.e. > lawn work, baby sitting, etc... It is a pretty uptight town and they are > concerned that some kids might get on there and post a bunch of > profanity or whatever... > > The client wants the ability to check each post and approve it > before it goes > live to the site. They do not want to have to reenter each form > by hand, and I > do not want to have to do any updates to this section at all > myself. I need a > solution that allows them to approve the post before it becomes > part of the > database. Is there any way to do this elegantly? I do not want to have to > handle the database updates myself and the person who will > probably be doing > these updates is not necessarily web savvy. > > I would appreciate any thought on this issue. > > Please respond to me directly as well as to the list as I am on the digest > version and would like to receive any feedback as soon as it is posted. > > Thanks, > > -= Charles Kline =- > _____________________________________ > Pixel Dust Productions -- MacSultants > ckline@webtown.com > ckline@macsultants.com > http://www.webtown.com > http://www.macsultants.com > >
Associated Messages, from the most recent to the oldest:
This is a walk in the park for webcat! Just make two databases: approved and pendingThe record format should be identical and one should be used to populate the public display. Make an administration page to view the pending records. For convenience, I'd make sure to make every field of every record quickly editable, along with a quick delete button to blow away nonsense posts.Couple of other tips:
[protect] your admin pages, and keep public and administration pages in separate directories to ease confusion. All dbs should be in one db folder because there aren't that many. Images in one folder with subfolders for types if necessary (buttons, banners, etc.) is also helpful.Almost every one of the sites I have has a set of adnmin pages in an adminhtml folder which allow non-HTML folks the ability to completely maintain their sites. It seems to happen with every site when using WebCatGood Luck! Pat> -----Original Message----- > From: charles kline [mailto:ckline@webtown.com] > Sent: Tuesday, August 18, 1998 9:05 AM > To: WebDNA-Talk@smithmicro.com > Subject: Remote administration > > > I am setting up a website for a client who wants to have a section where > people in the community can post items for sale or services available i.e. > lawn work, baby sitting, etc... It is a pretty uptight town and they are > concerned that some kids might get on there and post a bunch of > profanity or whatever... > > The client wants the ability to check each post and approve it > before it goes > live to the site. They do not want to have to reenter each form > by hand, and I > do not want to have to do any updates to this section at all > myself. I need a > solution that allows them to approve the post before it becomes > part of the > database. Is there any way to do this elegantly? I do not want to have to > handle the database updates myself and the person who will > probably be doing > these updates is not necessarily web savvy. > > I would appreciate any thought on this issue. > > Please respond to me directly as well as to the list as I am on the digest > version and would like to receive any feedback as soon as it is posted. > > Thanks, > > -= Charles Kline =- > _____________________________________ > Pixel Dust Productions -- MacSultants > ckline@webtown.com > ckline@macsultants.com > http://www.webtown.com > http://www.macsultants.com > >
Pat McCormick
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Configuring E-mail (1997)
Frames and WebCat (1997)
Re:Transfer of data from Invoice to thank you templates (1998)
Confusing [protect] (long) (1999)
Problems with [Applescript] (1997)
db protection on NT (1997)
Design Help Needed (1998)
MacWEEK article help needed (1996)
The Guru Speaks-Is That Really the Only Manuel? (1998)
flushdatabases (2000)
Max Record length restated as maybe bug (1997)
WCS Newbie question (1997)
Possible solution to malformed pages in NN (2000)
A sendmail warning (2005)
Webcat/Webmerchant part II (1998)
b12 cannot limit records returned and more. (1997)
Re:quit command on NT (1997)
hidden databases (2000)
Upgrading old WebCat Database Files (1997)
Order not created error (1997)