Re: RFC with pepr
| From: | Vincent Gevers | Date: | Mon, 16 Aug 2004 14:21:55 +0000 |
| Subject: | Re: RFC with pepr | ||
| References: | 1 2 3 | Groups: | php.doc.web |
| Request: | Send a blank email to doc-web+get-181@lists.php.net to get a copy of this message | ||
On Sunday 15 August 2004 00:14, Gabor Hojtsy wrote:
> >>Yes, currently It's a bit ugly...
> >>Oh, the /user/xxx doesn't work. Maybe you are missing some .htaccess file
> >
> > I've added some css, I'm not an expert in that, but it looks a bit
> >nicer :)
> > but it can always be changed when the code is in cvs, if we agree to use
> > it
>
> Please make it, so that it will be easy to update our pepr copy. We
> should not start a new copy of pepr IMHO. Ways need to be found to plug
> into parts of pepr, and if need be, we can always file patches against
> pepr so it better support the kind of reuse we are up to.
I'll see what I can do, but somethings just can't be the same, like some
queries.. UNIX_TIMESTAMP() is not supported in SQLite
I've marked changes and parts that need to be reviewed with "// !!!"
most is related to the karma system and user info
also, pearweb uses a cookie called 'PEAR_USER' it's in most of the files, but
that is easy to replace :)
I'm going to upload the files into CVS this week, school starts again next
week, and this should not be lost.
should I create a new www/rfc dir or use the old www/RFC dir and overwrite the
old files? ATM the system is used with /rfc/
http://docweb.allowee.no-ip.com/rfc/ for the
current version
you can try everything, I will get all the emails :)
>
> Goba
>
- Vincent