Re: [viewvc-dev] Porting templates to viewvc 1.1

Jens Peters wrote:
> Hi Mike,
> 
> I'm currently busy with porting my viewsvn template to viewvc 1.1. I 
> have several small questions.
> 
> - How should I start committing? Should I just commit the files as is, 
> or do you prefer a copy from the original templates or my 1.0 templates 
> first? (I guess committing based on a copy of my old templates..)

I don't have a preference for how you initialize the new template set, but I 
do think it best that you do your work under templates-contrib/1.1 instead 
of just tweaking the templates-contrib/1.0 bits.

> - Missing download_href. I would like to have the download_href symbol 
> when being in file.ezt. I don't get an error, but download_href holds 
> just the current url. head_download_href isn't working (I suppose that's 
> for the log view only). Could you check that?

Do you have the "co" view enabled in viewvc.conf (allowed_views)?  If not, 
then it may be that what you are seeing isn't that download_href contains 
the current URL, but that it is empty and your browser is treating that as 
"current URL".

> And at last a simple question for an inspiration. The tarball generation 
> isn't working in apache/mod_python. This problem isn't related to viewvc 
> I guess, because generating tarballs works just perfectly when using the 
> standalone server. Somehow the compressed file I got from the response 
> is marginal different, has nearly the supposed size and thus broken. Do 
> you have an idea what could cause this and where I could start looking?

Do you have 'allow_compress' set in viewvc.conf?  If so, I wonder if there's 
a misinteraction between the request-level compression and the tarball 
compression.

-- 
C. Michael Pilato <[email protected]>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIe1erokEGqRcG/W4RAgSsAJ44HhNYlkwT9F20BQun76gKSKybqACgyyk5
V3fQEvFwSY+9/zjEyHxCq34=
=em1w
-----END PGP SIGNATURE-----