Re: [Phpwebsite-developers] Problem with password being e-mailed out...

[Wendall C. <wen...@to...>]

+1

I think it was discussed before that config files we overused. There are
many advantages to having configurations in the database, as well as
disadvantages. Overall, I think it is clearly more advantageous having
the configuration information in the database with direct access via the
control panel. I really like the simplicity of the main config file. I
rarely use other configuration files, since I always try to change
things via the CP first. It is somewhat annoying to find several other
configuration files that control things that aren't readily apparent or
available to branch sites. However, looking at some of the other CMS
systems out there, as well as other PHP applications, the config file is
really daunting and incredibly complex and obscure when everything under
the sun is in it. Why not keep the main config file simple, all other
configuration settings in the database and accessible via the control
panel? Makes sense to me anyhow.

Wendall


On Sun, 2005-01-23 at 22:35 +0000, Shaun Murray wrote:
> On 23 Jan 2005, at 21:02, Wendall Cada wrote:
> 
> > IIRC it is already using the pear mail class. It does need a config
> > however. I've had a problem before with the pear class where the
> > straight php function worked better, since I could set things in
> > php.ini. Having a configurable mail would be much nicer. Maybe even a 
> > CP
> > page with config setting for mail.
> >
> 
> The PEAR class defaults to using mail() anyway I think but at one point 
> it didn't work in safe mode for the same reasons that it doesn't work 
> in the odd module that uses mail() still. There's no one consistent way 
> that mail is handled in the modules.
> 
> Also, one of the things that was better in phpWebSite 0.8x was that 
> most of the config was done in the control panel, including the text 
> filtering, swear words etc.
> 
> A web based front end to the config files that wrote the config in the 
> database would be very useful and would have the advantage of letting 
> branches have a different config to the main site. And it wouldn't get 
> wiped out on an update unless you're careful with the config directory.
> 
> There's probably a bunch RFEs already for this, at least one from me, 
> but it's the kind of thing that needs changing in the core and probably 
> in a bunch of modules as well.
> 
> Shaun
> aegis design - http://www.aegisdesign.co.uk
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers