headers
Rob Siklos | 8 Oct 03:02
Picon

variable reference error in co.php

Hi,

I'm using the latest released Horde (3.0.5) and Chora (2.0) just downloaded 
today.  At various pages, I get the following at the top of the page:

 Notice: Only variable references should be returned by reference in 
/var/www/cvs/horde/lib/Horde/VC/cvs.php on line 62

Any idea what the problem could be?

Thanks,

Rob. 

--

-- 
Chora mailing list - Join the hunt: http://horde.org/bounties/#chora
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: chora-unsubscribe <at> lists.horde.org
Permalink | Reply | 1 comment |
headers
Jan Schneider | 8 Oct 16:56
Favicon
Gravatar

Re: variable reference error in co.php

Zitat von Rob Siklos <rob2 <at> siklos.ca>:

> Hi,
>
> I'm using the latest released Horde (3.0.5) and Chora (2.0) just downloaded
> today.  At various pages, I get the following at the top of the page:
>
> Notice: Only variable references should be returned by reference in
> /var/www/cvs/horde/lib/Horde/VC/cvs.php on line 62

Fixed in CVS already.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/

--

-- 
Chora mailing list - Join the hunt: http://horde.org/bounties/#chora
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: chora-unsubscribe <at> lists.horde.org
Permalink | Reply | 0 comments |
headers
Rob Siklos | 11 Oct 14:50
Picon

cvsps output

Hi All,

Is there any way to have cvsps output go to the horde log file instead of 
the Apache error log?

Also, on a side note, the "Patchsets" link doesn't work on cvs.horde.org 
(unable to spawn cvsps).  Not sure if this was intentional or not.

Thanks,

Rob. 

--

-- 
Chora mailing list - Join the hunt: http://horde.org/bounties/#chora
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: chora-unsubscribe <at> lists.horde.org
Permalink | Reply | 0 comments |
headers
Jan Schneider | 13 Oct 17:07
Favicon
Gravatar

Chora H3 (2.0.1) (final)

The Horde Team is pleased to announce the final release of the Chora
Repository Viewer version H3 (2.0.1).

Chora is built upon the Horde Application Framework and provides a read-only
browser interface to any number of version control repositories.  Advanced
features include a visual branch view of the repository's history,
pretty-printed output, annotation, patchsets and basic statistics.

Major changes compared to the Chora version H3 (2.0.1-RC1) are:
    * Updated Finnish and Slovak translations.

Major changes compared to the Chora version H3 (2.0) are:
    * Fixed mime type detection using the PHP fileinfo extension.
    * Added Russian translation.
    * Updated Brazilian Portuguese, Finnish, German, and Norwegian
      translations.

The full list of changes (from version H3 (2.0)) can be viewed here:

http://cvs.horde.org/diff.php/chora/docs/CHANGES?r1=1.100&r2=1.100.2.9&ty=h

The Chora H3 (2.0.1) distribution is available from the following locations:

    ftp://ftp.horde.org/pub/chora/chora-h3-2.0.1.tar.gz
    http://ftp.horde.org/pub/chora/chora-h3-2.0.1.tar.gz

Patches against version H3 (2.0) are available at:

    ftp://ftp.horde.org/pub/chora/patches/patch-chora-h3-2.0-h3-2.0.1.gz
    http://ftp.horde.org/pub/chora/patches/patch-chora-h3-2.0-h3-2.0.1.gz
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jan Schneider | 14 Oct 09:55
Favicon
Gravatar

Interesting

http://jodrell.net/projects/convulsion

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/

--

-- 
Chora mailing list - Join the hunt: http://horde.org/bounties/#chora
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: chora-unsubscribe <at> lists.horde.org
Permalink | Reply | 2 comments |
headers
Chuck Hagenbuch | 14 Oct 16:14
Favicon
Gravatar

Re: Interesting

Quoting Jan Schneider <jan <at> horde.org>:

> http://jodrell.net/projects/convulsion

Quite. It's done against Horde 2, unfortunately; it'd be much easier 
for them if they used the packaged VC library. It's almost tempting to 
contact them and see if they're interested in actively maintaining it 
against the framework packages, so we can list at least one other 
project using our libs as a development base. :)

