Michael thanks. That fixed it. I did read the documentation and thought I’d done the right thing.
However upon reflection I think it would be a good idea to force the administrator to put a limit. Zip files that are too big will choke a server and greedy users will take all they can if given a chance.
Better to let the admin make a considered decision on the basis of his own user’s feedback. If he wants a free for all then let him configure the site with the resources to handle it. On the other hand if he is charging for the content then he will have to balance client’s ease of use vs cost of providing the service.
I’ve set a limit of 10Mb and 100 files for now but I’m already looking at ways of making the service more user friendly eg a monthly archive as well as a daily one.
One final point is that you might leave the non-functioning download button as a “feature” but document it as such. That is by setting the limits to zero the admin can allow users to see all the available files but not download them. So he can create one profile for “look but can’t touch” users and another one for those with download rights.
You have a slick interface there and if I had a prospective user wanting to see what was available and how neat it is to download that would be a perfect demo.