Menu
▾
▴
phpwebsite-developers — For our development team.
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: Todd O. <to...@da...> - 2001-04-03 02:00:20
|
Clayton Collie wrote the following on Saturday: >Ars Digita Community System >ACS in its later versions began to implement a more layered user (hence >permissions) structure, but based on my reading of the code, it really would >take a well tuned back end to deal with the type of queries they needed to >support it. definitely not for your garden variety ISP. thats one of the >reasons i stopped tracking it at version 3.xxx. The Zope architecture is >indeed nice, but i think they have custom serialization to handle their data >model. The ACS permission scheme looks very nice and very flexible. We would probably need to streamline the code some for performance reasons, but it definately gives us a level of granularity seen few other places. How does everyone else feel about this? --Todd |
|
From: Todd O. <to...@da...> - 2001-04-02 17:44:50
|
Re: [Phpwebsite-developers] binarycloudI've been reviewing binarycloud = this morning and don't see much new. Most of the classes are either = PEAR or from the class repository. The xml database setups and dumps = looked interesting, but I saw much more that I liked in phpGroupWare. --Todd |
|
From: Todd O. <to...@da...> - 2001-04-02 17:42:36
|
> I think we should code according to PEAR standards. I agree, but there are some things that aren't addressed in PEAR (at least yet). Most of the HTML markup is in echo statements now. I that what we want to continue to do? BinaryCloud.com and many others believe that there should not be ANY echo or print statements. This from BinaryCloud: ---Markup --Global Rules -Do not use echo or print for markup. Using echo & print obscures the markup, is time consuming to edit, is error prone, and will impede the progress of any project where non-php authors are involved. -Do not include complex logic in template files. Conditionals are the most complex logic allowed in templates. If you need to loop through an array, do it in the module, and call the template function recursively. -Declare all of your variables at the top, right under the function. Don't get globals, etc inside the code. In other words, do all of your setup at the top of the file. -It is nice if comments are wrapped to 80 chars, you'll probably get in the habit anyway - but it is not necessary. Tags cannot and should not be wrapped to 80 chars. Note that this standard applies to _all_ markup: html, wml, xml, etc. -This is a complex example, because this would be used as a 'master' template for a site. Template files associated with modules should be simple, and light on php code. They should not scare people who only know html. -Note the conspicuous absence of any comment header for the template function. Master templates must all use $tmpl_obj to get their list of modules, and some other miscellaneous values like page title, etc. It is not necessary to document this in every file, and adds quite a lot of redundant comments to the phtml masters. -Your module phtml files should be so simple and light on php logic that commenting them seems like a waste of time. (and is) -Every file must contain a header -You must place an html comment at the top & bottom of the html with the path to the file. (see format below) -Use html comments _ONLY_ when you are printing html. If the comment is about PHP code, use PHP comments. The purpose of the html comments is to allow html authors to locate code embedded in complex pages, so they can fix it easily. Diagnostic information is the only exception. Comments anyone, anyone... --Todd |
|
From: Brian W. B. <br...@ap...> - 2001-04-02 15:49:14
|
First, thanks to our current developers for the very valuable feedback they have provided regarding developing a detailed Roadmap for phpWebSite. We are now working on a draft of the Roadmap based on feedback from our current developers, as well as the ongoing discussions on this list and on the phpWebSite project site. This draft will then be distributed to our current developers for final review and comment. Once approved by the development team, the final roadmap will be posted both to this list and the phpWebSite project site. I know many of you are very anxious to receive this information. Please be patient. Important decisions are being made and we want to make sure that *good* decisions are made in the end. Once again, thank you for your continued involvement with phpWebSite. Your honesty, your ideas, and most of all, your hard work is appreciated. phpWebSite is on the way to becoming a great product because you have made the choice to be involved. Kind Regards, Brian W. Brown phpWebSite Project Manager -- Brian W. Brown Internet Systems Architect, ESS Student Development Room 269, John Thomas Hall Appalachian State University Boone, NC 28608 vox: 828-262-7124 fax: 828-262-2585 |
|
From: Brian W. B. <br...@ap...> - 2001-04-02 15:26:59
|
> Due to different syntactical rules in different languages the actual > language file is no good option. It would be much better to use > complete phrases containing all needed variables, so you can put them > in the sentence, where you need them. This would make all translations > much easier to handle and could avoid some very strange expressions and > phrases I had to use in the german translation. Agreed. There is no reason why the needed variables could not be included in the TRANSLATE[[....]] statements. Feel free to track these down in the core code and change them. If you look in the CVS at the Language "Changes" file: http://152.10.194.1/cvs/cvs.php/phpwebsite/make_distro/Changes You can note what has been deleted/changed/added in this file. This file is what the folks helping to keep the language files up-to-date should be using to keep any given language.pp file "in sync". Brian -- Brian W. Brown Internet Systems Architect, ESS Student Development Room 269, John Thomas Hall Appalachian State University Boone, NC 28608 vox: 828-262-7124 fax: 828-262-2585 |
|
From: Geoff S. <Ge...@Ho...> - 2001-04-02 14:46:15
|
> On Sat, Mar 31, 2001 at 02:44:54PM -0600, Geoff Staples wrote: > > Todd: > > > > Thanks for the suggestion of Mailman. However, I'm curious. Why > would I want > > to use a Python based program instead of a PHP based one? > > > Karsten's Reply: > Because it is one of the best known mailing list software > packages, it does > it's job _very_ well, has a very good interface, a complete > featureset, ... > ... > > It should be easy to integrate the web interface of mailman by means of a > plugin. > I'm sure all of the above is true. But, my concern is quite simple: If I add a Python plug-in to phpWebSite, then anyone who wants to use the plug-in has to have Python on their server in addition to PHP. I think it is counterproductive to pile on additional requirements for using phpWebSite. I wonder how we can find out whether many php servers also have Python installed? I'm sure Mailman is great, but ... Geoff |
|
From: Mike W. <wi...@ce...> - 2001-04-02 14:38:52
|
Hi, I recently found a really simple threaded forum script that has = basically two files and a sql file. I got it installed really easy. It = doesn't have an admin front end yet but the developer is working on it. = It also is open to the public to posting. If you want to take a look at = what I did on my test site you can see it here. = http://test.blackriverfalls.com/board.php if you want the script site = it's http://xhawk.net/discussion/ I don't have the ability to make it a = plug in yet but I'm learning :) winzor P.S. If it's a cheesy script please don't hurt my test site but feel = free to post test messages. |
|
From: Geoff S. <Ge...@Ho...> - 2001-04-02 14:30:58
|
Matt: Are you writing a NEW calendar for phpWebSite? Can you give a more specific time frame then "this month"? Will it have a user submission similar to user submission for news articles? AS FOR THE BUG in the current calendar: I installed phpWebSite at www.txsd16democrats.org and the calendar was screwed up. But, once I got an event for April into it, the calendar started working correctly. Then, I installed phpWebsite at www.glsendallas.org and the calendar seemed to work correctly "out of the box". Both are on the same server, so... ANYWAY, if I can make the existing calendar work by adding a few events to it, and you are writing a replacement, there's not much point to finding the bug. Can I do something to help with the new calendar? Geoff Geoff Staples, Dallas, Texas 75219-4432 Hostricity Web Hosting <http://www.hostricity.com/> -----Original Message----- From: php...@li... [mailto:php...@li...]On Behalf Of Matthew McNaney Sent: Monday, April 02, 2001 7:22 AM To: php...@li... Subject: Re: [Phpwebsite-developers] Fixing Calendar Bug Geoff, I am not planning on supporting the calendar included with phpWS any longer. Instead, I am concentrating on the plug-in conversion which should be completed this month. If you would like to fix the bug, we be more than happy to host the changes. Sincerely, Matthew McNaney > I'm having the problem with the screwed up months in the calendar. > Here's the bug report: > > https://sourceforge.net/tracker/index.php? func=detail&aid=405305&group_id=15 > 539&atid=115539 > > I'd like to go ahead and fix it, but, I don't want to step on anyone's > toes. > > It's assigned to Matthew. (So, if you are working on it ...) > > Anyway, I need it fixed ASAP, so, I'm happy to do it! > > Geoff > > Geoff Staples, > Founder > Action Agenda <http://www.actionagenda.com/> _______________________________________________ Phpwebsite-developers mailing list Php...@li... http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers |
|
From: Alain F. <al...@va...> - 2001-04-02 14:15:41
|
Chris, Try setting your locale to "ge" for a try... this works for me anyway, don't ask me why! Seems to be a bug somewhere.. :) > -----Message d'origine----- > De : php...@li... > [mailto:php...@li...]De la part de > Christian Schims > Envoye : lundi 2 avril 2001 15:55 > A : php...@li... > Objet : Re: [Phpwebsite-developers] French Language, general translation > woes ! > > [snip] > > My locale in the config file is DE, but it won't work. > > Chris > > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > |
|
From: Christian S. <chr...@sc...> - 2001-04-02 13:56:20
|
Karsten Dambekalns wrote: > > The script used to build the distribution now creates a list of all > TRANSLATE statements still found in the code after translating it. This > should help to spot some errors (in fact it did, I fixed a few bugs in the > german translation. Chris, I hope this is OK with you). Gr8, all that counts is the result, not the man who fixed the bug. But my issue is the syntactical problem we have. At the moment one phrase with a variable in the middle is broken in two independent translate statements that are independently sorted into the language file. NNot quite easy to kee thiungs together this way. > Well, that actually is because the mont and day names are not written as > TRANSLATE statements in the source, but are generated using the date > function. You would have to supply the proper locale setting to that > function to achieve the correct results. My locale in the config file is DE, but it won't work. Chris |
|
From: Matthew M. <mcn...@tu...> - 2001-04-02 13:28:01
|
Just to let everyone know. Brian is out ill today. Therefore, we will have to wait a little bit for us to review the roadmap. Have a great weekend, Matt |
|
From: Matthew M. <mcn...@tu...> - 2001-04-02 13:27:56
|
Geoff, I am not planning on supporting the calendar included with phpWS any longer. Instead, I am concentrating on the plug-in conversion which should be completed this month. If you would like to fix the bug, we be more than happy to host the changes. Sincerely, Matthew McNaney > I'm having the problem with the screwed up months in the calendar. > Here's the bug report: > > https://sourceforge.net/tracker/index.php? func=detail&aid=405305&group_id=15 > 539&atid=115539 > > I'd like to go ahead and fix it, but, I don't want to step on anyone's > toes. > > It's assigned to Matthew. (So, if you are working on it ...) > > Anyway, I need it fixed ASAP, so, I'm happy to do it! > > Geoff > > Geoff Staples, > Founder > Action Agenda <http://www.actionagenda.com/> |
|
From: Todd O. <to...@da...> - 2001-04-02 12:56:05
|
The case statements in Nuke are far too slow. phpGroupWare uses database lookups for translation and places the "inserted" or variable text in context with the static test. I don't know what type of performance issues it has, but it's apparently very accurate. --Todd |
|
From: Karsten D. <k.d...@tu...> - 2001-04-02 12:52:27
|
On Sat, Mar 31, 2001 at 02:44:54PM -0600, Geoff Staples wrote: > Todd: >=20 > Thanks for the suggestion of Mailman. However, I'm curious. Why would I w= ant > to use a Python based program instead of a PHP based one? Because it is one of the best known mailing list software packages, it does it's job _very_ well, has a very good interface, a complete featureset, ... I tried to write something similar in PHP once, but i stopped that project very soon. Sending lot's of emails (whether you use a loop or BCC or whatever) is not the task you love to do using PHP (IMHO). And to rephrase your question (somewhat): Why should I use something not written in Python, it it works?. It should be easy to integrate the web interface of mailman by means of a plugin. Just my 2c, Karsten --=20 Why do we have to hide from the police, daddy? Because we use emacs, son. They use vi. ----------------------------- mailto:k.d...@tu... w=B3: http://www.k-fish.de/ gpg: http://www.k-fish.de/mykeys.gpg |
|
From: Karsten D. <k.d...@tu...> - 2001-04-02 12:52:27
|
On Mon, Apr 02, 2001 at 01:52:10PM +0200, Christian Schims wrote: > Hi Alain, >=20 > it's right the same problem with the german translation. Additionally lots > of phrases and commands are not translated when the distro files are > generated, although the language file contains all information. For The script used to build the distribution now creates a list of all TRANSLATE statements still found in the code after translating it. This should help to spot some errors (in fact it did, I fixed a few bugs in the german translation. Chris, I hope this is OK with you).=20 > instance most day and month names still are in english - not only in the > calendar. Well, that actually is because the mont and day names are not written as TRANSLATE statements in the source, but are generated using the date function. You would have to supply the proper locale setting to that function to achieve the correct results. Regards, Karsten --=20 Why do we have to hide from the police, daddy? Because we use emacs, son. They use vi. ----------------------------- mailto:k.d...@tu... w=B3: http://www.k-fish.de/ gpg: http://www.k-fish.de/mykeys.gpg |
|
From: Karsten D. <k.d...@tu...> - 2001-04-02 12:52:27
|
On Fri, Mar 30, 2001 at 05:21:02PM -0500, Bob McCambridge wrote: > [ a lot of unnecessary quoting deleted ] Good to have you in the team (the more people help, the better) but I have to nag all of you again: I almost decided to not read your email (at least not immediately) because it seemed just tooo long. But it turned out that most of the text was quoted stuff, which you didn't in the remotest sense of the word answer to or comment on. So please try to avoid such fullquotings in the future. All of us, I should say. It makes handling the ever growing amount of emails flowing into the PHPWS mail folder easier. And it is easy to just delete some text, isn't it? Thank you, Karsten --=20 Why do we have to hide from the police, daddy? Because we use emacs, son. They use vi. ----------------------------- mailto:k.d...@tu... w=B3: http://www.k-fish.de/ gpg: http://www.k-fish.de/mykeys.gpg |
|
From: Alain F. <al...@va...> - 2001-04-02 12:16:15
|
Hi, Okay, I see there are more people that have the same problem. What is going to be done about it? Are we going to think of an intermediate solution so that foreign people can actually use the current phpWebSite before the new completely rewritten version is available? I'd surely hope so :) Anyone else, comments ? > -----Message d'origine----- > De : php...@li... > [mailto:php...@li...]De la part de > Frits Jensen > Envoyé : lundi 2 avril 2001 14:01 > À : 'php...@li...' > Objet : SV: [Phpwebsite-developers] French Language, general translation > woes ! > > > This is why I stopped the Danish translation project I started - I'm > observing the project as of now, because it would be way wierd > translated - > wouldnt want my name on it ;) > [...] |
|
From: Aaron A. <aa...@wc...> - 2001-04-02 12:08:21
|
Check out http://binarycloud.com (it may save some work for people looking to do the things described below): binarycloud is a platform for building web applications with PHP It includes basic services like authentication, permissions, a template engine, database abstraction etc., an extensive collection of libraries, and a framework for configuring the system and building your own logic. Also, binarycloud is compatible with PEAR. --- Aaron Adams |
|
From: Frits J. <FJ...@uv...> - 2001-04-02 12:01:40
|
This is why I stopped the Danish translation project I started - I'm observing the project as of now, because it would be way wierd translated - wouldnt want my name on it ;) I Know its a lot to ask, but a REM of where the translated phrase would appear also is kinda necessary for a proper translation. Often a sentence can mean very different things, depending on the context it is in, so to be given a phrase alone to translate eventually will produce some wierd resoults. Frits. > -----Oprindelig meddelelse----- > Fra: Christian Schims [mailto:chr...@sc...] > Sendt: 2. april 2001 13:52 > Til: php...@li... > Emne: Re: [Phpwebsite-developers] French Language, general translation > woes ! > > > Alain Fontaine wrote: > > > > Hi everyone, > > > > Today I wanted to correct a few mistakes in the french > translation of > > phpWebSite, but I have stopped quite quickly after I have > found a major > > problem with the current translation system. The problem I > am describing > > happens on a lot of different places actually, but to give > you an easy to > > understand example: > > Hi Alain, > > it's right the same problem with the german translation. Additionally > lots of phrases and commands are not translated when the distro files > are generated, although the language file contains all > information. For > instance most day and month names still are in english - not > only in the calendar. > > Due to different syntactical rules in different languages the actual > language file is no good option. It would be much better to > use complete > phrases containing all needed variables, so you can put them in the > sentence, where you need them. This would make all translations much > easier to handle and could avoid some very strange expressions and > phrases I had to use in the german translation. > > Any suggestions? > > Chris > > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > |
|
From: Christian S. <chr...@sc...> - 2001-04-02 11:53:13
|
Alain Fontaine wrote: > > Hi everyone, > > Today I wanted to correct a few mistakes in the french translation of > phpWebSite, but I have stopped quite quickly after I have found a major > problem with the current translation system. The problem I am describing > happens on a lot of different places actually, but to give you an easy to > understand example: Hi Alain, it's right the same problem with the german translation. Additionally lots of phrases and commands are not translated when the distro files are generated, although the language file contains all information. For instance most day and month names still are in english - not only in the calendar. Due to different syntactical rules in different languages the actual language file is no good option. It would be much better to use complete phrases containing all needed variables, so you can put them in the sentence, where you need them. This would make all translations much easier to handle and could avoid some very strange expressions and phrases I had to use in the german translation. Any suggestions? Chris |
|
From: W.D.Sumilang <wa...@on...> - 2001-04-01 21:40:38
|
I think we should code according to pear standards. __________________________________________________ FREE voicemail, email, and fax...all in one place. Sign Up Now! http://www.onebox.com |
|
From: Todd O. <to...@da...> - 2001-04-01 18:48:45
|
Are we going to standardize on (4) space indents and echo "" in lieu of
print("")?
--Todd
|
|
From: Alain F. <al...@va...> - 2001-04-01 16:40:02
|
Hi everyone,
Today I wanted to correct a few mistakes in the french translation of
phpWebSite, but I have stopped quite quickly after I have found a major
problem with the current translation system. The problem I am describing
happens on a lot of different places actually, but to give you an easy to
understand example:
In english, the word "No" can mean:
1. The negative answer to a question, in opposition to 'yes'
2. A quantitative qualifier, like in "there are no news", "there is no one
here"
What seems to have been done with phpWebSite is that the "same" [[No]] was
used for both meanings ! While with this setup, the sentences do make sense
in English, they don't make any sense in french anymore because there are
two (or even many more!) different words to express the two meanings of "no"
in french. For instance, in the admin tool you can read:
Non Category found. (should mean 'No category found')
First of all, there's a missing/wrong translation here, of course. "found"
is not a french word, and it reads "catégorie" in french. But the main
problem is the "non" you see there. NON means "No" as in "No thanks" or "No,
I haven't been there". In this sentence, however, it should be the second
meaning (quantity), as in "None found" --> "Aucune catégorie trouvée", and
not "Non catégorie trouvée".
There are a couple of other places that have the same problem, with
different words / strings. The source of the problem is that the same
english word ('no') can have different meanings, and while in english it's
okay to use the same word for different meanings, you just can't do so in
french (or other languages, for that matter).
What are we going to do about this? A customer of mine is waiting for the
french translation to get ready, and I don't know what I should tell him :)
Anyway, here's what I have corrected/added before stopping:
<-- snip -->
[[I forgot my password]] = [[J'ai oublié mon mot de passe]]
[[Registered user benefits include themes manager, comments configuration,
personal content box on home page, and more]] = [[Les utilisateurs
enregistrés profitent de la gestion des thèmes, de la configuration des
commentaires, de leur boîte de contenu personnelle, et bien plus]]
[[Name of image save]] = [[Nom de l'image sauvegardée]] /* saved =
sauvegardée */
------
Alain Fontaine
Analyst-Programmer
NVision s.à.r.l.
|
|
From: Geoff S. <Ge...@Ho...> - 2001-04-01 05:04:00
|
I'm having the problem with the screwed up months in the calendar. Here's the bug report: https://sourceforge.net/tracker/index.php?func=detail&aid=405305&group_id=15 539&atid=115539 I'd like to go ahead and fix it, but, I don't want to step on anyone's toes. It's assigned to Matthew. (So, if you are working on it ...) Anyway, I need it fixed ASAP, so, I'm happy to do it! Geoff Geoff Staples, Founder Action Agenda <http://www.actionagenda.com/> 3883 Turtle Creek Blvd., Suite 1812 Dallas, Texas 75219-4432 214.599.0260 Action Agenda is hosted as a public service by Hostricity Web Hosting <http://www.hostricity.com/> ActionAgenda.com is a Community Center for progressive and liberal activists to stay informed, find allies, and build support. |
|
From: Bob M. <web...@is...> - 2001-04-01 03:46:26
|
Hi everyone, I have seen a post not to long ago about this portal and saw no response from anyone...I would like to suggest everyone take a look at it here http://www.kodewulf.za.net/index.php this portal has a new blocksystem and here is the quote from the developers: There are no left-, right-, admin- and mainblock in this system. For this types of blocks exists only one in the new system. The Custom Block. You can set every blocktype as an admin block. You can set the displayorder for the blocks. You set the side of the block. Left or right. You set that the block is visible or not. For the blocktypes other then the customblock you can input a new Title for this block and add an addional content above or after the original content. you can also weigh the blocks in a specific order...these guys did a nice job IMHO... Bob McCambridge -----Original Message----- From: php...@li... [mailto:php...@li...]On Behalf Of Spiggy TheCat Sent: Saturday, March 31, 2001 10:36 PM To: php...@li... Subject: Re: [Phpwebsite-developers] Roadmap > > > The big deal here is this: topics, subtopics, etc. should be setup once >and > > available to news stories, the links subsystem, discussion forums, and all > > plug-ins that require the information. When someone registers, they should > > be able to put in their information once and have it used throughout the > > system so that their is no duplicate entry of information for each >plug-in. >Is this what everyone wants? This is where I'm currently working. If we do >want the "topics" and "subtopics" to be consistant across the organization, >then this needs to be in the core. Once the topics are defined for each >organization, then the plug-in modules can draw on them (topics) >immediately. i think it would make most sense this way. what id also like is to have a possibility of having a user portal kind of approach. not user submitted stuff (although they can) but user chosen content.. like choose a 'track' you're interested in and get news, articles etc on that topic. what i am thinking is choosing just one topic out of the options available... or if one of the topics is gardening and the user has no interest on it.. he/she can choose to ignore it completely. of course the admin could choose to override this (maybe the main topic IS gardening). anyway, i managed to accomplish a small victory Friday. phpwebsite will be considered as the portal for my college. woohoo! what phpws does is enough for now. im hoping the real deal will be functional when the testing is over :) paivi _______________________________________________ Phpwebsite-developers mailing list Php...@li... http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers |
5 messages has been excluded from this view by a project administrator.