-chuck

-- 
"But she goes not abroad in search of monsters to destroy." - John 
Quincy Adams
--

-- 
Chora mailing list - Join the hunt: http://horde.org/bounties/#chora
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: chora-unsubscribe <at> lists.horde.org
Permalink | Reply | 1 comment |
headers
Jan Schneider | 14 Oct 17:19
Favicon
Gravatar

Re: Interesting

Zitat von Chuck Hagenbuch <chuck <at> horde.org>:

> Quoting Jan Schneider <jan <at> horde.org>:
>
>> http://jodrell.net/projects/convulsion
>
> Quite. It's done against Horde 2, unfortunately; it'd be much easier
> for them if they used the packaged VC library. It's almost tempting to
> contact them and see if they're interested in actively maintaining it
> against the framework packages, so we can list at least one other
> project using our libs as a development base. :)

Heh, true.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/

--

-- 
Chora mailing list - Join the hunt: http://horde.org/bounties/#chora
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: chora-unsubscribe <at> lists.horde.org
Permalink | Reply | 0 comments |
headers
Admin | 24 Oct 19:10

Potentially Dangerous URL

Hi,
I was searching on how to get rid of the Potentially Dangerous URL  
warning, which is bothering my Horde users a lot and I've found this  
Jan's post:
 >This is nothing to worry about, as you know the source of that link  
and
 >can trust. It can't (and probably shouldn't) be disabled at the  
moment.
 >It's a security feature.

I think this reasoning is overlooking the [absolutely useless IMHO]  
scaring effect it has on a group of novice users and it's unseen in  
any other webmail program I've ever used. This extra click is just  
annoying and I strongly doubt anyone can assess a "Potentially  
Dangerous URL", not knowing what the danger might be and for what,  
except the Horde developers themselves; then if s/he has the "guts",  
s/he will click anyway, as s/he would have done without the warning.  
Otherwise, s/he will just stop using Horde and check his email thru a  
yahoo.com external POP account, where the absence of the warning will  
make him/her feel "safer".

Therefore I think is should be an user option, if not an admin  
option, to disable this so called "security feature", at admin's  
risk, if you want to say so.

brunus
--

-- 
Chora mailing list - Join the hunt: http://horde.org/bounties/#chora
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: chora-unsubscribe <at> lists.horde.org
(Continue reading)

Permalink | Reply | 1 comment |
headers
Jan Schneider | 25 Oct 09:29
Favicon
Gravatar

Re: Potentially Dangerous URL

Zitat von Admin <admin <at> ltarngozi.org>:

> Therefore I think is should be an user option, if not an admin
> option, to disable this so called "security feature", at admin's
> risk, if you want to say so.

No. Hack the code if you don't want to bother your users with extra 
security. *We* care about web application security.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/

--

-- 
Chora mailing list - Join the hunt: http://horde.org/bounties/#chora
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: chora-unsubscribe <at> lists.horde.org
Permalink | Reply | 0 comments |
headers
Admin | 25 Oct 23:34

Re: Potentially Dangerous URL


Jan,
would you be so kind to explain me how I could hack the code?

thanks,

brunus

> Date: Tue, 25 Oct 2005 09:29:01 +0200
> From: Jan Schneider <jan <at> horde.org>
> Subject: Re: [chora] Potentially Dangerous URL
> To: chora <at> lists.horde.org
> Message-ID: <20051025092901.jt99tcyf4w0gso0g <at> neo.wg.de>
> Content-Type: text/plain;    charset=ISO-8859-15;    format="flowed"
>
> Zitat von Admin <admin <at> ltarngozi.org>:
>
>
>
>> Therefore I think is should be an user option, if not an admin
>> option, to disable this so called "security feature", at admin's
>> risk, if you want to say so.
>>
>>
>
> No. Hack the code if you don't want to bother your users with extra
> security. *We* care about web application security.
>
> Jan.
>
(Continue reading)

Permalink | Reply | 1 comment |

Gmane