Mike_Dean:

Hi,

Hoping someone can help as I'm into the 4th hour and no joy on this mod.

I'm working on a new site with a clean install of 1.5.4 on my local server (wamp)

I have installed the mod several times and it all check out fine using the installation check page

I have generated URI mapping on a particular category page and individual product, but I'm getting 404 and 500 errors depending on the following.

If I DON'T add the .htaccess file, I can get to the store front, but I get 404 errors on any of the product category pages.
If I DO install the .htaccess file in either the wamp/www/ folder of the wamp/www/zencart folder I get 500 error when I try an load the sites main page.

This is what the .htaccess file currently looks like

BEGIN CEON URI MAPPING REWRITE RULE

RewriteEngine On

ONLY rewrite URIs beginning with /zencart/

RewriteCond %{REQUEST_URI} ^/zencart/ [NC]

Don't rewrite any URIs ending with a file extension (ending with .[xxxxx])

RewriteCond %{REQUEST_URI} !.[a-z]{2,5}$ [NC]

Don't rewrite any URIs for some, popular specific file format extensions,

which are not covered by main file extension condition above

RewriteCond %{REQUEST_URI} !.(mp3|mp4|h264)$ [NC]

Don't rewrite any URIs for some specific file format extensions,

which are not covered by main file extension condition above

