RE: [phpslash-users] submissionAdmin.

[Costas M. <cma...@ea...>]

Yeah, agreed on the user directory.  And don't forget about .inc and .tpl
files as well.

C.


> -----Original Message-----
> From: php...@li...
> [mailto:php...@li...]On Behalf Of Ajay
> Sharma
> Sent: Saturday, November 25, 2000 2:55 PM
> To: PHPslash list
> Subject: RE: [phpslash-users] submissionAdmin.
>
>
>
> So this what you guys want:
>
> /doc-root
>    index.php3
>    /class
>       Author.class
>       Story.class
>    /admin
>       storyAdmin.php3
>       authorAdmin.php3
>       submissionAdmin.php3
>    /user
>       comment.php3
>       submission.php3
>       article.php3
>    /templates
>       [all the .tpl files]
>
> I can go for the class and admin directories, but the user stuff can be
> in the document root. Splitting up the admin/user code won't be a
> problem and it's probably better for security reasons.
>
> All the .class files should be renamed to .class.php.  I'm not sure if
> our php3 users will dig us renaming everything to .php though.  Maybe we
> should have two releases one for .php3 and one for .php?  Just a
> thought.
>
> On Sat, 25 Nov 2000, Costas Malamas wrote:
>
> > I am with Sam on this one.  Moreover, I have to add something:
> > naming our files anything but .php3 or .php makes them visible by
> > anyone with a browser: we cannot change permissions (otherwise
> > Apache wont get to them) and we can't rely on the webmaster to
> > change suffix handlers for Apache --not for those in web-hosted
> > sites-- so I think we should break the stuff up in directories *and*
> > rename the files to .php.  I don't know about templates...
> >
> > I am also anal-retentive :-)...
> >
> > C.
> >
> >
> > > -----Original Message-----
> > > From: Sam Kimery [mailto:ki...@ki...]
> > > Sent: Saturday, November 25, 2000 2:34 PM
> > > To: Ajay Sharma; co...@ma...
> > > Cc: Joe Stewart; php...@li...
> > > Subject: Re: [phpslash-users] submissionAdmin.
> > >
> > >
> > >
> > > My name is Sam. I'm anal-retentive. :-)
> > >
> > > What are the chances of getting some organization wrt. to all
> the class
> > > files, admin files and so forth? We already have templates
> stowed away in
> > > $basedir/templates, why not do the same thing for the other bits
> > > of code as
> > > well? For example, put the Admin pieces into $basedir/Admin
> and the user
> > > stuff into $basedir/user. Common bits could go in $basedir/common. I'd
> > > really like to see some of the clutter reduced and result in
> a directory
> > > with an index.php3 and several directories.
> > >
> > > Of course this pretty much depends on the user code being
> > > separated from the
> > > admin code. Probably not a bad idea - keeps everything simple.
> > >
> > > Just a thought.
> > >
> > > - Sam
> > >
> > > on 11/25/00 12:42 PM, Ajay Sharma at ss...@od... wrote:
> > >
> > > >>
> > > >> Also, guys, why are we calling the old submit.php3
> > > >> submissionsAdmin.php3? why not submissions.php3 or something
> > > >> --basically I don't want people who are considering submitting
> > > >> something be scared off by that Admin thingy...
> > > >
> > > > All the other files are "admin" types, like blockAdmin.php3 and
> > > > topicAdmin.php3 so to keep it consistant, submissionAdmin.php3.
> > > >
> > > > Why doesn't submissionAdmin.php3 take care of the
> Administrative duties
> > > > and we keep submit.php3 around for the users?  I don't like
> to deal with
> > > > too many files.  If I want to work with submissions, I know
> that there's
> > > > ONLY Submission.class and submissionAdmin, nothing else.
> The comment
> > > > stuff is still screwed up because we have comment.class,
> commentAdmin,
> > > > commentSubmit, AND commentShow!!
> > > >
> > > > later,
> > > > ajay
> > >
> > >
> >
>
> ----------------------------------------------------------------
> Satyajot (Ajay) Sharma
> ss...@od...
> Digital Odyssey System Administrator
> There's a brightness dial on the monitor, but the users don't get
> any smarter.
> ----------------------------------------------------------------
>
> _______________________________________________
> phpslash-users mailing list
> php...@li...
> http://lists.sourceforge.net/mailman/listinfo/phpslash-users
>