You can subscribe to this list here.
2001 |
Jan
|
Feb
(1) |
Mar
(265) |
Apr
(166) |
May
(25) |
Jun
(17) |
Jul
(20) |
Aug
(47) |
Sep
(6) |
Oct
(14) |
Nov
(66) |
Dec
(64) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(109) |
Feb
(64) |
Mar
(34) |
Apr
(23) |
May
(64) |
Jun
(9) |
Jul
(13) |
Aug
(6) |
Sep
(33) |
Oct
(272) |
Nov
(67) |
Dec
(75) |
2003 |
Jan
(264) |
Feb
(244) |
Mar
(171) |
Apr
(119) |
May
(54) |
Jun
(93) |
Jul
(51) |
Aug
(48) |
Sep
(14) |
Oct
(49) |
Nov
(47) |
Dec
(15) |
2004 |
Jan
(13) |
Feb
(27) |
Mar
(18) |
Apr
(44) |
May
(35) |
Jun
(24) |
Jul
(39) |
Aug
(142) |
Sep
(35) |
Oct
(34) |
Nov
(49) |
Dec
(24) |
2005 |
Jan
(60) |
Feb
(71) |
Mar
(19) |
Apr
(27) |
May
(68) |
Jun
(4) |
Jul
(30) |
Aug
(10) |
Sep
(23) |
Oct
(24) |
Nov
(13) |
Dec
(6) |
2006 |
Jan
(4) |
Feb
(46) |
Mar
(64) |
Apr
(18) |
May
(16) |
Jun
(37) |
Jul
(7) |
Aug
(19) |
Sep
(9) |
Oct
(8) |
Nov
(3) |
Dec
(23) |
2007 |
Jan
(25) |
Feb
(21) |
Mar
(32) |
Apr
(36) |
May
(12) |
Jun
(1) |
Jul
(7) |
Aug
(15) |
Sep
(13) |
Oct
(1) |
Nov
|
Dec
|
2008 |
Jan
(3) |
Feb
(5) |
Mar
(1) |
Apr
(2) |
May
|
Jun
(1) |
Jul
(2) |
Aug
(7) |
Sep
|
Oct
(5) |
Nov
(1) |
Dec
|
2009 |
Jan
(7) |
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
From: Matthew M. <ma...@tu...> - 2002-03-31 18:12:05
|
> Fallout Developers: > > Can I suggest that all class files in the new core be loaded using > "require_once()" instead of "require()"? > > Seems to me that this has the benefit of not breaking module classes > that require their own subclasses. I know that you are discouraging the > requiring of classes within module files, but the PEAR coding > recommendations and general PHP coding recommendations are that all > required files get required wherever they are required to improve > reliability and readability. > Absolutely. Consider it done. Matthew McNaney Internet Systems Architect Electronic Student Services Email: ma...@tu... URL: http://phpwebsite.appstate.edu Phone: 828-262-6493 ICQ: 141057403 |
From: Randall W. <rh...@ma...> - 2002-03-30 21:26:02
|
Fallout Developers: Can I suggest that all class files in the new core be loaded using "require_once()" instead of "require()"? Seems to me that this has the benefit of not breaking module classes that require their own subclasses. I know that you are discouraging the requiring of classes within module files, but the PEAR coding recommendations and general PHP coding recommendations are that all required files get required wherever they are required to improve reliability and readability. The affected lines in <fallout_root>/index.php (CVS checkout 3/29/02) are lines 22, 23, and 94. -- Randall Wood rh...@ma... |
From: Alessandro P. (T. / J578) <al...@ti...> - 2002-03-29 16:31:47
|
29/march/2002 - X-Web is a new CMS project being created from a fork of phpWebSite (0.8.1-CVS). The goal of X-Web is to become a feature rich CMS (content management system) offering improved data management and scalability, overall package stability, compatibility, and a shot of powerful new features. The target user base for X-Web will be both Professional Website Administrators and the average Personal Website Manager, with an extra emphasis on creating an excellent user experience. X-Web is endorsed by phpWebSite Development Team / Appalachian State University but is, and will remain, completely independent from both of them. The founders of X-Web thank them for providing this opportunity to start from such a well-rounded code base. Detailed information, project goals and developer information are now available at http://www.X-WebCMS.com For further information you can contact: Alessandro Pisani <al...@us...> Mike Lansberry <mid...@us...>. -- Alessandro "TXM" Pisani - al...@ti... - ICQ #2209087 phpWebSite Development Team http://phpwebsite.appstate.edu INWO Project coordinator http://inwoproject.sourceforge.net "I will carry you through, kicking and screaming, and in the end you will thank me" - Tyler Durden [from "Fight Club"] |
From: Alessandro P. (T. / J578) <al...@ti...> - 2002-03-28 08:50:02
|
can be found here: http://www.faqts.com/knowledge_base/view.phtml/aid/1/fid/40 HTH Bye, Alessandro -- Alessandro "TXM" Pisani - al...@ti... - ICQ #2209087 phpWebSite Development Team http://phpwebsite.appstate.edu INWO Project coordinator http://inwoproject.sourceforge.net "I will carry you through, kicking and screaming, and in the end you will thank me" - Tyler Durden [from "Fight Club"] |
From: Randall W. <rh...@ma...> - 2002-03-25 02:59:44
|
I have made a basic translation module, called Translator. It is designed to allow developers to maintain translation tables that can be used on-the-fly to translate phpWebSite modules. It includes a basic internationalization tool as well. It can be downloaded at http://homepage.mac.com/rhwood This module is very basic and is somewhat untested (it works on my Mac). I would like you to poke at it to get a feel for how I should develop the APIs for this kind of thing rather than to use it in a real environment. -- Randall Wood rh...@ma... |
From: <bo...@el...> - 2002-03-24 16:29:06
|
I am looking for a system that allows me to create html user and technical manuals on line. Some such thing must exist, but putting "documentation tool" in google is no way to find it. What I want to do is to associate an image (screen shot) with a section title and an image subtitle and some text. Sections are rolled up into pages, which are rolled up in chapters, which are rolled up into books. ( I am describing a system I have already written in Oracle ... Hence the detail ) Table of contents is generated, and also index. Judging from online documentation that is available -- like at php.net for instance, there are tools that do this. Can anybody point me to any of them? Thanks in advance! Bob Treumann |
From: Karsten D. <k.d...@fi...> - 2002-03-22 11:18:25
|
On Don, Mär 21, 2002 at 06:21:20 -0500, Randall Hansen Wood wrote: > Regarding the new language constructs: [...] > I can think of a couple of reasons to store the translations in the > database: > 1) files full of code do not have to be maintained. > 2) translations can be updated off the web without having to download, FTP > and install a file. > 3) translations do not have to sync with the English updates. Code can be > updated, patched, whatnot and translations can come later, if need be... 4) We use the database for every page call anyway. So the impact wouldn't be that bad. If you combine with the mentioned cacheing, this would be cool. Just my 2 cents, Karsten -- fishfarm netsolutions - Karsten Dambekalns Echternstraße 73 - 38100 Braunschweig Tel. +49 531 1232902 k.d...@fi... Fax. +49 531 1232906 http://www.fishfarm.de/ ----------------------------------------------------- |
From: Randall H. W. <rh...@ea...> - 2002-03-21 23:19:21
|
Regarding the new language constructs: I have this week been (mostly to exercise my PHP muscles) a translation database maintenance module for 0.8.x (The purpose was that the ??.pp files could be generated from a database before building phpWebSite and that anyone could suggest translations although a maintainer would need to approve suggestions before they are included in the builds). I'll have it done this weekend. Right now it uses mod_translation_* for its own purposes and i18n_translation_modname and i18n_translation_core for the translation tables. It includes an i18n (internationalization/localization) class that can handle translations and maybe in the future other internationalization/localization tasks (like numerical and date/time formatting). The current call is $i18n->translate($string). By including the function in a class, I can cache translation calls to reduce the number of db calls...but call the db to translate any string required... I can think of a couple of reasons to store the translations in the database: 1) files full of code do not have to be maintained. 2) translations can be updated off the web without having to download, FTP and install a file. 3) translations do not have to sync with the English updates. Code can be updated, patched, whatnot and translations can come later, if need be... I hope you find this rambling helpful... -- Randall Wood rh...@ma... |
From: Bob T. <bo...@el...> - 2002-03-21 17:05:37
|
I just thought of two reasons to use a function call instead of just a variable assignment. 1. You could pass the entire string into the function call. If the function doesn't have a variable of that name, it just returns the string that is passed in: show_string('Do you really mean it') function show_string($key) { If ( ! ($lang[$key] ) { return $key; } This would make it easy when developing code to get everything right before creating abbreviation keys and changes to the translation file or database. The other reason is so that the function can log certain types of messages that are very unexpected, (Database not available or 'Cant write to file XYZ fior instance) or indicate a possible security breach or hacking attempt ( "Too many login attempts" ) -- Bob Treumann, 651-603-1245 Elmwood Solutions Inc. (St. Paul, Minnesota) bo...@el... http://www.elmwood.com ORACLE Business Alliance Program Member |
From: Bob T. <bo...@el...> - 2002-03-21 17:01:37
|
I think this could be accomplished with the current make_disto script, with some tweaks. Just change the search so it looks for the function or variable call $lang_[] instead of TRANSLATE[[]]. On 21 Mar 2002 at 7:40, Joel Kleppinger wrote: > Random thought: > > What about having an option to "compile" the language into the files > at install so that a webmaster that only needs to worry about one > language (me and English) can do that and get the associated > performance benefit AND making it easier/straightforward to work with > the files. > > I have a feeling that nearly all of us only worry about one language, > whatever that may be so this type of feature would benefit a lot of > people. > > Joel > > > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers -- Bob Treumann, 651-603-1245 Elmwood Solutions Inc. (St. Paul, Minnesota) bo...@el... http://www.elmwood.com ORACLE Business Alliance Program Member |
From: Brian W. B. <br...@tu...> - 2002-03-21 15:37:46
|
Developers: In light of some rather heated discussions on the SF forums as of late, I feel the need to clarify the goals and philosophy of the phpWebSite project. Our first goal is to foster an open, healthy, helpful, and most of all, a cooperative development environment. Until recently, this has been universally true. Whatever phpWebSite was or was not, everyone involved got along and everyone tried to help each other and learn from each other. Quite frankly, it saddens me to see the kind of behavior I have witnessed recently. Our second goal is to create a flexible content management system that enables non-technical people to effectively manage information on the web. Make no mistake - these goals are in the proper order. It should also be noted that the the word "cooperative" is not a synonym for "submissive". Active discussion within our community is not only tolerated, but encouraged. Active discussion, however, requires that those involved maintain respect for each others ideas, and that the individuals involved simply be polite. It is an unfortunate reality that the primary means by which we communicate within this community - email and forums - easily add a sharp edge to words that would be softened by the tongue. For this reason, it is important that we make the effort to communicate not only clearly, but gently. The irony in this case was that some very valid ideas and opinions (on both sides) were grossly overshadowed by the tone of delivery. For those involved in the thread and for those who followed it in morbid curiosity, let me quickly address a few major points: o "Data Packing" is strongly discouraged. Smart data structures and dumb code works better than the other way around. o Class serialization is also strongly discouraged and will not be stored in the database in serialized form. o Serialized arrays can be stored in the database under certain well-defined, limited circumstances. Please note that this discussion is still open, and Matt and I will post an official policy once we feel we have something everyone can live with. If you have any thoughts, ideas, or solutions you would like to share, please email Matt or myself. I would also like to clarify that those of us employed by Appalachian State University must maintain a balance of responsibilities in our work with the phpWebSite project. This has always seemed to be readily apparent to me, but based various comments about the University's role in the project there would seem to be some fundamental misunderstandings in this regard. The University neither blindly supports phpWebSite, caring not whether development efforts serve the institution, nor is phpWebSite an exclusive University project that limits non-university developers to voyeuristic participation. The truth is more complicated and lives in the middle of these two extremes. The balance we seek is best illustrated by a very real example from the project. More than once we have been criticized for not testing phpWebSite on multiple platforms or for saying that we cannot duplicate a reported problem. We run campus installs of phpWebSite on Red Hat Linux Servers running Apache, PHP, and MySQL Max. Our compile options for PHP are on the web. This works for us, and this is the platform on which we test. Freely spending money and resources by testing configurations and platforms that we have no intention of using in a production environment would very simply not be in the best interest of the institution, our students, or the hard-working tax payers (i.e. *you*) that support this institution and others like it. If, on the other hand, someone wishing to use a different platform provided the development team with code that had been successfully tested on other platforms, it would certainly be incorporated. Please understand that those associated with the university are trying only to be responsible, but that does not necessarily limit in any way the scope of contribution by those that wish to participate in the project. Finally, I would like to say that I see phpWebSite as being on the cusp of becoming a truly great software package. Matt McNaney's work on the updated core is impressive and will allow phpWebSite to become truly modular. Making phpWebSite what you need it to be will only become easier for both the developer and the user. If you have not taken a look at the updated core, code named "fallout" - please do, it is the future of phpWebSite. The 0.8.2 release is getting very close and should provide a stable resting point while the integration of the updated core begins in earnest. On a more personal note, I feel the need to share some of the circumstances that have limited my direct participation in the project as of late. I was promoted to Director of Electronic Student Services about six months ago and my new duties have understandably impacted my role in the project. Matt McNaney was designated as Assistant Project Manager in response to these changes and has done a very good job in this role. My focus is primarily with the students involved in the program and in the administrative role of keeping the project funded and "alive". Thank you for your time and thank you for your many contributions. Kind Regards, Brian W. Brown phpWebSite Project Manager -- Brian W. Brown Director, Electronic Student Services Student Development Room 269, John Thomas Hall Appalachian State University Boone, NC 28608 vox: 828-262-7124 fax: 828-262-2585 L I N U X .~. /V\ // \\ /( )\ ^^-^^ Love the Penguin |
From: Karsten D. <k.d...@fi...> - 2002-03-21 15:30:27
|
On Don, Mär 21, 2002 at 08:25:46 -0600, bo...@el... wrote: > request. We want to include the files only once per session. The > variables need to survive across multiple page requests. For this, > we need a session variable, hence: > $lang_loaded["books"] ="yes" So you want to keep the language stuff in the users's session? Hmm... okay. Then there is no other way. Regards, Karsten -- fishfarm netsolutions - Karsten Dambekalns Echternstraße 73 - 38100 Braunschweig Tel. +49 531 1232902 k.d...@fi... Fax. +49 531 1232906 http://www.fishfarm.de/ ----------------------------------------------------- |
From: Joel K. <jo...@jo...> - 2002-03-21 14:38:34
|
Random thought: What about having an option to "compile" the language into the files at install so that a webmaster that only needs to worry about one language (me and English) can do that and get the associated performance benefit AND making it easier/straightforward to work with the files. I have a feeling that nearly all of us only worry about one language, whatever that may be so this type of feature would benefit a lot of people. Joel |
From: <bo...@el...> - 2002-03-21 14:19:57
|
Karsten - include_once and require_once are used to ensure that files are not loaded more than once while the server is responding to a single request. We want to include the files only once per session. The variables need to survive across multiple page requests. For this, we need a session variable, hence: $lang_loaded["books"] =3D"yes" Thanks for the tip though. On 21 Mar 2002 at 12:51, Karsten Dambekalns wrote: > On Mit, M=E4r 20, 2002 at 11:57:20 -0600, bo...@el... wrote: > > > I'd like to suggest that there be multiple files, and that > > one definition inside that file would indicate that it > > has already been loaded. > > $lang_loaded["books"] =3D "yes"; //module is called "books" > > This way, we only load what is needed. > > > > If not ($lang_loaded["books"]) { > > include 'books_file' > > } > > Ahem. Did you know about include_once() and it's sister > require_once()? There are even functions to query for all > included/required files. This should solve the problem better and > faster... > > Regards, > Karsten > -- > fishfarm netsolutions - Karsten Dambekalns > Echternstra=DFe 73 - 38100 Braunschweig > > Tel. +49 531 1232902 k.d...@fi... > Fax. +49 531 1232906 http://www.fishfarm.de/ > ----------------------------------------------------- > > > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers |
From: Karsten D. <k.d...@fi...> - 2002-03-21 11:51:38
|
On Mit, Mär 20, 2002 at 11:57:20 -0600, bo...@el... wrote: > I'd like to suggest that there be multiple files, and that > one definition inside that file would indicate that it > has already been loaded. > $lang_loaded["books"] = "yes"; //module is called "books" > This way, we only load what is needed. > > If not ($lang_loaded["books"]) { > include 'books_file' > } Ahem. Did you know about include_once() and it's sister require_once()? There are even functions to query for all included/required files. This should solve the problem better and faster... Regards, Karsten -- fishfarm netsolutions - Karsten Dambekalns Echternstraße 73 - 38100 Braunschweig Tel. +49 531 1232902 k.d...@fi... Fax. +49 531 1232906 http://www.fishfarm.de/ ----------------------------------------------------- |
From: Karsten D. <k.d...@fi...> - 2002-03-21 11:51:38
|
On Mit, Mär 20, 2002 at 12:49:33 -0500, Matthew McNaney wrote: > Greetings again, > > As I work on the new core, it was decided to switch to modular updates. In > other words, portions of the web site can be upgraded instead of the whole > package. The admin can check for updates via an internal interface. The > core would check the version file indicated by the module install. If an > update exists, the admin downloads it and runs the update. > > All very nice but there is one problem: the translation system. > > The current translation system upgrades the package as a whole and it seems > unwieldy for the new schema. So I am proposing this for CONSIDERATION. I hope you dig through the old mail. There have at least been two occasions when the translation system was discussed, at that time mainly with having on-the-fly language switching and the pros and cons of this. I hope the new system (however it will look) will support this. I must admit that I am too lazy to look up the mgs-ids of the relevant mails right now. But a search on your mailbox file (you do keep the mails, don't you?) should reveal the stuff. I was into the discussion both times, so it might be enough to search for my name. If needed, I can of course look up the messages and post pointers or forward them to you directly. Regards, Karsten -- fishfarm netsolutions - Karsten Dambekalns Echternstraße 73 - 38100 Braunschweig Tel. +49 531 1232902 k.d...@fi... Fax. +49 531 1232906 http://www.fishfarm.de/ ----------------------------------------------------- |
From: Alessandro P. (T. / J578) <al...@ti...> - 2002-03-20 18:16:50
|
On Wed, 2002-03-20 at 17:33, Matthew McNaney wrote: > Greetings all, > > If you have been reading Sourceforge, there is a message about Alessandro > Pisani and Mike Lansbury making a fork of phpWebSite entitled X-Web. Ehm...it is "Mike Lansberry" :) Bye, Alessandro -- Alessandro "TXM" Pisani - al...@ti... - ICQ #2209087 phpWebSite Development Team http://phpwebsite.appstate.edu INWO Project coordinator http://inwoproject.sourceforge.net "I will carry you through, kicking and screaming, and in the end you will thank me" - Tyler Durden [from "Fight Club"] |
From: Matthew M. <ma...@tu...> - 2002-03-20 18:08:03
|
> I'd like to suggest that there be multiple files, and that > one definition inside that file would indicate that it > has already been loaded. > $lang_loaded["books"] = "yes"; //module is called "books" > This way, we only load what is needed. > > If not ($lang_loaded["books"]) { > include 'books_file' > } Agreed. Think about this too: 1) all module language files are loaded at once. 2) Only the active modules language files are loaded. a)They are unloaded when not in use. b)They are kept in memory until user logs off. Which is fastest/smarter? 1) All loaded at once and then never again is one file hit but more memory 2) More file hits, less overhead a) Even less overhead b) More overhead but no more file hits This may be an exercise in minutia but I am interested in 'the best way'. > There should also be a local overide file, so that site operators can > tailor some of the messages without changing the released > files: Good point. I'll make sure that is in the translate module as you may have different translations within the same language. > It would be nice also if we had a file of generic translations for > things like "Submit", "Delete", "Are you Sure". Ya I was thinking about this. Consider also that a programmer may program in Spanish and we use an English translation. The generic translation file becomes useless if the Spanish speaker could care less about English =) Maybe a combination? Not sure yet. > I have not yet used session_register to save arrays. If this can be > done, then I like the use of arrays. What is the syntax for > registering an array? Is it the same as registering any other > variable? Yes. > I assume you will be writing a function to do this. Not sure yet. For developer simplicity, I like the idea of just entering: echo LANG_modulename["trans_this"] instead of $core->translate(LANG_modulename["trans_this"]) Kind of like calendar but with the language mod doing the work behind the scenes. Matthew McNaney Internet Systems Architect Electronic Student Services Email: ma...@tu... URL: http://phpwebsite.appstate.edu Phone: 828-262-6493 ICQ: 141057403 |
From: <bo...@el...> - 2002-03-20 17:51:36
|
I appreciate your asking for input. I hope these thoughts are helpful: I think we need multiple language files, not just one big one. The english file is 112,000 bytes today. I'm not sure how that would translate into memory usage. Maybe about half that. But as features and modules are added, it could get to be ten times its current size. Also, not all things will be short. How about instructions for instance? They can get detailed. I'd like to suggest that there be multiple files, and that one definition inside that file would indicate that it has already been loaded. $lang_loaded["books"] = "yes"; //module is called "books" This way, we only load what is needed. If not ($lang_loaded["books"]) { include 'books_file' } There should also be a local overide file, so that site operators can tailor some of the messages without changing the released files: If ( !$lang_loaded["local_stuff"] ) && file_exists('local_language_mods') { include ('local_language_mods') ; } else if (!{$lang_loaded["local_stuff"])) { //to avoid checking for the file again $lang_loaded["local_stuff"]="yes" } It would be nice also if we had a file of generic translations for things like "Submit", "Delete", "Are you Sure". I have not yet used session_register to save arrays. If this can be done, then I like the use of arrays. What is the syntax for registering an array? Is it the same as registering any other variable? I assume you will be writing a function to do this. The call to the function should also pass the option to force a reload: load_translation('books','') load_translation('books','reload') would force a reload. Bob T. |
From: Matthew M. <ma...@tu...> - 2002-03-20 16:54:03
|
Greetings again, As I work on the new core, it was decided to switch to modular updates. In other words, portions of the web site can be upgraded instead of the whole package. The admin can check for updates via an internal interface. The core would check the version file indicated by the module install. If an update exists, the admin downloads it and runs the update. All very nice but there is one problem: the translation system. The current translation system upgrades the package as a whole and it seems unwieldy for the new schema. So I am proposing this for CONSIDERATION. A new system would work much like the Calendar translation works. There could be an array of translations in the form of LANG_modulename. echo LANG_modulename["ten_charac"]; The core would session the array beforehand and load the appropriate translation file indicated by the core. The file would only be loaded once. The module would echo the element that sits in the index position. I am thinking the index would be the first 10 characters of the language the developer speaks: another plus for non-English speaking developers. It could also be a number, depending on responses to this letter. I figure an associative array would be just as fast as a numerically indexed array but I'm not sure. In any case, an associative array would be easier to read. I would also program a 'translation' module. That way a developer can assign users to the upkeep of different language files. It would keep track of additions and deletions and would point out incomplete language files before release. When the release is sound, the module would write the module's translation file. What I would like is input from anyone who develops international code. The reason we chose the preprocess route was speed. I want to know if this proposed system would cause delays or too much overhead. I would think that since your instructional text is usually brief, the memory concerns would be negligible. Let me know what you think by replying back to the list. Thanks for your time, Matthew McNaney Internet Systems Architect Electronic Student Services Email: ma...@tu... URL: http://phpwebsite.appstate.edu Phone: 828-262-6493 ICQ: 141057403 |
From: Matthew M. <ma...@tu...> - 2002-03-20 15:38:20
|
Greetings all, If you have been reading Sourceforge, there is a message about Alessandro Pisani and Mike Lansbury making a fork of phpWebSite entitled X-Web. Before everyone draws spurious conclusions: 1) Yes, we support them 2) No we are not mad =) 3) They say it will be compatible with the current core 4) It is not based on 'fallout' Do not read anything into this. They are acting on their own and not because we shunned them from the project. Alessandro is still a developer for phpWebSite. This is not a 'signal' that anything is happening to phpWebSite. It will continue as normal, though maybe a tad slower with Alex dividing his time ;) Please join me in supporting their ambition. Sincerely, Matthew McNaney Internet Systems Architect Electronic Student Services Email: ma...@tu... URL: http://phpwebsite.appstate.edu Phone: 828-262-6493 ICQ: 141057403 |
From: Alessandro P. (T. / J578) <al...@ti...> - 2002-03-14 23:43:15
|
I fixed a nasty and stupid bug in my code which prevented html <!-- --> to be accepted by check_html() Bye, Alessandro -- Alessandro "TXM" Pisani - al...@ti... - ICQ #2209087 phpWebSite Development Team http://phpwebsite.appstate.edu INWO Project coordinator http://inwoproject.sourceforge.net "I will carry you through, hicking and screaming, and in the end you will thank me" - Tyler Durden [from "Fight Club"] |
From: <dyn...@us...> - 2002-03-12 21:40:29
|
Mike, I put some info on the bugs in the bugtracker for the blocks script at sourceforge. Want to know if <javascript> is prevented from being put into blocks on purpose or a bug. Or anyone at appstate. This was not an issue prior to the move of blocks to a module. I'm gonna do some cleaning of the code due to the readability of the brackets opening and closing. So let me know if you are in the middle of working on it. So we don't submit anything at the same time. I'm gonna verify everything before I submit to CVS of course. :^) So just letting others know what I'm going to work on. Tat |
From: Vlad S. <vl...@bi...> - 2002-03-12 17:10:38
|
Hey people... I keep running into a problem with adding weblinks - somehow ' turns into '' when I save a link.. also, if I use a ' in a category name, all hell breaks loose, and SQL errors ensue. Another thing - You cannot have sub-categories with the same name even if they're under different main categories... Has anyone else noticed such behavior, or am I doing something wrong? later, Vlad |
From: Matthew M. <ma...@tu...> - 2002-03-11 18:23:05
|
Information on the new core has been updated. Go here to read more: http://phpwebsite.appstate.edu/mod.php?mod=userpage&menu=1504&page_id=27 Matthew McNaney Internet Systems Architect Electronic Student Services Email: ma...@tu... URL: http://phpwebsite.appstate.edu Phone: 828-262-6493 ICQ: 141057403 |