Menu
▾
▴
phpwebsite-developers
|
From: Matthew M. <ma...@tu...> - 2002-12-04 13:00:19
|
Greetings, First a short unpleasantness. I write to this list for opinions. Recently, I haven't really heard many. Not to be harsh, but if I don't receive feedback from this channel, I will start asking just the hometeam developers. Realize I appreciate people's input. In fact, had it not been for this forum, we might not have sequencial numbering yet. Anyway, I am thinking of how to rid ourselves of the core_settings table. That way, when we perform a core update, it never has to worry about the database. I was thinking there should be a date time format file like the language files. Basically there would be a file named after the abbreviation (ie en.php for English, es.php for Spanish). This file would contain the time and date format for that language. phpWS would ship with a default.php for all languages that do not contain a date/time file. These files could not be with language module as they work independantly from it. Along these lines, there are core_settings for censoring and allowed tags. I think these should be put into a file as well. These do not have to be php files either. We could make them text format so textpad could edit them. Let me know what you guys/gals think and whether you prefer core_settings to remain in a table. Matt Matthew McNaney Internet Systems Architect Electronic Student Services Appalachian State University Phone: 828-262-6493 phpwebsite.appstate.edu ess.appstate.edu |
|
From: Don S. <do...@se...> - 2002-12-04 14:04:42
|
+1 to this idea. I haven't had a chance to run around with RC2 yet. I've been busy using 0.8.3 to set up sites for people who can't wait. :p Don. On Wed, 4 Dec 2002, Matthew McNaney wrote: > Greetings, > > First a short unpleasantness. I write to this list for opinions. Recently, > I haven't really heard many. Not to be harsh, but if I don't receive > feedback from this channel, I will start asking just the hometeam > developers. > > Realize I appreciate people's input. In fact, had it not been for this > forum, we might not have sequencial numbering yet. > > Anyway, I am thinking of how to rid ourselves of the core_settings table. > That way, when we perform a core update, it never has to worry about the > database. > > I was thinking there should be a date time format file like the language > files. Basically there would be a file named after the abbreviation (ie > en.php for English, es.php for Spanish). This file would contain the time > and date format for that language. phpWS would ship with a default.php for > all languages that do not contain a date/time file. > > These files could not be with language module as they work independantly > from it. > > Along these lines, there are core_settings for censoring and allowed tags. > I think these should be put into a file as well. > > These do not have to be php files either. We could make them text format > so textpad could edit them. > > Let me know what you guys/gals think and whether you prefer core_settings > to remain in a table. > > Matt > > Matthew McNaney > Internet Systems Architect > Electronic Student Services > Appalachian State University > Phone: 828-262-6493 > phpwebsite.appstate.edu > ess.appstate.edu > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Microsoft Visual Studio.NET > comprehensive development tool, built to increase your > productivity. Try a free online hosted session at: > http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > > > |
|
From: Steven L. <st...@tu...> - 2002-12-04 14:52:12
|
+1 from me as well. Where did you plan on sticking this file? I suggest we create a date directory since the conf directory may be busy with configs for many branch sites. Maybe even a settings directory, where we might put other files later. Just an idea. Steven > Greetings, > > First a short unpleasantness. I write to this list for opinions. > Recently, I haven't really heard many. Not to be harsh, but if I don't > receive feedback from this channel, I will start asking just the > hometeam > developers. > > Realize I appreciate people's input. In fact, had it not been for this > forum, we might not have sequencial numbering yet. > > Anyway, I am thinking of how to rid ourselves of the core_settings > table. That way, when we perform a core update, it never has to worry > about the database. > > I was thinking there should be a date time format file like the language > files. Basically there would be a file named after the abbreviation (ie > en.php for English, es.php for Spanish). This file would contain the > time and date format for that language. phpWS would ship with a > default.php for all languages that do not contain a date/time file. > > These files could not be with language module as they work independantly > from it. > > Along these lines, there are core_settings for censoring and allowed > tags. I think these should be put into a file as well. > > These do not have to be php files either. We could make them text format > so textpad could edit them. > > Let me know what you guys/gals think and whether you prefer > core_settings to remain in a table. > > Matt > > Matthew McNaney > Internet Systems Architect > Electronic Student Services > Appalachian State University > Phone: 828-262-6493 > phpwebsite.appstate.edu > ess.appstate.edu > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Microsoft Visual Studio.NET > comprehensive development tool, built to increase your > productivity. Try a free online hosted session at: > http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers -- Steven Levin Electronic Student Services Appalachian State University Phone: 828.262.2431 PhpWebsite Development Team URL: http://phpwebsite.appstate.edu Email: st...@NO... |
|
From: Projet/Objet <li...@pr...> - 2002-12-04 15:03:45
|
+1 here also Would there be also anything planned regarding the possibility to ajust the time for those who are host on a server where the time zone is different from their own localization.? Regards, Yves le 2002/12/04 08:03, Matthew McNaney =E0 ma...@tu... a =E9crit=A0: > Greetings, >=20 > First a short unpleasantness. I write to this list for opinions. Recently= , > I haven't really heard many. Not to be harsh, but if I don't receive > feedback from this channel, I will start asking just the hometeam > developers. > ... >=20 > Matt |
|
From: Eloi G. <el...@re...> - 2002-12-04 18:17:30
|
+1, with a caveat. Both methods have their pros and cons, and for a tiny amount of non-changing data like this it probably would be better to just have it in a file. However, I'd like the file to reside under the /conf directory either as itself or in a subdirectory. This serves 2 purposes -- (1) to prevent the organizational problem of having tons of configuration files littered across the directory structure, and (2) to allow hosts to easily cache the most-accessed files into memory if they want to take that step in optimization. Eloi George |
|
From: Matthew M. <ma...@tu...> - 2002-12-05 00:39:12
|
It seems most people are for this. I will implement it in the conf/ directory as suggested. I (and the other developers) are currently trapped in the Overlook for a few days, so we probably will be quiet until dug out. Thanks, Matt -- Matthew McNaney Internet Systems Architect Electronic Student Services Appalachian State University Phone: 828-262-6493 phpwebsite.appstate.edu ess.appstate.edu |
|
From: Eloi G. <el...@re...> - 2002-12-05 14:16:24
|
Overlook? |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X