Newbie - Installing on Zeus Server

Dowloaded the latest and unpacked/uploaded to my ISPs server.
Tried to run setup - lots of 500 errors.
After loads of messing around I found if I renamed all of the .htaccess files as 1.htaccess then there was no problem.

I know that the ZEUS server they use does not have a full implementation of .htaccess.

Can anyone offer advice?

In the mean time - I am having a play - seems a great product. Complex, and daunting to a newbie - and I dont even know if I can get Zen to do what I want yet
:(

Your problem is going to be the ZEUS server. In addition to the .htaccess problem you can forget about Mod Rewrite (URL rewriting) because ZEUS is not an Apache server and does not support Mod Rewrite.

Vger

Am I being dense? I thought Mod Rewrite was part of the implementation of .htaccess.:dontgetit
Since I have effectively 'turned off' .htaccess by renaming the files how will the lack of Mod Rewrite affect the functionality of Zen?

Of course there are still security issues that have been turned off by disabling the Match functions - which I understand Zeus supports although the code structure in the .htaccess file may need changing - and I've no experience in doing that.:dontgetit

Beggars cant be choosers. We are a registered charity and our ISP provides a free service - so I cant look for another ISP unless another, reputable, service provider can offer, at least, to host the shop and shop database, then I could leave the main site and email where it is.

Zen Cart doesn't require mod_rewrite. But many so-called SEO experts insist that it's important to rewrite URLs to shorter wordier strings. What Vger is telling you is that if you ever wanted to do any mod_rewrite, you'd be unable to do that if you're going to use Zeus as your webserver, since Zeus is incapable of mod_rewrite.

As for all your 500 errors, those are also a result of Zeus's incomplete .htaccess implementation. You're right: renaming the files will allow the PHP scripts to run, but will give you ZERO protection, and you'll have to write your own new security rules to work with your server.

With respect, if I may be so forward, even a registered charity finds ways to come up with the funds required for administrative expenses. Hosting a website is only a few pounds a month, and is money well-spent on finding a solid hosting company offering conventional and secure hosting services.

Thanks for the confirmation on .htaccess - just as I expected.

With an income only during Apr - Sept and in Dec
and frequently less than £1000/month income
and after taking out running costs -a railway is expensive to run and maintain
There's little left at the end of the month - every little bit of sponsorship helps

OK - so ignoring issues with mod-rewrite.

I am going to go through all the .htaccess files and check then for ZWS

I have started with the one in the /includes folder.

Very simple and straight forward - shouldnt need any changes - but I am puzzled:blink:
It contains a FileMatch string

".*\.(js|JS|css|CSS|jpg|JPG|gif|GIF|png|PNG|swf|SWF|xsl|XSL)$"

Why is "php|PHP" not in the string -
or am I just having a senior moment?

I have checked with the original in the downloaded zip and I havent messed it up!!

Ah - I think I figured it out.
In normal use php files in this folder aren't 'served' they are accessed by local file access with the 'inclde' command.
So they will be accessible even if not in the FileMatch

The FileMatch doesnt have them so they wont be 'served' to someone poking around:D

Exactly. It first prevents "everything", and then selectively "allows" only acceptable files. This significantly prevents abuse.

Thanks for the confirmation.....
So why when I put that in the /includes folder does the shop NOT display uploaded .gif files - on ZWS as far as I can see the FilesMatch should be idnetical to an Apche statement

That's a good question to ask the Zeus support people, since it's an issue directly related to the workings of their software.

Yes - it was kind of hypothetical - I had already posted on their support forum - no replies

In the distribution, in the /images/uploads folder is an .htaccess file that contains code to deny access to all files
It does not contain corresponding code to permit specific files a the .htaccess files elsewhere do.

Why is this?
Have I missed some instruction somewhere that tells me I need to configure this?

I have discovered that Apache and Zeus use the
Order Allow,Deny directive differently.
By changing it to 'Order Deny,Allow'
things have started working.

That's a good question to ask the Zeus support people, since it's an issue directly related to the workings of their software.

Basically, on a Zeus server, you either need to:

1. Forget about using .htaccess
2. Find out how to use the partial and atypical application of.htaccess that exists for use on Zeus servers.

Vger

2. Find out how to use the partial and atypical application of.htaccess that exists for use on Zeus servers.
   I believe I have done this - by modifying the

Order Deny,Access

Things seem to be working - although as yet I havent checked every possible web page, I have check most folder to ensure non-servable files remain '403'.
The question remains - what is the point of the deny all on the /images/uploads without a qualifying 'permit some'.

There remains one item in the admin area relating to SSL that is in the .htaccess, and I cant see a wayaround that.

On the SEO mod_rewrite there are a number of scripts on the web that can be found under 'Joomla' and 'Zeus' - but I arent interested in this as I wont be using the mod_rewrite SEO stuff.

tsrplatelayer:

In the distribution, in the /images/uploads folder is an .htaccess file that contains code to deny access to all files
It does not contain corresponding code to permit specific files a the .htaccess files elsewhere do.

Why is this?That's because you should not be using a browser to access those files.
You are to use FTP to download them for use with fulfilling orders.
If you use a browser, you leave yourself open to immediately putting yourself at risk of damaging your site if a rogue customer uploaded a damaging file.
tsrplatelayer:

Have I missed some instruction somewhere that tells me I need to configure this?No.

Thankyou for the explanation. I had anticipated that documents for download would be put in the 'downloads' folder.

I used 'uploads' to upload product images into - where should I be putting them? Perhaps in folders like those in the next paragraph - in which case how are new product folders created from within 'admin'?

There are a number of folders which dont seem relevant in the 'images' folder. I selected not to install the demo database - however there are folders lik Microsoft, Matox, Samples, Sierra, hewlett_packard, dvd, 3ds, gt-interactive - can these be deleted?
What are the images in 'small; and 'medium' for?

I will not be selling music or Dvds - what else can be 'tidied up'?

The /images/ folder is where you store your product images.
The medium/large folders are for additional-sized images. See this FAQ article: https://www.zen-cart.com/tutorials/index.php?article=58
The folders for demo product images can be deleted by hand.

You can't create new folders via the admin, but you can create them via FTP so that they're selectable from within the admin when uploading images for products.

But now you're straying away from the topic of Zeus-specific issues. :wink:

Once again thanks for the clear explanations- and the gentle reminder to stay on topic - new topic created