So I am trying to insert the the <?php if (function_exists('printAlbumZip')) { printAlbumZip(); } ?> which is in place and works of sorts.... you can see the test link here.... http://boatsandho.es/index.php?album=test3/

It is the first download link as the second is a test of albumzip stream. when I click ont he download album I get this :

http://boatsandho.es/http%3A//boatsandho.es/index.php?album=test3/&download=test3&albumzip

which of course 404s

if I clean the url and remove /http%3A//boatsandho.es out of the center making the url http://boatsandho.es/index.php?album=test3/&download=test3&albumzip it works fine and downloads the album correctly.

Is there a reason that is is creating that additional text in the url and how can I correct that.... any help is greatly appreciated.

The function `printAlbumZip()` is deprecated. Try the function `printDownloadLinkAlbumZip()` instead.

Which is a function of the downloadlist plugin that needs to be enabled naturally.

Thank you, it seemed to be an issue that i needed to resetup zp after making changes to my server configuration. I appreciate the prompt response.

I have the same problem as described in the 1st post with ZP v1.4.3.5. I've enabled the downloadList plugin. In my album.php file I have:

`<?php printDownloadLinkAlbumZip(); ?>`

The link appears on the page correctly, but the href is incorrect:

`http://myserver/zenphoto/http%3A//myserver/zenphoto/index.php?album=album1/&download=album1&albumzip`

It would be great to find out what themisters changed in the config to make this work.

Try re-running setup or set the WEBPAT define in /zp-date/zenphoto.cfg manually.

I tried both of those. Unfortunately, no change. Setup doesn't give any indication of errors. Only some warnings about my file permissions being more lax than what is recommended.

In zenphoto.cfg, I set

`define('WEBPATH', '/zenphoto');`
`define('SERVERPATH', '/var/www/zenphoto');`

and restarted Apache, but no change.

It was a bug and is fixed in tonight's nightly (or the soon sadly required following of 1.4.3.6...)

Yes, it's now fixed in the 12/5 build. Thanks very much.