Zen Cart® is made available to you for your use, addition, changes, modification, etc. without charge, under Version 2 of the GNU General Public License.
While we do not charge for this software, donations are greatly appreciated, each time you install a new version, to help cover the expenses of maintenance, upgrades, updates, the free support forum and the continued development of this software for your online E-Commerce store.
Donations can be made on the Zen Cart® Team Page
We appreciate your support.
The Zen Cart® Team
Zen Cart® v1.5.0 requires a minimum of the following:
While Zen Cart® can run on Windows/IIS servers, Linux/Apache servers are recommended for best results, superior performance, and easier use by shopowners.
For a list of files that have been changed since v1.3.9h, see the changed_files-v1-5-0.html
Please follow the instructions in the "how to upgrade" documentation in the /docs folder of the Zen Cart® files.
If you are attempting to upgrade custom code or addons written for prior versions, you may find this tutorial article helpful: upgrading_old plugins to_1.5
Please see this online article for guidance on upgrading old sites from iso-8859-1 to utf8
For added security, Zen Cart® comes with several .htaccess files already included in various folders to help provide protection against unwanted visitors and even against misuse of your site in the unfortunate situation of your site being hacked. These protections prevent hackers from using your site as phishing sources.
However, for these built-in protections to work, your web hosting server administrator MUST set the AllowOverride directive in the server's apache configuration (the server's master httpd.conf file) to "All" or at least ensure it includes these parameters: 'Limit Indexes'.
ie: AllowOverride All
or: AllowOverride Limit Indexes
Without these settings, you will likely encounter "500 Internal Server Error" messages when attempting to access various parts of your site, including perhaps the zc_install installer script.
Storeowners hosting on Windows Servers using IIS instead of Apache may need to remove the .htaccess files and rework them into suitable equivalents within your IIS configuration. See Microsoft's IIS website for specific assistance.
Inside some folders is an .htaccess file that lists certain *permitted* filetypes which may be accessed. (Anything else is blocked to prevent abuse on your site).
The side effect of this is that if you choose to use media types that are not already listed in the *permitted* list, then your visitors will not be able to see those resources.
Thus, if you are using product images that are not in the list of permitted types in your /images/.htaccess, you will need to add those types to the list.
Similarly, if you are using certain media types in music product previews, you will need to make sure those are in your /media/.htaccess.
And, if you are using filetypes for downloadable products that are not already listed in your /pub/.htaccess and /download/.htaccess you will need to add those as well.