accurate buy buyer buyers contact create deal download error file files help later link offer open option over plan product products purchase regarding reporting respond sale seller selling separate server setting single site size try upload url usually website www

If I have ten separate mp3 for sale on my site and I want to give the buyer the option to buy all songs as an album, is that considered an 11th product?

Yes, it is considered as a additional product.

Hello, how would you do this for a collection of mp3s that are to be sold as a collection only, but they would go over the file size limit if zipped? I'm trying to find a way to "compile" collections of 8 to 20+ files for a single sale able download purchase.

When I tried to offer a zip of one of these collections on my site's ftp, the sale goes through, but the download link says: "This file is served directly by the seller. At this moment seller's server has failed to respond. Please try again later. You can contact the seller at ----@-------.com"

What's the deal with that? I'm sure it's just a minor setting, or somthing like that, but I'm not sure what to do. Please help.

Thanks

To create "collections" of tracks that you are also selling individually, you would use our "Package files from other products" setting for each compilation/collection product, as explained in Approach 2 here:
http://www.e-junkie.com/ej/help.package.htm

Any files you are serving from your own server do not count against your storage allocation on E-junkie's server; e.g., if your plan includes 500MB of storage, that only counts the total size of all files you actually upload to our server, not any files we're delivering to buyers from your site.

Regarding the download error you are reporting, make sure you are using http://... URLs for your Remote Product File URL (we cannot work with ftp://... URLs), and make sure the file's path is accurate in your URL. When you upload files to your server by FTP, there's usually a specific folder that you have to open, where all of your website and other Web-accessible files need to go; that folder's name should not be explicitly included in your remote file URL, since any file being accessed on your site via HTTP is implicitly presumed to be in that folder. E.g., if "www" is the name of your "website folder" in FTP, then if you are uploading your product files by FTP to this folder path:

/www/productfiles/filename.zip

...then this would be your Remote Product File URL:

http://www.yoursite.com/productfiles/filename.zip