headers
fago | 5 May 20:27
Favicon

chora svn revision log

hi!
I'm using chora 2.0.2 for viewing my svn repository. Unfortunately I
noticed that there are no revision log messages, if one views a file
history (like this: http://cvs.horde.org/horde/login.php )

I've only the revision number as well as the modification date listed -
but log messages are missing completely.

However if I view a  directory listing, I see at least the log message
of the last entry - so chora is able to get the messages.
So why arent' the shown at the "file history"? Is there anything I could
have configured wrong? Or is this a bug,  or just on the TODO list?

Note that I've tried it with a directly accessed repository (with
file://) as well with a local checkout - but the behavior was the same.

thanks,
fago

--

-- 
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
Chuck Hagenbuch | 7 May 17:21
Favicon
Gravatar

Re: chora svn revision log

Quoting fago <nuppla <at> zites.net>:

> I'm using chora 2.0.2 for viewing my svn repository. Unfortunately I
> noticed that there are no revision log messages, if one views a file
> history (like this: http://cvs.horde.org/horde/login.php )
>
> I've only the revision number as well as the modification date listed -
> but log messages are missing completely.
>
> However if I view a  directory listing, I see at least the log message
> of the last entry - so chora is able to get the messages.
> So why arent' the shown at the "file history"? Is there anything I could
> have configured wrong? Or is this a bug,  or just on the TODO list?

What Horde version are you using? It's possible that there's a Chora  
or VC library bug that causes this that's since been fixed (I just  
double checked and it works on my svn repository with HEAD, so it's  
not a TODO or an existing bug).

> Note that I've tried it with a directly accessed repository (with
> file://) as well with a local checkout - but the behavior was the same.

In general checkouts aren't going to work, but using file:/// (three  
slashes) should. Unfortunately the best I can tell you with what we  
have above is to trace the code a bit and see where the info is being  
lost; possibly try a snapshot to see if that fixes it; and make sure  
you're checked your Horde logfile.

-chuck
--

--
(Continue reading)

Permalink | Reply | 0 comments |
headers
Chuck Hagenbuch | 7 May 21:09
Favicon
Gravatar

Fwd: Re: chora svn revision log

Please keep conversations on the list.

----- Forwarded message from nuppla <at> zites.net -----
     Date: Mon, 07 May 2007 21:06:31 +0200
     From: fago <nuppla <at> zites.net>
  Subject: Re: [chora] chora svn revision log
       To: Chuck Hagenbuch <chuck <at> horde.org>

hi!

> What Horde version are you using?
The 3.1.4 release.

> It's possible that there's a Chora
> or VC library bug that causes this that's since been fixed (I just
> double checked and it works on my svn repository with HEAD, so it's
> not a TODO or an existing bug).
>
> > Note that I've tried it with a directly accessed repository (with
> > file://) as well with a local checkout - but the behavior was the same.
>
> In general checkouts aren't going to work, but using file:/// (three
> slashes) should.
That's bad, as I'd have preferred using a checkout.

> Unfortunately the best I can tell you with what we
> have above is to trace the code a bit and see where the info is being
> lost; possibly try a snapshot to see if that fixes it; and make sure
> you're checked your Horde logfile.
The logfile says nothing about that.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Chuck Hagenbuch | 9 May 20:13
Favicon
Gravatar

Fwd: Re: chora svn revision log

Please keep discussions on the list

----- Forwarded message from nuppla <at> zites.net -----
     Date: Mon, 07 May 2007 21:06:31 +0200
     From: fago <nuppla <at> zites.net>
  Subject: Re: [chora] chora svn revision log
       To: Chuck Hagenbuch <chuck <at> horde.org>

hi!

> What Horde version are you using?
The 3.1.4 release.

> It's possible that there's a Chora
> or VC library bug that causes this that's since been fixed (I just
> double checked and it works on my svn repository with HEAD, so it's
> not a TODO or an existing bug).
>
> > Note that I've tried it with a directly accessed repository (with
> > file://) as well with a local checkout - but the behavior was the same.
>
> In general checkouts aren't going to work, but using file:/// (three
> slashes) should.
That's bad, as I'd have preferred using a checkout.

> Unfortunately the best I can tell you with what we
> have above is to trace the code a bit and see where the info is being
> lost; possibly try a snapshot to see if that fixes it; and make sure
> you're checked your Horde logfile.
The logfile says nothing about that.
(Continue reading)

Permalink | Reply | 501 comments |
headers
Chuck Hagenbuch | 9 May 20:15
Favicon
Gravatar

Re: Fwd: Re: chora svn revision log

Quoting uppla <at> zites.net

> I've installed chora-FRAMEWORK_3-2007-05-07 now - but no change.
> So I tried to identify where the message is lost and found out that it
> happens on line 215 of browse.php:
>
>          $logMessage = Chora::formatLogMessage($lg->log);
>
> If I change it to $logMessage = $lg->log; I get the messages...

You're probably missing Text/Filter or something from your Horde  
framework install. You'll see an error message if you turn on error  
logging in PHP, or turn display_errors on and set error_reporting to  
an appropriate level.

-chuck
--

-- 
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 | 501 comments |
headers
fago | 10 May 15:54
Favicon

Re: Fwd: Re: chora svn revision log

Am Mittwoch, den 09.05.2007, 14:15 -0400 schrieb Chuck Hagenbuch:
> Quoting uppla <at> zites.net
> 
> > I've installed chora-FRAMEWORK_3-2007-05-07 now - but no change.
> > So I tried to identify where the message is lost and found out that it
> > happens on line 215 of browse.php:
> >
> >          $logMessage = Chora::formatLogMessage($lg->log);
> >
> > If I change it to $logMessage = $lg->log; I get the messages...
> 
> You're probably missing Text/Filter or something from your Horde  
> framework install. You'll see an error message if you turn on error  
> logging in PHP, or turn display_errors on and set error_reporting to  
> an appropriate level.

hm, I have php display_errors on (and at a appropraite level) but I
don't get any errors. The horde log file also contains nothing about
chora, I have just some imp notices there.

thanks,
fago

--

-- 
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 |

Gmane