Uncomment the following line to apply this condition! (Remove the # at the start of the next line)

#RewriteCond %{REQUEST_URI} !.(3gp|3g2|h261|h263|mj2|mjp2|mp4v|mpg4|m1v|m2v|m4u|f4v|m4v|3dml)$ [NC]

Don't rewrite admin directory

RewriteCond %{REQUEST_URI} !^/zencart/admindemo [NC]

Don't rewrite editors directory

RewriteCond %{REQUEST_URI} !^/zencart/editors/ [NC]

Don't rewrite logs directory

RewriteCond %{REQUEST_URI} !^/zencart/logs/ [NC]

Don't rewrite zencart directory

RewriteCond %{REQUEST_URI} !^/zencart/ [NC]

Handle all other URIs using Zen Cart (its index.php)

RewriteRule .* index.php [QSA,L]

RewriteRule .* /zencart/index.php [QSA,L]

END CEON URI MAPPING REWRITE RULE

I have modified the last line of the file to

/index.php
index.php
/zencart/index.php
zencart/index.php.

All to no avail.

The worst part is I have an older version of it working nicely on my old 1.3.9 site !!

Any suggestions as to what I may have done wrong would be greatly appreciated

Many thanks,
Mike

Well, honestly, very little if anything has changed for the .htaccess file requirements through the ZC versions, if anything it is the server or other system changes that may necessitate a change. Therefore, basically if the .htaccess works fine for your 1.3.9 version of ZC, the same basic .htaccess could/should work for ZC 1.5.4... There may be some other factors about your local setup that are causing the issue, also if the .htaccess is placed in wamp/www does your wamp/www/zencart folder also have a .htaccess? (If wamp/www/zencart is your site's root folder for the zencart program, the answer should be that there is no .htaccess in the zencart subdirectory because zencart does not require one for normal operation.) If there is a .htaccess file in the wamp/www/zencart folder, what are its contents? Why is it there? And if so, you may need to incorporate the .htaccess content above into it, but move down a directory (instead of /zencart/ may just be / but also have to use a command at the beginning to indicate the current directory...

I did have to in one case have a .htaccess file in both the sites root as well as the store's root both providing the same general rewrite rule in each directory but a difference in that the subfolder didn't have reference to the subfolder, but as if at the site itself... Removal of the CEON .htaccess code from either caused trouble because the sub-directory had a .htaccess file for other reasons...

But it still could also be setup of the server as well at least without further information.

500 = Internal Server Error = Check Apache Logs.

Guessing some part of WAMP is misconfigured (for example not enabling mod_rewrite). But the Apache error log should help us better determine the cause.

I have a client where her 1.3.9h files are in the root public folder but am upgrading her to 1.5.4 and having the same issue. I had to turn off Ceon in order to access the test store site for if the mod is active I get the same error. It being a test store doesn't bother me cause I still have to finish edits then transfer to the clone of her store. But if this continues after the live store is with the files, we shall have a problem...lol

lhungil:

500 = Internal Server Error = Check Apache Logs.

Guessing some part of WAMP is misconfigured (for example not enabling mod_rewrite). But the Apache error log should help us better determine the cause.

Ahhh Its the simple things in life that cause the most stress !
Didn't think to check the Apache settings. Yes, the mod-rewrite was not enabled, so a quick change, restart the wamp server and re-set all the product categories and all good.

:smile::smile::smile:

Thanks all....

good for you to gets yours going, but hers is active or the mod would not work in the active store so no idea why it is not behaving in the test store that is in a directory of its own

DarkAngel:

good for you to gets yours going, but hers is active or the mod would not work in the active store so no idea why it is not behaving in the test store that is in a directory of its own
If you have the exact same symptoms (an HTTP 500 / internal server error)... Then you will need to check the server error logs (may need to contact your hosting provider as not all provide direct access to the Apache server error logs).

If you have a different symptom (it sounds like you do), please elaborate. Is the phpinfo() output exactly the same for both the live and demo store? What are the physical paths for the live store and demo store? Is the .htaccess file in a "parent" folder shared by both stores or is one store "nested inside" the other? If so have you altered the .htaccess file(s) accordingly?

lhungil:

If you have the exact same symptoms (an HTTP 500 / internal server error)... Then you will need to check the server error logs (may need to contact your hosting provider as not all provide direct access to the Apache server error logs).

She has a shared server but the host is fairly easy with the php stuff or with fixing things on their end

If you have a different symptom (it sounds like you do), please elaborate. Is the phpinfo() output exactly the same for both the live and demo store?

Yes I believe so

What are the physical paths for the live store and demo store? Is the .htaccess file in a "parent" folder shared by both stores or is one store "nested inside" the other? If so have you altered the .htaccess file(s) accordingly?

paths are different since the live store is directly in the public folder/store files
the test store is public folder/teststore/store files

1. I tried adding the ceon code it wants in the .htaccess file to the main one in the root AND still admin is accessible but clicking the link within there to go to the front end of the store it goes to page not found of live store

2. removed the code and created its own .htaccess code and still the same thing.

3. turned off ceon in test and now can access the store font with no issues.

Can you post "/public/.htaccess", "/public/store/.htaccess", "/public/teststore/.htaccess", and "/public/teststore/store/.htaccess"?

Please obscure the admin path (change to "!^/store/admin", "!^/teststore/store/admin", etc).

I'd also ask if you could kindly place the file contents inside "code tags" (ex: ```
[CODE]file contents[/CODE]

lhungil:

Can you post "/public/.htaccess", "/public/store/.htaccess", "/public/teststore/.htaccess", and "/public/teststore/store/.htaccess"?

Please obscure the admin path (change to "!^/store/admin", "!^/teststore/store/admin", etc).

I'd also ask if you could kindly place the file contents inside "code tags" (ex: ```
[CODE]file contents[/CODE]

1. public/.htaccess is the live store .htaccess file since all files live within the public folder so this is live store file

2. as for the test .htaccess file has long since gotten deleted but it was exactly like the one first posted below with the information of second

RewriteEngine On

Redirect all users to access the site WITH the 'www.' prefix

RewriteCond %{HTTP_HOST} !^www. [NC]
RewriteCond %{HTTP_HOST} !.([a-z-]+.[a-z]{2,6})$ [NC]
RewriteRule ^ http://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

BEGIN CEON URI MAPPING REWRITE RULE

Don't rewrite any URIs ending with a file extension (ending with .[xxxxx])

RewriteCond %{REQUEST_URI} !.[a-z]{2,5}$ [NC]

Don't rewrite any URIs for some, popular specific file format extensions,

which are not covered by main file extension condition above

RewriteCond %{REQUEST_URI} !.(mp3|mp4|h264)$ [NC]

Don't rewrite any URIs for some specific file format extensions,

which are not covered by main file extension condition above

Uncomment the following line to apply this condition! (Remove the # at the start of the next line)

#RewriteCond %{REQUEST_URI} !.(3gp|3g2|h261|h263|mj2|mjp2|mp4v|mpg4|m1v|m2v|m4u|f4v|m4v|3dml)$ [NC]

Don't rewrite admin directory

RewriteCond %{REQUEST_URI} !^/admin [NC]

Don't rewrite editors directory

RewriteCond %{REQUEST_URI} !^/editors/ [NC]

Don't rewrite darkangel directory

RewriteCond %{REQUEST_URI} !^/private/ [NC]

Don't rewrite cgi-bin directory

RewriteCond %{REQUEST_URI} !^/cgi-bin/ [NC]

Handle all other URIs using Zen Cart (its index.php)

RewriteRule .* /index.php [QSA,L]

END CEON URI MAPPING REWRITE RULE

EXPIRES CACHING

ExpiresActive On

ExpiresByType image/jpg "access plus 1 year"

ExpiresByType image/jpeg "access plus 1 year"

ExpiresByType image/gif "access plus 1 year"

ExpiresByType image/png "access plus 1 year"

ExpiresByType text/css "access plus 1 month"

ExpiresByType application/pdf "access plus 1 month"

ExpiresByType text/x-javascript "access plus 1 month"

ExpiresByType application/x-shockwave-flash "access plus 1 month"

ExpiresByType image/x-icon "access plus 1 year"

ExpiresDefault "access plus 2 days"

EXPIRES CACHING

deny from 144.76.95.231

Use PHP53 as default

AddHandler application/x-httpd-php53 .php
<IfModule mod_suphp.c>
suPHP_ConfigPath /opt/php53/lib
</IfModule>

2nd code

BEGIN CEON URI MAPPING REWRITE RULE

RewriteEngine On

ONLY rewrite URIs beginning with /test/

RewriteCond %{REQUEST_URI} ^/test/ [NC]

Don't rewrite any URIs ending with a file extension (ending with .[xxxxx])

RewriteCond %{REQUEST_URI} !.[a-z]{2,5}$ [NC]

Don't rewrite any URIs for some, popular specific file format extensions,

which are not covered by main file extension condition above

RewriteCond %{REQUEST_URI} !.(mp3|mp4|h264)$ [NC]

Don't rewrite any URIs for some specific file format extensions,

which are not covered by main file extension condition above

Uncomment the following line to apply this condition! (Remove the # at the start of the next line)

#RewriteCond %{REQUEST_URI} !.(3gp|3g2|h261|h263|mj2|mjp2|mp4v|mpg4|m1v|m2v|m4u|f4v|m4v|3dml)$ [NC]

Don't rewrite admin directory

RewriteCond %{REQUEST_URI} !^/test/admin [NC]

Don't rewrite editors directory

RewriteCond %{REQUEST_URI} !^/test/editors/ [NC]

Don't rewrite !!storage directory

RewriteCond %{REQUEST_URI} !^/test/logs/ [NC]

Handle all other URIs using Zen Cart (its index.php)

RewriteRule .* storetest/index.php [QSA,L]

END CEON URI MAPPING REWRITE RULE

Something similiar to the following should work:

## BEGIN host specific settings

# Use PHP53 as default
AddHandler application/x-httpd-php53 .php
<IfModule mod_suphp.c>
    suPHP_ConfigPath /opt/php53/lib
</IfModule>

## END host specific settings

## START Access control

# Block access from these IP Addresses
deny from 144.76.95.231

## END Access control

## BEGIN the usual suspects

# Enable mod_rewrite
RewriteEngine On

# Redirect all users to access the site WITH the 'www.' prefix
RewriteCond %{HTTP_HOST} !^www\. [NC]
RewriteCond %{HTTP_HOST} !\.([a-z-]+\.[a-z]{2,6})$ [NC]
RewriteRule ^ http://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

## END the usual suspects

## BEGIN CEON URI MAPPING REWRITE RULE (folder "test")

# ONLY rewrite URIs beginning with /test/
RewriteCond %{REQUEST_URI} ^/test/ [NC]
# Don't rewrite any URIs ending with a file extension (ending with .[xxxxx])
RewriteCond %{REQUEST_URI} !\.[a-z]{2,5}$ [NC]
# Don't rewrite any URIs for some, popular specific file format extensions,
#   which are not covered by main file extension condition above
RewriteCond %{REQUEST_URI} !\.(mp3|mp4|h264)$ [NC]
# Don't rewrite any URIs for some specific file format extensions,
#   which are not covered by main file extension condition above
#   Uncomment the following line to apply this condition! (Remove the # at the start of the next line)
#RewriteCond %{REQUEST_URI} !\.(3gp|3g2|h261|h263|mj2|mjp2|mp4v|mpg4|m1v|m2v|m4u|f4v|m4v|3dml)$ [NC]
# Don't rewrite admin directory
RewriteCond %{REQUEST_URI} !^/test/admin [NC]
# Don't rewrite editors directory
RewriteCond %{REQUEST_URI} !^/test/editors/ [NC]
# Don't rewrite !!storage directory
RewriteCond %{REQUEST_URI} !^/test/logs/ [NC]
# Handle all other URIs using Zen Cart (its index.php)
RewriteRule .* test/index.php [QSA,L]

## END CEON URI MAPPING REWRITE RULE (folder "test")

## BEGIN CEON URI MAPPING REWRITE RULE (site root)

# Don't rewrite the test folder
RewriteCond %{REQUEST_URI} !^/test/ [NC]
# Don't rewrite any URIs ending with a file extension (ending with .[xxxxx])
RewriteCond %{REQUEST_URI} !\.[a-z]{2,5}$ [NC]
# Don't rewrite any URIs for some, popular specific file format extensions,
#   which are not covered by main file extension condition above
RewriteCond %{REQUEST_URI} !\.(mp3|mp4|h264)$ [NC]
# Don't rewrite any URIs for some specific file format extensions,
#   which are not covered by main file extension condition above
#   Uncomment the following line to apply this condition! (Remove the # at the start of the next line)
#RewriteCond %{REQUEST_URI} !\.(3gp|3g2|h261|h263|mj2|mjp2|mp4v|mpg4|m1v|m2v|m4u|f4v|m4v|3dml)$ [NC]
# Don't rewrite admin directory
RewriteCond %{REQUEST_URI} !^/admin [NC]
# Don't rewrite editors directory
RewriteCond %{REQUEST_URI} !^/editors/ [NC]
# Don't rewrite darkangel directory
RewriteCond %{REQUEST_URI} !^/private/ [NC]
# Don't rewrite cgi-bin directory
RewriteCond %{REQUEST_URI} !^/cgi-bin/ [NC]
# Handle all other URIs using Zen Cart (its index.php)
RewriteRule .* index.php [QSA,L]

## END CEON URI MAPPING REWRITE RULE (site root)


## EXPIRES CACHING ##

<IfModule mod_expires.c>
ExpiresActive On
ExpiresByType image/jpg "access plus 1 year"
ExpiresByType image/jpeg "access plus 1 year"
ExpiresByType image/gif "access plus 1 year"
ExpiresByType image/png "access plus 1 year"
ExpiresByType text/css "access plus 1 month"
ExpiresByType application/pdf "access plus 1 month"
ExpiresByType text/x-javascript "access plus 1 month"
ExpiresByType application/x-shockwave-flash "access plus 1 month"
ExpiresByType image/x-icon "access plus 1 year"
ExpiresDefault "access plus 2 days"
</IfModule>

## EXPIRES CACHING ##

NOTE 1: mod_rewrite rules should always go from the most specific at the top to the most general at the bottom. They are matched in order from top to bottom (and L does not always mean last in a .htaccess file).

NOTE 2: The above assumes the "live" store is installed at "/public/" (URL of /) and the "test" store is installed at "/public/test/" (URL of /test/).

NOTE 3: If multiple domain names point to the same web root, one may wish to use slightly different code for the FQDN redirect.

Thanks, I will try that once I get all the owners stuff situated for transferring, right now I am answering more questions fromt eh owner than working on the site...LOL

DarkAngel:

Thanks, I will try that once I get all the owners stuff situated for transferring, right now I am answering more questions fromt eh owner than working on the site...LOL
Honestly if Conor were alive, he'd tell you that you need to setup your test site using a sub-domain and not just a simple folder off the root.. It will look like this:

Live site: http://yourdomain.com
Test Site: http://testsite.yourdomain.com

Ask your host for help in setting up a subdomain to point at your test site's folder if you don't know how to do this -- or Google it. This way your test site will behave like a top level domain and your production site's .htaccess SHOULD work on your test site too.. It will make code migrations MUCH easier too..

Thank you Diva, you always point out what my feeble mind tends to block out.

I shall do that...I am so mind boggled that i never thought of that.

Honestly if Conor were alive, he'd tell you that you need to setup your test site using a sub-domain and not just a simple folder off the root.. It will look like this:

Live site: http://yourdomain.com
Test Site: http://testsite.yourdomain.com

I would agree.
Just to add my meagre experience, for many moons I was developing Zen Cart locally using an alias in the Apache config, so I would access my sites as
192.168.1.100/mytestsite.
It was only when I starting using the URI mapping that I was forced to do it "properly" and use virtual hosts and a redirect in my windows host files to use
https://www.mysite.local to access the local site. Otherwise the URI mapping was problematical.

DivaVocals:

...

Live site: http://yourdomain.com
Test Site: http://testsite.yourdomain.com
nods Still sometimes issues though if the subdomain's public_root is nested inside the domain's public_root... Can be avoided by making sure the subdomain is not nested inside the public_root (cPanel hosting allows this, some bargain basement hosting does not).

Only real catch with using a subdomain is testing with SSL enabled. But one can always turn it off SSL during testing and turn it back on when ready to go live.

torvista:

I would agree.
...
It was only when I starting using the URI mapping that I was forced to do it "properly" and use virtual hosts and a redirect in my windows host files to use ```
www.mysite.local

*nods* This is how I do the majority of my testing (local AMPP configurations - no nested public_root folders and certificates signed by a locally trusted authority). Allows testing with SSL enabled - without paying for a certificate or a hosting provider to install a certificate.


So where is this bandwagon headed? Might I suggest we meander into a club with live music?

lhungil:

nods Still sometimes issues though if the subdomain's public_root is nested inside the domain's public_root... Can be avoided by making sure the subdomain is not nested inside the public_root (cPanel hosting allows this, some bargain basement hosting does not).True.. but I've managed to work through/around this...

lhungil:

Only real catch with using a subdomain is testing with SSL enabled. But one can always turn it off SSL during testing and turn it back on when ready to go live.I've managed to get away with doing things this way.. giggle I know I know.. I can HEAR you smacking my hand from here..

lhungil:

So where is this bandwagon headed? Might I suggest we meander into a club with live music?Did someone say music AND cocktails?????

Hello

I use a shared ssl certificate and my https server cataloge is //..com/~***
It doesnt work and the installation checker says I cant have any subdirectory in the path in the configure.php

my host appends the /~ for my account.

Thanks Alot

Hi,
Would you be able to post the contents of your configuration file.
It might help in trying to figure out what the problem may be.
Thanks

merica:

Hello

I use a shared ssl certificate and my https server cataloge is //..com/~***
It doesnt work and the installation checker says I cant have any subdirectory in the path in the configure.php

my host appends the /~ for my account.

Thanks Alot

merica:

Hello

I use a shared ssl certificate and my https server cataloge is //..com/***
It doesnt work and the installation checker says I cant have any subdirectory in the path in the configure.php
my host appends the / for my account.
Thanks Alot

Why not just buy an SSL Certificate? https://www.instantssl.com/free-ssl-certificate.html?track=3338&key5sk1=0c9103f7f16c83c6279a55d4ab45022b5bc670fe

That would solve it? I think I have a free one from positivessl from the hosting plan