> > You are correct that there is a possibility that some code might get
> > executed out of context with this naming convention. But this is true of
> > of our scripts (like delete_photo.php) And we should watch that we
> > the proper security checks in these include files (like we do in scripts
> > like delete_photo). I just think it's really bad form to see source code
> > a browser. And I've noticed some other projects using this naming
> > lately (like phpgroupware). Anyway, we might have to just disagree on
> > one.
> Well, could you at least make it configurable? I'd hate to have to fork
> this stuff for my own use.
Hey, be careful where you stick that fork! It's all fun and games until
someone loses an eye! :)
Actually I've been chatting with bharat, and he beat on me as well, so I'm
going to change it back. No biggie.