phpslash-devel Mailing List for phpSlash (Page 4)
Brought to you by:
joestewart,
nhruby
This list is closed, nobody may subscribe to it.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(45) |
Dec
(50) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(29) |
Feb
(49) |
Mar
(38) |
Apr
(22) |
May
(39) |
Jun
(21) |
Jul
(6) |
Aug
(9) |
Sep
(6) |
Oct
(26) |
Nov
(42) |
Dec
(19) |
2003 |
Jan
(15) |
Feb
(71) |
Mar
(40) |
Apr
(41) |
May
(28) |
Jun
(5) |
Jul
(25) |
Aug
|
Sep
(2) |
Oct
(50) |
Nov
(89) |
Dec
(19) |
2004 |
Jan
(21) |
Feb
(9) |
Mar
(5) |
Apr
(6) |
May
(7) |
Jun
|
Jul
(4) |
Aug
|
Sep
(14) |
Oct
(24) |
Nov
(3) |
Dec
|
2005 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2006 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Mike G. <mi...@op...> - 2004-02-04 20:52:55
|
I haven't checked this out yet, but it might be interesting in terms of looking at phpbb integration. Sorry, I'm not an IRC person Luis, otherwise I'd have joined you on #phpslash Looking closer at it it seems that postnuke largely rewrote phpBB2 to fit into postnuke.. Perhpas not a bad approach, but an expensive one. Mike -----Forwarded Message----- From: PHP Classes <hel...@ph...> To: mi...@op... Subject: [PHP Classes] Added a new class: phpBB login Date: Wed, 04 Feb 2004 09:26:04 +0000 You are getting this message because you voluntarily subscribed to the PHP Classes site. To change your newsletter or alert messages delivery options, see the instructions at the bottom of this message. ___________________________________________________________________________ A new class was added to "PHP Classes" repository. Name: phpBB login Author: MARY Matthieu <ma...@if...> Description: This class is meant to provide user authentication to sites that have already installed the phpBB forum application database. This class avoids the need to create or install another authentication system if you already have installed or plan to install phpBB. For now, this class supports only user authetication but not to add, update or delete user records. These features are planned to be supported in future versions of this class. URL: http://www.phpclasses.org/browse/package/1474.html ___________________________________________________________________________ PHP Classes site tip of the day: o Friends of the PHP Classes site Be recognized publically for helping the site community to grow. http://www.phpclasses.org/friends.html o Read about other interesting tips http://www.phpclasses.org/tips.html?tip=6 ___________________________________________________________________________ If you are not interested in receiving any more messages like this one, or want to switch the message format between text and HTML, go to the user options page ( http://www.phpclasses.org/user_options.html ) and change the respective delivery options. -- Mike Gifford, OpenConcept Consulting Free Software for Social Change -> http://www.openconcept.ca Stop Cdn Pension Plan War Investments -> http://coat.openconcept.ca/ Another world is not only possible, she is on her way -Arundhati Roy |
From: Mike G. <mi...@op...> - 2004-02-02 19:25:16
|
Hi Luis, On Mon, 2004-02-02 at 01:04, Luis M wrote: > [...] > >I like phpBB too.. > > > > > Examples: > > > phpslash: http://www.latinomixed.com > > > phpBB: http://foro.latinomixed.com > > > >Ok.. But how did you integrate it? Does phpBB use phpSlash templates? > >Is there a common authorization? > Ooops! sorry that I took so long to respond. It happens online.. Thanks for making your way to the response :) > At first I originally wanted to make them both authenticate againts a LDAP > database since I can control the schema of the files (and it would be just > simpler to maintain if I want to allow some users to have valid email > addresses @latinomixed.com and not to others, yet all users can authenticate > against the same DB). We've done some work with that for Back-End.. Was a year ago so it isn't at all fresh now (and I didn't do the work).. But there's code.. The client ended up using PAM as a reference.. > However, I just make both pages look similar and never really got the time > to update the user DB's so that they can share "containers", meaning use > PHPLIB to authenticate against an LDAP DB for both phpBB and phpSlash. > Now that this subject has come to my mind again, I'll try to do my best to > look into that (I know a lot more Perl/PHP/LDAP now to do the transition > simpler: Perl first to pull the records, and PHP to create new users against > a single Sign On/User Creation page.) So there'd be a cron run ever few minutes to check & transfer as required? > I guess that with 0.8 this can be done a lot simpler (modules modules > modules) > What do you think? The current version of BE is still based on 0.7 (as we haven't had time to migrate all of our code).. But if you get the authorization working against 0.8 then it should be easier.. > We can work together on this if you so want. Let's meet on #phpslash every > now and then and divide the work needed. I think this can be accomplish very > simply (with Perl or PHP). Just php would make it much more transferable if it is possible. > Essentially we will need: > 1. Migration scripts (simple) > 2. Authentication mechanism (PHP Classes for both projects) (a bit harder) > 3. Single User Creation process > 4. Other minor stuff (cookie names, whatever other cookie related stuff) > 5. Test test test Might also be useful to look at how other folks have done this.. PostNuke has been doing this for a while.. Anyone know any others that do? > I'm up for this. And I know the guys at Back-End might love this also. Yup! :) > On a side note, Joe, I need you to assign the Bugs to me so that I can close > as many as I can (and ask people who can deal with the ones I can't), so > that we can get ready for a "beta" 0.8. Cool! > P.S. Please note that I'm not subscribe to back-end-development mailinglist. I didn't get a bounce, but who knows.. They'll get my response for sure.. Mike -- Mike Gifford, OpenConcept Consulting Free Software for Social Change -> http://www.openconcept.ca Stop Cdn Pension Plan War Investments -> http://coat.openconcept.ca/ Another world is not only possible, she is on her way -Arundhati Roy |
From: Joe S. <joe...@us...> - 2004-02-02 16:48:27
|
> The url for the website is: http://s94043039.onlinehome.us looking at: http://s94043039.onlinehome.us/test.php and http://s94043039.onlinehome.us/test.php?mode=phpinfo I would suggest turning off session.use_trans_sid and magic_quotes_gpc. > > > Is there some kind of a known bug that causes this problem? > > > Not that has been reported. > >Does your provider have phpaccelerator installed? > How would I find out if my provider has phpaccelerator installed? It's listed on the phpinfo page in the Zend copyright area I believe. You don't have it installed. This program makes use of the Zend Scripting Language Engine: Zend Engine v1.2.0, Copyright (c) 1998-2002 Zend Technologies >I had to start using >mmcache instead becaus of intermittent errors like this. > Were you errors at random? By me, sometimes they work fine and the other times I > get this "internal server error". I went back and looked at the errors reported. It was allowed memory being exceeded, and was intermittent. Oh yeah. Please reply in text-only to the list. sorry, Joe > Thanks, > Daniel |
From: Luis M <le...@ho...> - 2004-02-02 06:05:00
|
[...] >I like phpBB too.. > > > Examples: > > phpslash: http://www.latinomixed.com > > phpBB: http://foro.latinomixed.com > >Ok.. But how did you integrate it? Does phpBB use phpSlash templates? >Is there a common authorization? > >Mike Ooops! sorry that I took so long to respond. At first I originally wanted to make them both authenticate againts a LDAP database since I can control the schema of the files (and it would be just simpler to maintain if I want to allow some users to have valid email addresses @latinomixed.com and not to others, yet all users can authenticate against the same DB). However, I just make both pages look similar and never really got the time to update the user DB's so that they can share "containers", meaning use PHPLIB to authenticate against an LDAP DB for both phpBB and phpSlash. Now that this subject has come to my mind again, I'll try to do my best to look into that (I know a lot more Perl/PHP/LDAP now to do the transition simpler: Perl first to pull the records, and PHP to create new users against a single Sign On/User Creation page.) I guess that with 0.8 this can be done a lot simpler (modules modules modules) What do you think? We can work together on this if you so want. Let's meet on #phpslash every now and then and divide the work needed. I think this can be accomplish very simply (with Perl or PHP). Essentially we will need: 1. Migration scripts (simple) 2. Authentication mechanism (PHP Classes for both projects) (a bit harder) 3. Single User Creation process 4. Other minor stuff (cookie names, whatever other cookie related stuff) 5. Test test test I'm up for this. And I know the guys at Back-End might love this also. On a side note, Joe, I need you to assign the Bugs to me so that I can close as many as I can (and ask people who can deal with the ones I can't), so that we can get ready for a "beta" 0.8. P.S. Please note that I'm not subscribe to back-end-development mailinglist. ----)(----- Luis Mondesi System Administrator LatinoMixed.com "We think basically you watch television to turn your brain off, and you work on your computer when you want to turn your brain on" -- Steve Jobs in an interview for MacWorld Magazine 2004-Feb No .doc: http://www.fsf.org/philosophy/no-word-attachments.es.html _________________________________________________________________ MSN Search, le moteur de recherche qui pense comme vous ! http://search.msn.fr/worldwide.asp |
From: DANIEL G. <dan...@ho...> - 2004-02-01 03:58:53
|
<html><div style='background-color:'><DIV class=RTE><mailto:php...@li...?subject=unsubscribe><mailto:php...@li...><mailto:php...@li...?subject=help><mailto:php...@li...?subject=subscribe>>On Thu, Jan 29, 2004 at 02:12:31PM -0500, DANIEL GOLDMAN wrote: </DIV> <DIV></DIV>> > Hello, I am new to the phpsash mailing lists and I don't know on which list <DIV></DIV>> > to post this particular problem, so I am posting it on two list. Sorry if <DIV></DIV>> > you are getting this twice. <DIV></DIV>> > <DIV></DIV>> > I just installed phpslash Version: 0.7.2 everything seems to be working <DIV></DIV>> > fine. However, about every 10 page requests, I get a "500 Internal Server <DIV></DIV>> > Error". This seems to be happening at random. If I reload the page that <DIV></DIV>> > gave me the error, it then loads the page properly. <DIV></DIV>> > <DIV></DIV>> <DIV></DIV> <P>>What's the url? </P> <P> </P> <P>The url for the website is: <A href="http://s94043039.onlinehome.us">http://s94043039.onlinehome.us</A></P> <DIV></DIV>> > Is there some kind of a known bug that causes this problem? <DIV></DIV>> > <DIV></DIV>> <DIV></DIV>>Does your provider have phpaccelerator installed? <DIV></DIV> <P>How would I find out if my provider has phpaccelerator installed? </P> <P> </P> <P> >I had to start using </P> <DIV></DIV> <P>>mmcache instead becaus of intermittent errors like this. </P> <DIV></DIV> <DIV> </DIV> <DIV>Were you errors at random? By me, sometimes they work fine and the other times I get this "internal server error".</DIV> <P></mailto:php...@li...?subject=subscribe></mailto:php...@li...?subject=help></mailto:php...@li...></mailto:php...@li...?subject=unsubscribe> </P> <P> </P> <P>Thanks,</P> <P>Daniel</P></div><br clear=all><hr> <a href="http://g.msn.com/8HMAENUS/2740??PS=">Check out the new MSN 9 Dial-up fast & reliable Internet access with prime features!</a> </html> |
From: Mike G. <mi...@op...> - 2004-01-31 12:56:52
|
that's the minimum price to get back phpslash.org. I've put in an offer and perhaps it will be accepted in the next 7 days. I'll report whatever I hear back from the sudo folks back to the group. Mike -- Mike Gifford, OpenConcept Consulting Free Software for Social Change -> http://www.openconcept.ca Stop Cdn Pension Plan War Investments -> http://coat.openconcept.ca/ Another world is not only possible, she is on her way -Arundhati Roy |
From: Joe S. <joe...@us...> - 2004-01-30 22:22:42
|
On Thu, Jan 29, 2004 at 02:12:31PM -0500, DANIEL GOLDMAN wrote: > Hello, I am new to the phpsash mailing lists and I don't know on which list > to post this particular problem, so I am posting it on two list. Sorry if > you are getting this twice. > > I just installed phpslash Version: 0.7.2 everything seems to be working > fine. However, about every 10 page requests, I get a "500 Internal Server > Error". This seems to be happening at random. If I reload the page that > gave me the error, it then loads the page properly. > What's the url? > Is there some kind of a known bug that causes this problem? > Does your provider have phpaccelerator installed? I had to start using mmcache instead becaus of intermittent errors like this. > Here are some of the specs: > Hosting provider: 1and1 > PHPSlash Version: 0.7.2 > PHP Version: 4.2.3 > PHP Major Version: 4 > PHP Minor Version: 3 > > > Also, is jpcache installed and running with the default setup or do I have > do manually install it? > It is installed using the db for cache storage. You might change to file based or disable to test. Joe > Thanks, > Daniel Goldman > > _________________________________________________________________ > Let the new MSN Premium Internet Software make the most of your high-speed > experience. http://join.msn.com/?pgmarket=en-us&page=byoa/prem&ST=1 > > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > Phpslash-devel mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpslash-devel |
From: DANIEL G. <dan...@ho...> - 2004-01-30 21:43:29
|
Hello, I am new to the phpsash mailing lists and I don't know on which list to post this particular problem, so I am posting it on two list. Sorry if you are getting this twice. I just installed phpslash Version: 0.7.2 everything seems to be working fine. However, about every 10 page requests, I get a "500 Internal Server Error". This seems to be happening at random. If I reload the page that gave me the error, it then loads the page properly. Is there some kind of a known bug that causes this problem? Here are some of the specs: Hosting provider: 1and1 PHPSlash Version: 0.7.2 PHP Version: 4.2.3 PHP Major Version: 4 PHP Minor Version: 3 Also, is jpcache installed and running with the default setup or do I have do manually install it? Thanks, Daniel Goldman _________________________________________________________________ Let the new MSN Premium Internet Software make the most of your high-speed experience. http://join.msn.com/?pgmarket=en-us&page=byoa/prem&ST=1 |
From: Lars H. <he...@qu...> - 2004-01-30 16:44:17
|
Hi, Just a hint (don't know, if someone has recognized it): phpslash.org doesn't points anymore to phpslash.sf.net, but is for sale. :( Regards, Lars |
From: Tim V. <dj...@si...> - 2004-01-22 19:33:32
|
On Wed, 21 Jan 2004, Joe Stewart wrote: > phorum5 has a script for integrating into other scripts that does call all of those > scripts from central index file. I think we can just capture that output using output > buffering. It's been awhile since I've looked at it. ... > I would suggest integrating phorum5 as a start instead of the current stable stuff. > It is a complete rewrite. ... > At this point I decided to wait till phorum5 was more stable. At the time it was > only in cvs and not near any kind of release. > > I would like to help get phorum5 working as psl0.8 module first. This is one of > the modules I want available when psl0.8 is released. > > After that, maybe help. backport to BE0.7 Hi All, After Joe's comment I started looking at the phorum5 code. And it looks like it's getting into a stable state. They already had some alfa releases and the phorum project is using the phorum5 code to power some of the phorums. So I got the a CVS snapshot of phorum5 and first installed it on it's own. And it seems to work nicely. So after setting up a testforum I decided to try the integration into BE0.7. The phorum5 code includes a "portable" directy that basicaly contains the code you can use to "import" phorum5 into your own code. It's wraps the phorum5 code in a function and provides some hooks to make sure that URL's are read and created correctly. Well, I've got in working, but not completely. The import itself seems to be working. I can get different phorum5 pages to appear with BE, and the URL translation also works. The only problem I still seems to have has to do with the phorum5 variables/session support. I can browse the forums ok using the phorum5 code directly, but using the portable code I get a permission denied. It just looks like I still need to setup certain variables, but I'm sure I'll get it to work. The result it that I can get phorum5 to work with only editing the templates and the portable code. And I don't need to edit any of the actual phorum5 code. This ofcourse won't be true anymore if we continue for a more tighter integration. But the idea, I guess, would be to replace certain key files that link to the BE/PSL code instead of phorum5's own code. (DB, Template, Users/Authentication,...) So for the moment I'll continue to work on getting phorum5 integrated into BE in a basic mode (without changing anything to the actual phorum5 code). Since I don't need further integration for the site I'm currently building. The only thing maybe would be dynamic language selection. After that I'm willing to continue working in tighter integration. So we can start discussing what we want to have integrated and where the priorities are. About phpbb or other forums/messageboards. For me their are 2 kind of messageboars and they serve a different audience : The more lightweight/simple ones (like Phorum) are for sites where the main focus is on the content, distributing a message, serve a general audience. The goal of the messageboard here is to provide another way of communication between the site owners and the visitors. The big, full-featured messageboards (phpbb,...) are for sites that would like to create communities and the messageboard would be primary please in which that community would communicate. Ok, all that intro to say this. I feel that both messageboard (phorum and phpbb) have a reason to exist as modules/plugins/extensions for BE/PSL. You would select the messageboard that fits the kind of website you are building, running. For me personaly, all the websites I've build/run/... only need the features given by phorum. But I encourage anyone to also work on a port of phpbb or any other large mesageboard. Maybe we could even work together on certain areas. On that note, let the comments flow ;-) Kind regards, Tim Verhoeven -- ====================================================================== Tim Verhoeven Linux & Open Source Specialist GSM : 0479 / 88 11 83 + e-business solutions Email : dj...@si... + consulting URL : www.sin.khk.be/~dj/ + Server consolidation ====================================================================== |
From: Mike G. <mi...@op...> - 2004-01-22 04:21:02
|
Hi Luis, On Wed, 2004-01-21 at 22:00, Luis M wrote: > >I would like to help get phorum5 working as psl0.8 module first. This is > >one of > >the modules I want available when psl0.8 is released. > >After that, maybe help. backport to BE0.7 > >thanks, > >Joe > (Sorry for the long un-clean post ... but... kept it for consistency...) I nixed most of it.. but it's not like it's taking up a lot of bandwidth.. > IMHO it's a lot easier to integrate phpBB and it's a lot nicer than Phorum: I like phpBB too.. > Examples: > phpslash: http://www.latinomixed.com > phpBB: http://foro.latinomixed.com Ok.. But how did you integrate it? Does phpBB use phpSlash templates? Is there a common authorization? Mike -- Mike Gifford, OpenConcept Consulting Free Software for Social Change -> http://www.openconcept.ca Stop Cdn Pension Plan War Investments -> http://coat.openconcept.ca/ Another world is not only possible, she is on her way -Arundhati Roy |
From: Luis M <le...@ho...> - 2004-01-22 03:01:07
|
>On Wed, Jan 21, 2004 at 10:05:36AM -0500, Mike Gifford wrote: > > Hello, > > > > Thought that I'd forward this question over to the phpSlash list to see > > if anyone has done anything like this and would have some suggestions. > > Tim's looking to bring this into Back-End, but hopefully we'd be able to > > bring that over to PSL pretty easily to add to the new foundry. > > > > Mike > > > > -----Forwarded Message----- > > From: Tim Verhoeven <dj...@si...> > > To: Back-end Development list ><bac...@li...> > > Subject: [Back-end-development] Integrating Phorum into Back-end > > Date: Wed, 21 Jan 2004 11:45:19 +0100 > > > > Hey, > > > > As some of you know I'm trying to integrate the Phorum messageboard > > (www.phorum.org) into Back-end. Yesterday I've made some first attempts >at > > it. This using the BE_survey.php file as a example. (Uses PHP's output > > buffering and includes). > > > > This allowed me to get started with it and get a feeling on how the >Phorum > > code is build. > > Basically each function is written in a seperate php file. Some basic > > functions are present in common.php. But all the rest are standalone. So > > no OO or functions calls we can use. There also is no central index file > > that controls the flow, so a typical phorum page contains links to a lot > > of different files. > >phorum5 has a script for integrating into other scripts that does call all >of those >scripts from central index file. I think we can just capture that output >using output >buffering. It's been awhile since I've looked at it. > >I would suggest integrating phorum5 as a start instead of the current >stable stuff. >It is a complete rewrite. > > > Templates is very simple, they just include a header and footer into the > > output. > >This is how I integrated phorum into phpslash. I changed the headers to >use the >phpslash config files, header, columns and footer. Here are some old >patches: > >[ 541835 ] Phorum w/ phpSlash look and feel. >http://sourceforge.net/tracker/index.php?func=detail&aid=541835&group_id=10566&atid=310566 > >and an older: > >[ 541701 ] Simple Phorum header and footer files. >http://sourceforge.net/tracker/index.php?func=detail&aid=541701&group_id=10566&atid=310566 > >phorum5 does have its own templating system. We may be able to tack some >stuff in >there easier. It compiles the templates to php and caches them. I think >you can >have phpblocks in the templates, but I'm not sure. > > > For DB they use a abstraction layer (nothing standard). > > > >At one time I had a phplib abstraction file for phorum5. It's not too >hard. I >think Brian made a couple of changes that I suggested along the way. > > > As I understand it Back-end needs it's content passed (using a variable, > > function, ...). So there are some strategies to make Phorum integrate >into > > Backend : > > > > 1) Make a "index" file ourself that intercepts all links made on phorum > > pages and use those to select to correct page to include. > > Problems : we need to parse the get arguments and forward those and > > edit each file to change all <a> tags. > > 2) Make functions for each phorum file and have a "index" file that >calls > > the required function. So we don't need to parse the get arguments. > > Problems : a lot of rewriting, we still could use PHP output >buffering > > to reduce that workload. > > 3) Rewrite it into a "real" Backend module/plugin with a class file > > containing all functions. This allows to rewrite all stuff to use > > Back-end provided functions (DB, Session, cookies,...) > > Problems : a lot ot work, no real quick results. > > > >Yeah. I didn't get this far yet. > > > So now for discussion. Did I miss another way to do this. What is the >best > > option to choose. As I see it, it will be nearly impossible to make the > > ingration work without touching any of the phorum files. So for me at >the > > moment I'm more going for option 3. > > > >That was my conclusion with the stable tree too. The authorization can be >done. >You can patch the login process to preauth BE/PSL. Then change the login >links to >the phorum login page. I got this to work. I wanted to auth phorum using >the >phplib auth, but went the brute force way to get something working. I >never >consolidated registration. > >At this point I decided to wait till phorum5 was more stable. At the time >it was >only in cvs and not near any kind of release. > > > Any other ideas, sugggestions, ... > > > >I would like to help get phorum5 working as psl0.8 module first. This is >one of >the modules I want available when psl0.8 is released. > >After that, maybe help. backport to BE0.7 > >thanks, > >Joe (Sorry for the long un-clean post ... but... kept it for consistency...) IMHO it's a lot easier to integrate phpBB and it's a lot nicer than Phorum: Examples: phpslash: http://www.latinomixed.com phpBB: http://foro.latinomixed.com ----)(----- Luis Mondesi System Administrator LatinoMixed.com le...@ho... No .doc: http://www.fsf.org/philosophy/no-word-attachments.es.html Public signature: http://www.latinomixed.com/lems1/public-a.asc _________________________________________________________________ MSN Messenger : discutez en direct avec vos amis ! http://www.msn.fr/msger/default.asp |
From: Joe S. <joe...@us...> - 2004-01-21 15:35:30
|
On Wed, Jan 21, 2004 at 10:05:36AM -0500, Mike Gifford wrote: > Hello, > > Thought that I'd forward this question over to the phpSlash list to see > if anyone has done anything like this and would have some suggestions. > Tim's looking to bring this into Back-End, but hopefully we'd be able to > bring that over to PSL pretty easily to add to the new foundry. > > Mike > > -----Forwarded Message----- > From: Tim Verhoeven <dj...@si...> > To: Back-end Development list <bac...@li...> > Subject: [Back-end-development] Integrating Phorum into Back-end > Date: Wed, 21 Jan 2004 11:45:19 +0100 > > Hey, > > As some of you know I'm trying to integrate the Phorum messageboard > (www.phorum.org) into Back-end. Yesterday I've made some first attempts at > it. This using the BE_survey.php file as a example. (Uses PHP's output > buffering and includes). > > This allowed me to get started with it and get a feeling on how the Phorum > code is build. > Basically each function is written in a seperate php file. Some basic > functions are present in common.php. But all the rest are standalone. So > no OO or functions calls we can use. There also is no central index file > that controls the flow, so a typical phorum page contains links to a lot > of different files. phorum5 has a script for integrating into other scripts that does call all of those scripts from central index file. I think we can just capture that output using output buffering. It's been awhile since I've looked at it. I would suggest integrating phorum5 as a start instead of the current stable stuff. It is a complete rewrite. > Templates is very simple, they just include a header and footer into the > output. This is how I integrated phorum into phpslash. I changed the headers to use the phpslash config files, header, columns and footer. Here are some old patches: [ 541835 ] Phorum w/ phpSlash look and feel. http://sourceforge.net/tracker/index.php?func=detail&aid=541835&group_id=10566&atid=310566 and an older: [ 541701 ] Simple Phorum header and footer files. http://sourceforge.net/tracker/index.php?func=detail&aid=541701&group_id=10566&atid=310566 phorum5 does have its own templating system. We may be able to tack some stuff in there easier. It compiles the templates to php and caches them. I think you can have phpblocks in the templates, but I'm not sure. > For DB they use a abstraction layer (nothing standard). > At one time I had a phplib abstraction file for phorum5. It's not too hard. I think Brian made a couple of changes that I suggested along the way. > As I understand it Back-end needs it's content passed (using a variable, > function, ...). So there are some strategies to make Phorum integrate into > Backend : > > 1) Make a "index" file ourself that intercepts all links made on phorum > pages and use those to select to correct page to include. > Problems : we need to parse the get arguments and forward those and > edit each file to change all <a> tags. > 2) Make functions for each phorum file and have a "index" file that calls > the required function. So we don't need to parse the get arguments. > Problems : a lot of rewriting, we still could use PHP output buffering > to reduce that workload. > 3) Rewrite it into a "real" Backend module/plugin with a class file > containing all functions. This allows to rewrite all stuff to use > Back-end provided functions (DB, Session, cookies,...) > Problems : a lot ot work, no real quick results. > Yeah. I didn't get this far yet. > So now for discussion. Did I miss another way to do this. What is the best > option to choose. As I see it, it will be nearly impossible to make the > ingration work without touching any of the phorum files. So for me at the > moment I'm more going for option 3. > That was my conclusion with the stable tree too. The authorization can be done. You can patch the login process to preauth BE/PSL. Then change the login links to the phorum login page. I got this to work. I wanted to auth phorum using the phplib auth, but went the brute force way to get something working. I never consolidated registration. At this point I decided to wait till phorum5 was more stable. At the time it was only in cvs and not near any kind of release. > Any other ideas, sugggestions, ... > I would like to help get phorum5 working as psl0.8 module first. This is one of the modules I want available when psl0.8 is released. After that, maybe help. backport to BE0.7 thanks, Joe > Regards, > Tim Verhoeven > > |
From: Mike G. <mi...@op...> - 2004-01-21 15:05:44
|
Hello, Thought that I'd forward this question over to the phpSlash list to see if anyone has done anything like this and would have some suggestions. Tim's looking to bring this into Back-End, but hopefully we'd be able to bring that over to PSL pretty easily to add to the new foundry. Mike -----Forwarded Message----- From: Tim Verhoeven <dj...@si...> To: Back-end Development list <bac...@li...> Subject: [Back-end-development] Integrating Phorum into Back-end Date: Wed, 21 Jan 2004 11:45:19 +0100 Hey, As some of you know I'm trying to integrate the Phorum messageboard (www.phorum.org) into Back-end. Yesterday I've made some first attempts at it. This using the BE_survey.php file as a example. (Uses PHP's output buffering and includes). This allowed me to get started with it and get a feeling on how the Phorum code is build. Basically each function is written in a seperate php file. Some basic functions are present in common.php. But all the rest are standalone. So no OO or functions calls we can use. There also is no central index file that controls the flow, so a typical phorum page contains links to a lot of different files. Templates is very simple, they just include a header and footer into the output. For DB they use a abstraction layer (nothing standard). As I understand it Back-end needs it's content passed (using a variable, function, ...). So there are some strategies to make Phorum integrate into Backend : 1) Make a "index" file ourself that intercepts all links made on phorum pages and use those to select to correct page to include. Problems : we need to parse the get arguments and forward those and edit each file to change all <a> tags. 2) Make functions for each phorum file and have a "index" file that calls the required function. So we don't need to parse the get arguments. Problems : a lot of rewriting, we still could use PHP output buffering to reduce that workload. 3) Rewrite it into a "real" Backend module/plugin with a class file containing all functions. This allows to rewrite all stuff to use Back-end provided functions (DB, Session, cookies,...) Problems : a lot ot work, no real quick results. So now for discussion. Did I miss another way to do this. What is the best option to choose. As I see it, it will be nearly impossible to make the ingration work without touching any of the phorum files. So for me at the moment I'm more going for option 3. Any other ideas, sugggestions, ... Regards, Tim Verhoeven ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Back-end-development mailing list Bac...@li... https://lists.sourceforge.net/lists/listinfo/back-end-development -- Mike Gifford, OpenConcept Consulting Free Software for Social Change -> http://www.openconcept.ca Stop Cdn Pension Plan War Investments -> http://coat.openconcept.ca/ Another world is not only possible, she is on her way -Arundhati Roy |
From: Luis M <le...@ho...> - 2004-01-19 05:06:53
|
Now that we have more documentation on phpslash for developers and for users, and also we have more and more people interested in the project, we are getting closer and closer to a stable (gold) release for phpslash 0.8. As mentioned in previous posts, the translator's documentation is up in phpslash.sf.net and can be access from within the phpslash-dev module in CVS (sgml files). The new modules rock and we all can think of a million modules we can write to extend phpslash. For the adventurers who want to add modules you can check Joe's red hot phpslashforge project: http://phpslashforge.org/. Now there is no excuse why anybody would fork the project :-) or have to patch when new releases come ;-) I was thinking maybe we should have a simple "skel" module that people can use to write their own -- preset with values that all modules should have. Looking at the big picture, I have been running successfully a site based on phpslash-0.8 "alpha" release and I had to say that it has been very stable -- after a few modifications which were incorporated to CVS. Looking into the future, I'll try to add somehow the setup.php script I wrote and use this to edit the config.ini.php file that the current config_setup.php spits out. Also, I would like to close all bugs from the SourceForge project, so I'll try my best to resolve all bugs ( I mean it ). And if possible, look into the Feature Requests. So, if somebody has some free time and want to squash some bugs with me, let me know. After that, and some more testing, we should be ready for a beta release. Comments? Note to translators: =========== Please contact me as soon as possible -- either thru this list or to my email address directly (please CC Joe). I want to get an idea of who is in charge of what translations so that we can update the CREDITS file with new information before we do the next release -- this file is very, very outdated! Joe, it would be nice if you can do a flow chart in Dia format representing the "flow" of a typical phpslash site ;-) (For developers only of course). This file would contain the same information that you emailed in plain text -- I was about to start one, but, you know the flow better. What do you think? ----)(----- Luis Mondesi System Administrator LatinoMixed.com le...@ho... No .doc: http://www.fsf.org/philosophy/no-word-attachments.es.html Public signature: http://www.latinomixed.com/lems1/public-a.asc _________________________________________________________________ MSN Messenger : discutez en direct avec vos amis ! http://www.msn.fr/msger/default.asp |
From: Joe S. <joe...@us...> - 2004-01-16 16:56:14
|
Announcing phpslashforge.org. A dedicated place for phpslash modules and skins. http://phpslashforge.org/ Just started now. Let me know what you think and if it is needed. I'm going to put a stable and dev demo there sometime soon. So far, I've only put a simple "While You Were Out" module up. http://phpslashforge.org/projects/wywo/ If you find any glaring problems, don't be surprised, just tell me or Aric. Joe |
From: Joe S. <jo...@be...> - 2004-01-16 16:45:07
|
Module layout in psl0.8 modules are located in include/modules/modulename/ This modulename directory is mapped to what the registered name for psl is in the ini file. Modules not defined there are not available. admin.php - if there is any administration for the module index.php - public access any class files in this module are located here. templates subdirectory - module templates should be located in this directory. These are english templates applied to the default/top parent skin. Any skin/language changes should be done in the include/templates directory. plugins - the options mechanism can call plugins much the same way as block_render classes.. plugins requested will be searched for here. index.php - for psl modules, we add the required classes and bring in $_PSL, and $ary - note that we are not in the global namespace. get the content - The environment available is the session, auth, perm, $_PSL, $ary, and functions.inc. return the content - no direct output. All output is to be returned to the caller. non psl modules can use output buffering to capture output and return. admin.php - for psl modules, we add the required classes, etc. parse _POST variables into $ary apply actions in the "submit" _GET or _POST variable as required and approved. return the output any other pages needed can be called via _GET variables. blocks needed can be called via block_options. There probably isn't any need for new block_render_classes. They should just be another module page or template. Joe |
From: Joe S. <joe...@us...> - 2004-01-16 16:24:32
|
Okay, getting my php hat on again for a little bit - Anatomy of a pageview in psl-0.8 This is probably not entirely correct or complete. Using public_html/index.php browser sends request config.php is loaded. - config.ini.php parsed into $_PSL array. sets up phplib in include/class/phplib. test for unconfigured new install - This can be removed after installation setup other $_PSL variables. add class requirements jpcache - TODO move to function/method if cached, skip everything and spit out the page else go on with pageview and update the cache Load _GET variables into $ary menu definitions phplib page_open - php4 session, auth, and perms timezone set default options set page title login if requested set module file if not in _GET request [default is index.php] call block_module index.php - add block class requirements instantiate block object call page blocks (block_render_page) - This is basically the old index page running getBlocks on the columns and deciding which index template is correct. blocks are returned for the section and user perms top blocks - header, topicbar, navbar left, right blocks - whatever defined for the section. center block - module block calls story module by default unless set in _GET or block option add story class requirements instantiate story object call getStories getStories applies the options in $ary, individual story options including template and output plugins. bottom blocks - bottom navbar, footer return block module into $content variable. display $content variable. phplib page_close. That is a simplified look. There is much flexibility in the block setups. Joe |
From: Joe S. <joe...@us...> - 2004-01-16 14:57:41
|
On Thu, Jan 15, 2004 at 03:25:39PM -0500, Luis M wrote: > >On Thu, Jan 15, 2004 at 03:31:14AM -0800, Xavier Paris Roig wrote: > >> > >> Hi guys, > >> > >> > >> > >> I would like to help in the development of phpSlash. I have > >> > >> some free time to dedicate on this project (translations, > >> > >> interface design, tester...) :) > >> > >> > > > >Hello, > > > >I'll get with you on things you can help with. > > > >Luis will send info on translations and where help is needed. > > > >> > >> Let me know if I can help. > >> > >> > > > >After I catch up a little, I'll be on #phpslash irc.freenode.net > > > >thanks, > > > >Joe > > Hey Joe, I added that information to the "doc" for developers. You can get > a .sgml file from: > > http://cvs.sourceforge.net/viewcvs.py/*checkout*/phpslash/phpslash-dev/doc/html/psldeveloper.sgml > > Now, we should update the documentation in http://phpslash.sf.net. > The documentation is updated for the static files: http://phpslash.sourceforge.net/doc/phpslash.html http://phpslash.sourceforge.net/doc/psldeveloper.html Translation addition: http://phpslash.sourceforge.net/doc/psldeveloper-13.html#ss13.4 The documentation inside psl is not updated yet. Joe > Xavier, I'll send you an email with details later today. For the mean time > you should checkout a copy of the CVS repository for the phpslash-dev > module. From a terminal type: > > % cvs -d:pserver:ano...@cv...:/cvsroot/phpslash login > % [ENTER] > % cvs -z3 -d:pserver:ano...@cv...:/cvsroot/phpslash co > phpslash-dev > > > Or if you don't want to use a Terminal or are using a different OS (other > than Linux that is) use your favorite CVS client. :-) > > I'm working on a README that explains translations in detail. > > ----)(----- > Luis Mondesi > System Administrator > LatinoMixed.com > > le...@ho... > > No .doc: http://www.fsf.org/philosophy/no-word-attachments.es.html > |
From: Joe S. <joe...@us...> - 2004-01-16 14:36:49
|
On Thu, Jan 15, 2004 at 03:25:39PM -0500, Luis M wrote: > > Hey Joe, I added that information to the "doc" for developers. You can get > a .sgml file from: > > http://cvs.sourceforge.net/viewcvs.py/*checkout*/phpslash/phpslash-dev/doc/html/psldeveloper.sgml > > Now, we should update the documentation in http://phpslash.sf.net. > When I generate the docs on my machines, it builds, but has some formatting problems. Do the docs in the alpha snapshot look OK? If anyone can do a "make dist" from their cvs successfully, let me know. I'll try my script on sf.net too. Haven't run the snapshot script in awhile. Joe |
From: Luis M <le...@ho...> - 2004-01-15 20:25:45
|
>On Thu, Jan 15, 2004 at 03:31:14AM -0800, Xavier Paris Roig wrote: > > > > Hi guys, > > > > > > > > I would like to help in the development of phpSlash. I have > > > > some free time to dedicate on this project (translations, > > > > interface design, tester...) :) > > > > > >Hello, > >I'll get with you on things you can help with. > >Luis will send info on translations and where help is needed. > > > > > Let me know if I can help. > > > > > >After I catch up a little, I'll be on #phpslash irc.freenode.net > >thanks, > >Joe Hey Joe, I added that information to the "doc" for developers. You can get a .sgml file from: http://cvs.sourceforge.net/viewcvs.py/*checkout*/phpslash/phpslash-dev/doc/html/psldeveloper.sgml Now, we should update the documentation in http://phpslash.sf.net. Xavier, I'll send you an email with details later today. For the mean time you should checkout a copy of the CVS repository for the phpslash-dev module. From a terminal type: % cvs -d:pserver:ano...@cv...:/cvsroot/phpslash login % [ENTER] % cvs -z3 -d:pserver:ano...@cv...:/cvsroot/phpslash co phpslash-dev Or if you don't want to use a Terminal or are using a different OS (other than Linux that is) use your favorite CVS client. :-) I'm working on a README that explains translations in detail. ----)(----- Luis Mondesi System Administrator LatinoMixed.com le...@ho... No .doc: http://www.fsf.org/philosophy/no-word-attachments.es.html Public signature: http://www.latinomixed.com/lems1/public-a.asc _________________________________________________________________ MSN Search, le moteur de recherche qui pense comme vous ! http://search.msn.fr/worldwide.asp |
From: Mike G. <mi...@op...> - 2004-01-10 17:40:19
|
Hi Matthew, We ran into that problem with the text templates... Evan suggested a regex work around like: s/<!-- START .*?\.tpl -->// s/<!-- END .*?\.tpl -->// could be applied to the template.. Having a {START_TEMPLATE} {END_TEMPLATE} header to stick into the template files sounds fine.. Just need to find someone to integrate it and propose a patch.. Mike On Sat, 2004-01-10 at 02:02, Matthew Leingang wrote: > Hi guys, > > I hope it's not too late to chime in on this, but it seems like this > enhancement makes the unnecessary assumption that all templates are > HTML-like and use <!-- --> for comments. I have templates that write > JavaScript and you can imagine other text formats that can be templated. > > Why not have template::parse add some variables by default? You'd still > have to put them in the templates, but there'd be a standard way to access a > template's file name. > > You can extend PHPLIB's template to do what you want as well. > > --Matt > > On 12/30/03 9:49 AM, "Mike Gifford" <mi...@op...> wrote: > > > Hello, > > > > Presently Back-End.org is using template.inc as is and adding in > > template header/footer comments with each template just as phpSlash and > > (and most other phplib template driven apps likely do). > > > > In talking to the Back-end.org team though, it seems like the following > > modification to template.inc would make it easier for us to ensure that > > the file names are accurate and easily accessible. > > > > > > cvs diff phplib/php/template.inc > > Index: phplib/php/template.inc > > =================================================================== > > RCS file: > > /cvsroot/back-end/back-end0.7.x/class/phplib/php/template.inc,v > > retrieving revision 1.1.1.1 > > diff -r1.1.1.1 template.inc > > 909c909,911 > > < > > --- > >> > >> $str = "<!-- START $filename -->' . $str . '<!-- END $filename -->'; > >> > > > > > > If we implement this we'll have a lot of header/footer comments to delete and > > I'd just like to try to keep this in step with phpSlash if we can. > > > > > > I'd also like to contribute the following javascript which can just be > > inserted into a block to easily identify which templates are where. > > > > > > <script type="text/javascript"> > > <!-- > > // Code Contributed by Lasse Nielsen - http://www.infimum.dk > > function convert(node) { > > if (!node) {node = document.body;} > > > > switch (node.nodeType) { > > case Node.COMMENT_NODE: > > var text = node.nodeValue; > > if (text.substr(0,7)==" START ") { > > var newNode = createNewNode(text.substr(7)); > > node.parentNode.replaceChild(newNode,node); > > } > > break > > case Node.ELEMENT_NODE: > > for (var i=0;i<node.childNodes.length;i++) { > > convert(node.childNodes[i]); > > } > > break; > > default: > > break; > > } > > } > > > > function createNewNode(text) { > > var a = document.createElement("a"); > > a.href = > > "/admin/BE_editTemplateAdmin.php?submit=edit&file="+escape(text); > > var img = document.createElement("img"); > > img.src = "/images/BE/buttons/spacer.gif"; > > a.appendChild(img); > > return a; > > } > > --> > > </script> > > > > <input type="button" value="Convert!" onclick="convert()"> > > > > > > Mike -- Mike Gifford, OpenConcept Consulting Free Software for Social Change -> http://www.openconcept.ca Stop Cdn Pension Plan War Investments -> http://coat.openconcept.ca/ Another world is not only possible, she is on her way -Arundhati Roy |
From: Matthew L. <lei...@ma...> - 2004-01-10 07:02:39
|
Hi guys, I hope it's not too late to chime in on this, but it seems like this enhancement makes the unnecessary assumption that all templates are HTML-like and use <!-- --> for comments. I have templates that write JavaScript and you can imagine other text formats that can be templated. Why not have template::parse add some variables by default? You'd still have to put them in the templates, but there'd be a standard way to access a template's file name. You can extend PHPLIB's template to do what you want as well. --Matt On 12/30/03 9:49 AM, "Mike Gifford" <mi...@op...> wrote: > Hello, > > Presently Back-End.org is using template.inc as is and adding in > template header/footer comments with each template just as phpSlash and > (and most other phplib template driven apps likely do). > > In talking to the Back-end.org team though, it seems like the following > modification to template.inc would make it easier for us to ensure that > the file names are accurate and easily accessible. > > > cvs diff phplib/php/template.inc > Index: phplib/php/template.inc > =================================================================== > RCS file: > /cvsroot/back-end/back-end0.7.x/class/phplib/php/template.inc,v > retrieving revision 1.1.1.1 > diff -r1.1.1.1 template.inc > 909c909,911 > < > --- >> >> $str = "<!-- START $filename -->' . $str . '<!-- END $filename -->'; >> > > > If we implement this we'll have a lot of header/footer comments to delete and > I'd just like to try to keep this in step with phpSlash if we can. > > > I'd also like to contribute the following javascript which can just be > inserted into a block to easily identify which templates are where. > > > <script type="text/javascript"> > <!-- > // Code Contributed by Lasse Nielsen - http://www.infimum.dk > function convert(node) { > if (!node) {node = document.body;} > > switch (node.nodeType) { > case Node.COMMENT_NODE: > var text = node.nodeValue; > if (text.substr(0,7)==" START ") { > var newNode = createNewNode(text.substr(7)); > node.parentNode.replaceChild(newNode,node); > } > break > case Node.ELEMENT_NODE: > for (var i=0;i<node.childNodes.length;i++) { > convert(node.childNodes[i]); > } > break; > default: > break; > } > } > > function createNewNode(text) { > var a = document.createElement("a"); > a.href = > "/admin/BE_editTemplateAdmin.php?submit=edit&file="+escape(text); > var img = document.createElement("img"); > img.src = "/images/BE/buttons/spacer.gif"; > a.appendChild(img); > return a; > } > --> > </script> > > <input type="button" value="Convert!" onclick="convert()"> > > > Mike -- |
From: Matt \TrollBoy\ W. <tro...@sh...> - 2004-01-06 18:09:23
|
On Thu, 2003-11-27 at 01:14, Aric Caley wrote: > How did it wind up unregistered, anyway? People not watching it like they should be > If its a problem of having somebody pay for and maintain hosting I'd be > happy to provide a home for it... I paid for it last time, but alas someone came through and sniped it before I could register it... anyone for changing the project name? > ----- Original Message ----- > From: "Matt "TrollBoy" Wiseman" <tro...@sh...> > To: <php...@li...> > Sent: Wednesday, November 26, 2003 9:06 PM > Subject: [Phpslash-devel] PHPSLash.org > > > > The domain's up for grab's.. I'm gunna reg it before anyone else does.. > > what dns should I point it to? > > -- > > Matt "TrollBoy" Wiseman > > Webmaster: Shoggoth.net > > WebMonkey: Chaosium.com > > Site Designer: phpslash.org > > The oldest and strongest emotion of mankind is fear, > > and the oldest and strongest kind of fear is fear of the unknown. > > -H.P. Lovecraft > > --------------------------------------------------------- > > Please do not resell my e-mail address > > to anyone or send me unsolicited e-mail > > --------------------------------------------------------- > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: SF.net Giveback Program. > > Does SourceForge.net help you be more productive? Does it > > help you create better code? SHARE THE LOVE, and help us help > > YOU! Click Here: http://sourceforge.net/donate/ > > _______________________________________________ > > Phpslash-devel mailing list > > Php...@li... > > https://lists.sourceforge.net/lists/listinfo/phpslash-devel > > > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > Phpslash-devel mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpslash-devel > > -- Matt "TrollBoy" Wiseman Webmaster: Shoggoth.net WebMonkey: Chaosium.com Site Designer: phpslash.org The oldest and strongest emotion of mankind is fear, and the oldest and strongest kind of fear is fear of the unknown. -H.P. Lovecraft --------------------------------------------------------- Please do not resell my e-mail address to anyone or send me unsolicited e-mail --------------------------------------------------------- |
From: Luigi S <le...@ho...> - 2004-01-05 20:19:04
|
I'm cc'ing the phpslash-devel list... >From: "Raf Vantongerloo" <b3a...@ho...> >Subject: Re: phpSlash translators >Date: Sun, 3 Aug 2003 20:15:57 +0200 > >Hi again, > >I just noticed that the file you described (lang.php) is already translated >to dutch (nl.php). Unless there are other things to translate, I can't help >you. And in case there are other things, I'd like to know who the other >dutch-translator is, so we can work together maybe. > <snip> Hello, Well, that file might be outdated. Remeber that we are using the phpslash-dev module from CVS now. If you look at the en.php file and compare it with the current nl.php file, you might find some strings missing. You could just add those missing strings and I'll make sure it gets committed. I'm not sure who the translator for that file is, but, I'm sure they won't mind if you updated :-) For those who don't know, you can get the latest and greatest phpslash from: cvs -d:pserver:ano...@cv...:/cvsroot/phpslash login cvs -z3 -d:pserver:ano...@cv...:/cvsroot/phpslash co phpslash-dev Remember that we need lots of help debugging and with documentation/instalation etc... So if you can get a copy from the CVS repository and, say, install it in a non-production server for you to test that the installation process is smooth and that things work perfectly with your current setup. If they don't work as smooth, you can simply write back in this list and we will promptly fix whatever problems you might find. The latest phpslash installation i did is at http://v2divx.sf.net and after a number of tweaks it worked fine. However, that was from the point of view of somebody who has been using phpslash for a number of years, we would like to know more just how hard/easy it is for somebody who doesn't use phpslash as often, or at all, and use that experience to try to stream line the installation process. We have an "alpha" release just for those who might now have or care about CVS access and just want to play with phpslash before it gets officially release. Soon, I hope, Joe will release a new alpha version that will reflect the current CVS version :-) Also, there are other things at the SF project page that we need to get too, namely: Bugs and Requested Features After which I guess that we can start making Beta releases and worry about people doing upgrades from 0.7.2 to 0.8 :-) > > > > ============================== > > > > Translation files > > Files located in the "include/locale" directory are called by the >function > > pslgetText to translate strings contained in the code to the chosen > > language. > > > > Procedure for translating to new languages: > > . In the "locale" directory, copy the file en.php to LANG.php, where >LANG >is > > the desired language. > > . Change the values of the array to the new translated language. i.e. A >key > > value like, "This is English" => "This is English", will be changed to: > > "This is English" => "This is LANG". > > > > ============================== > > > > I think that's clear enough (and very simple to follow). If anybody has > > ideas on how to improve this (say more), please feel free to reply to >this > > post. > > <snip> ----)(----- Luis Mondesi System Administrator LatinoMixed.com le...@ho... No .doc: http://www.fsf.org/philosophy/no-word-attachments.es.html Public signature: http://www.latinomixed.com/lems1/public-a.asc _________________________________________________________________ MSN Messenger : discutez en direct avec vos amis ! http://www.msn.fr/msger/default.asp |