On the servers I own SSL works for better than Shared SSL and with the prices these days it is a good idea for everyone to use it....

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

ravynw34:

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

TSMedia:

On the servers I own SSL works for better than Shared SSL and with the prices these days it is a good idea for everyone to use it....

merica:

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

So the centrl issue (and one reason suggested to post your configure.php file though if you do be sure to obscure your DB_PASSWORD) is that the directories (DIR_WS_CATALOG and DIR_WS_HTTPS_CATALOG) need to be the same under http as well as https. To accomplish this if so desired with a shared SSL (though also suggest obtaining a dedicated one) is to incorporate the ~ portion into the HTTP_SERVER and HTTPS_SERVER as applicable.

The .htaccess may also need revision to support this setup, but there are a number of ways to accomplish that.

Will post back after I check this...Thanks

Hi! I am using Zen cart 1.5.4 and Ceon URi mapping 4.5.0
I am having two websites, both separate installations of zen cart, one at https://www.raunharman.com and the other at https://www.raunharman.com/wedding_prom_dresses/index.php (lets call this the wholesale site)
I have separately installed zen cart as well as Ceon URi mapping module for both the sites.
I have one .htaccess in the site root which works well for the main site (https://www.raunharman.com), but when I use a separate .htaccess file for the wholesale site, I get a 404 error.
Where am I going wrong?
Please suggest.

have you thought of making the second one a subdomain making it wedding_prom_dresses.nameofdomain

then you can add the information ceon gave you to the main htaccess...unless the second sites info is different from the first store then add it to the main htaccess file

did i confuse you yet? sorry

DarkAngel:

have you thought of making the second one a subdomain making it wedding_prom_dresses.nameofdomain

then you can add the information ceon gave you to the main htaccess...unless the second sites info is different from the first store then add it to the main htaccess file

did i confuse you yet? sorry

I could consider it.
The 2nd site is very old and I get substantial traffic through it. If I take the subdomain route, will the old URLs be accessible / searchable.
Anyway, could you please give me the specific lines to be added to .htaccess in both the cases.
Thanks for your quick reply.

when you are in admin and click the modules/ceon uri mapping (seo) config/installation check

that last one will give you a linksaying "click here to go to......installation check page, it will then check to make sure you did it right, then at the bottom---if no errors pop up---you wil see the code to put into your main .htaccess file.

If you do the same thing for your wholesale store and the code is different then you can just add both codes to the main .htaccess file

making it a subdomain in your c-panel will actually make it appear as though it is a "real" domain vs an extension of the main store.

You will most likely need to edit your two config files with the proper path information. The store links will be different also so you might need to reset those also. It has been awhile since I set up a sub domain so my thought process is rusty.

DarkAngel:

when you are in admin and click the modules/ceon uri mapping (seo) config/installation check

that last one will give you a linksaying "click here to go to......installation check page, it will then check to make sure you did it right, then at the bottom---if no errors pop up---you wil see the code to put into your main .htaccess file.

If you do the same thing for your wholesale store and the code is different then you can just add both codes to the main .htaccess file

making it a subdomain in your c-panel will actually make it appear as though it is a "real" domain vs an extension of the main store.

You will most likely need to edit your two config files with the proper path information. The store links will be different also so you might need to reset those also. It has been awhile since I set up a sub domain so my thought process is rusty.

Thanks for your help.
I will try this out and revert.

I merged the two codes, deleted the lines that seemed repetitive, but still got an Internal Server Error.
However, I guess the following two statements could be contradictory.

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

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

and

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

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

Or can both of them stay together in the same .htaccess file?

raunharman:

I merged the two codes, deleted the lines that seemed repetitive, but still got an Internal Server Error. ...
Please supply the filesystem layout of the FTP and WEB server. Some examples of common server layouts:

-+- ROOT (FTP root / private)
 |
 +- public_html (WEB root / public / domain 1) - Zen Cart install
 |
 +- domain2 (FTP root / private / domain 2)
 |      |
 |      +- public_html (WEB root / public / domain 2) - Zen Cart install
 
OR

-+- ROOT (FTP root / private)
 |
 +- public_html (WEB root / public / domain 1) - Zen Cart install
 |      |
 |      +- domain2 (WEB root / public / domain 2) - Zen Cart install

OR

-+- public_html (FTP & WEB root / public / domain 1) - Zen Cart install
 |      |
 |      +- domain2 (WEB root / public / domain 2) - Zen Cart install

OR

-+- public_html (FTP & WEB root / public)
 |      |
 |      +- domain1 (WEB root / public / domain 1) - Zen Cart install
 |      |
 |      +- domain2 (WEB root / public / domain 2) - Zen Cart install

Also provide the full contents of EACH .htaccess file (in each Zen Cart installation root and any parent folders). Change any "admin folder" references to "admin" to obscure. When supplying the contents of the .htaccess file please use code tags around the content (click the # in the editor to add these). This will make reading them easier.

Angel is right about setting up the wholesale site as a sub-domain. You can then redirect traffic from the "Old" URLs to the "New" sub-domain URL using a rewrite rule. I'm on a mobile device so I don't have the exact rule off the top of my head.. but I'm sure others here can help with that..

In the meantime we can't help solve your current issue without seeing the contents of your .htaccess file for the wholesale site..

lhungil:

Please supply the filesystem layout of the FTP and WEB server. Some examples of common server layouts:

-+- ROOT (FTP root / private)
|
+- public_html (WEB root / public / domain 1) - Zen Cart install
|
+- domain2 (FTP root / private / domain 2)
| |
| +- public_html (WEB root / public / domain 2) - Zen Cart install

OR

-+- ROOT (FTP root / private)
|
+- public_html (WEB root / public / domain 1) - Zen Cart install
| |
| +- domain2 (WEB root / public / domain 2) - Zen Cart install

OR

-+- public_html (FTP & WEB root / public / domain 1) - Zen Cart install
| |
| +- domain2 (WEB root / public / domain 2) - Zen Cart install

OR

-+- public_html (FTP & WEB root / public)
| |
| +- domain1 (WEB root / public / domain 1) - Zen Cart install
| |
| +- domain2 (WEB root / public / domain 2) - Zen Cart install

> 
> Also provide the full contents of EACH .htaccess file (in each Zen Cart installation root and any parent folders). Change any "admin folder" references to "admin" to obscure. When supplying the contents of the .htaccess file please use code tags around the content (click the # in the editor to add these). This will make reading them easier.



Thanks for your elaborate answer.

Actually it goes like this:
public_html (FTP & WEB root / public / domain 1) - Zen Cart install
public_html (FTP & WEB root / public / domain 1/folder) - Zen Cart install

The wholesale site does not have a separate domain name yet. it is in a folder by the name wedding_prom_dresses

The htaccess for domain1 is as follows:
## BEGIN CEON URI MAPPING REWRITE RULE

RewriteEngine On

# 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 scarves directory
RewriteCond %{REQUEST_URI} !^/scarves/ [NC]
# Don't rewrite wedding_prom_dresses directory
RewriteCond %{REQUEST_URI} !^/wedding_prom_dresses/ [NC]
# Don't rewrite cron directory
RewriteCond %{REQUEST_URI} !^/cron/ [NC]
# Don't rewrite bmz_cache directory
RewriteCond %{REQUEST_URI} !^/bmz_cache/ [NC]
# Don't rewrite twitter directory
RewriteCond %{REQUEST_URI} !^/twitter/ [NC]
# Don't rewrite jewelry directory
RewriteCond %{REQUEST_URI} !^/jewelry/ [NC]
# Don't rewrite logs directory
RewriteCond %{REQUEST_URI} !^/logs/ [NC]
# Don't rewrite min directory
RewriteCond %{REQUEST_URI} !^/min/ [NC]
# Handle all other URIs using Zen Cart (its index.php)
RewriteRule .* index.php [QSA,L]

## END CEON URI MAPPING REWRITE RULE



and the htaccess for the wholesale site is:

## BEGIN CEON URI MAPPING REWRITE RULE

RewriteEngine On

# ONLY rewrite URIs beginning with /wedding_prom_dresses/
RewriteCond %{REQUEST_URI} ^/wedding_prom_dresses/ [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} !^/wedding_prom_dresses/admin [NC]
# Don't rewrite editors directory
RewriteCond %{REQUEST_URI} !^/wedding_prom_dresses/editors/ [NC]
# Don't rewrite cron directory
RewriteCond %{REQUEST_URI} !^/wedding_prom_dresses/cron/ [NC]
# Don't rewrite bmz_cache directory
RewriteCond %{REQUEST_URI} !^/wedding_prom_dresses/bmz_cache/ [NC]
# Don't rewrite twitter directory
RewriteCond %{REQUEST_URI} !^/wedding_prom_dresses/twitter/ [NC]
# Don't rewrite logs directory
RewriteCond %{REQUEST_URI} !^/wedding_prom_dresses/logs/ [NC]
# Don't rewrite min directory
RewriteCond %{REQUEST_URI} !^/wedding_prom_dresses/min/ [NC]
# Handle all other URIs using Zen Cart (its index.php)
RewriteRule .* wedding_prom_dresses/index.php [QSA,L]

## END CEON URI MAPPING REWRITE RULE


Thanks for your time.

raunharman:

Thanks for your elaborate answer.

Actually it goes like this:
public_html (FTP & WEB root / public / domain 1) - Zen Cart install
public_html (FTP & WEB root / public / domain 1/folder) - Zen Cart install

The wholesale site does not have a separate domain name yet. it is in a folder by the name wedding_prom_dresses

The htaccess for domain1 is as follows:

BEGIN CEON URI MAPPING REWRITE RULE

RewriteEngine On

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 scarves directory

RewriteCond %{REQUEST_URI} !^/scarves/ [NC]
# Don't rewrite wedding_prom_dresses directory
RewriteCond %{REQUEST_URI} !^/wedding_prom_dresses/ [NC]

Don't rewrite cron directory

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

Don't rewrite bmz_cache directory

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

Don't rewrite twitter directory

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

Don't rewrite jewelry directory

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

Don't rewrite logs directory

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

Don't rewrite min directory

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

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

RewriteRule .* index.php [QSA,L]

END CEON URI MAPPING REWRITE RULE

and the htaccess for the wholesale site is:

BEGIN CEON URI MAPPING REWRITE RULE

RewriteEngine On

ONLY rewrite URIs beginning with /wedding_prom_dresses/

RewriteCond %{REQUEST_URI} ^/wedding_prom_dresses/ [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} !^/wedding_prom_dresses/admin [NC]

Don't rewrite editors directory

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

Don't rewrite cron directory

RewriteCond %{REQUEST_URI} !^/wedding_prom_dresses/cron/ [NC]

Don't rewrite bmz_cache directory

RewriteCond %{REQUEST_URI} !^/wedding_prom_dresses/bmz_cache/ [NC]

Don't rewrite twitter directory

RewriteCond %{REQUEST_URI} !^/wedding_prom_dresses/twitter/ [NC]

Don't rewrite logs directory

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

Don't rewrite min directory

RewriteCond %{REQUEST_URI} !^/wedding_prom_dresses/min/ [NC]

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

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

END CEON URI MAPPING REWRITE RULE

Thanks for your time.

It would appear that the issue is that your wholesale site is in a sub-directory of the main site, and you have a re-write rule for your main domain to NOT re-write that same directory.. I STRONGLY suggest that you create a subdomain for the wholesale site, and if your host allows it put it in a folder OUTSIDE your public_html folder.. I have my subdomains on my dev host setup as follows: subdomains/public_html/NAME-OF-MY-SUB-DOMAIN-FOLDER
This way you can correct the main domain .htaccess, and the sub-domain and main domain will no longer step on each others toes.. You will just need to include a re-write rule to re-direct traffic from your wholesale site's old URL base to the new sub-domain base.

mc12345678:

So the centrl issue (and one reason suggested to post your configure.php file though if you do be sure to obscure your DB_PASSWORD) is that the directories (DIR_WS_CATALOG and DIR_WS_HTTPS_CATALOG) need to be the same under http as well as https. To accomplish this if so desired with a shared SSL (though also suggest obtaining a dedicated one) is to incorporate the ~ portion into the HTTP_SERVER and HTTPS_SERVER as applicable.

The .htaccess may also need revision to support this setup, but there are a number of ways to accomplish that.

I got it to work using the new ssl domain, but howcome it adds (ex: /category/product-name?cPath=37_11&) to the end of every product url?

merica:

I got it to work using the new ssl domain, but howcome it adds (ex: /category/product-name?cPath=37_11&) to the end of every product url?

If I may suggest reviewing the instructions. This is a result of the product being linked and is normal. The additional content ensures a few things are displayed correctly including the breadcrumbs at the top of the screen.

Otherwise, congrats on getting it. To work. :)

raunharman:

... it goes like this:
public_html (FTP & WEB root / public / domain 1) - Zen Cart install
public_html (FTP & WEB root / public / domain 1/folder) - Zen Cart install

...

The htaccess for domain1 is as follows:
...
and the htaccess for the wholesale site is:
...
Do you also have a .htaccess file at either "/.htaccess" or "/public/.htaccess"? Not only are the .htaccess files in the current path run, but also any in a parent path... This is why I typically ask for ALL .htaccess files when trying to help people troubleshoot.

If you are receiving a "HTTP 500 / Internal Server Error", this usually indicates something is wrong in the .htaccess file (or the server does not like something in the .htaccess file). The WEB SERVER error logs (if enabled by your hosting provider) should indicate the cause of the Internal Server Error.

Based on the above, it sounds like you have one .htaccess file at "/public/domain1/.htaccess" and another at "/public/domain1/folder/.htaccess"? If so this could be the cause... The rules you list as being in the second .htaccess will not be correct when added at "/public/domain1/folder/.htaccess" (should be added to the START of "/public/domain1/.htaccess" instead).

DivaVocals:

... I STRONGLY suggest that you create a subdomain for the wholesale site, and if your host allows it put it in a folder OUTSIDE your public_html folder.. I have my subdomains on my dev host setup as follows: subdomains/public_html/NAME-OF-MY-SUB-DOMAIN-FOLDER
This way you can correct the main domain .htaccess, and the sub-domain and main domain will no longer step on each others toes.. You will just need to include a re-write rule to re-direct traffic from your wholesale site's old URL base to the new sub-domain base.
Great advice! I typically do things as follows when configuring add-on domains and subdomains via cPanel:

-+- ROOT (FTP root / private)
 |      |
 |      +- public_html (core cPanel WEB Root / public)
 |      |
 |      +- additional (private)
 |      |      |
 |      |      +- www.primarydomain (primary domain FTP root / private)
 |      |      |      |
 |      |      |      +- public_html (primary domain WEB root / public)
 |      |      |
 |      |      +- domainname (add-on domain FTP root / private)
 |      |      |      |
 |      |      |      +- public_html (add-on domain WEB root / public)
 |      |      |
 |      |      +- host.domainname (subdomain FTP root / private)
 |      |      |      |
 |      |      |      +- public_html (subdomain domain WEB root / public)
 |      |      |
 |
 +- other_folders
 |

As noted by DivaVocals, this separates out each domain (and provides each with a private place to store data). This helps reduce the number of potential conflicts when crafting mod_rewrite directives (or other Apache directives). By creating individual FTP users for each domain (and restricting the users to a specific domain's FTP root), when accessing the site remotely for maintenance each site is kept separate. IMHO, this makes synchronizing files (and creating manual backups) far easier because the FTP client will open by default directly to the domain's FTP root.

Basically a win-win (if your hosting provider allows something similiar to the above).

Another useful side effect is one can grant third parties FTP access specifically to a single domain (instead of needing to provide the MASTER FTP account). Because one has specific accounts for FTP, the cPanel account no longer needs to be used for FTP (and really should not be used for FTP ever IMHO). One of the many reasons Zen Cart recommends NOT using FTP (and using SFTP or FTPS) instead, is FTP essentially sends passwords in plaintext.

While adding "www.primarydomain" is not required, I personally do this so I can more easily work with the content in the primary domain (separating it from . I then rewrite or redirect (depending upon the request) from the core cPanel WEB Root to "www.primarydomain". On some hosting providers one can also customize the version of PHP (and PHP settings) for each domain (advanced topic way beyond the scope of this thread).

Keep in mind server side code (such as PHP) will still be able to transverse all of the domains (and subdomains), so you still need to trust those adding code to your sites (and beware of security holes / PCI compliance issues raised by software installed on any of the domains in the same hosting account)...

Okay I'm getting a bit off topic... Basically just restating, emphasizing, and providing other reasons for not testing Zen Cart (or modules such as CEON URI Mapping) in a folder (when the final destination will not be in a folder)... Always best to test mimicking the final resting place as closely as possible.

Our site just stopped working. Not sure why. No matter what you click, you get the main page. Been using CEON URI Mapping for years.

https://www.fantasycostume.net

masterrusty:

Our site just stopped working. Not sure why. No matter what you click, you get the main page. Been using CEON URI Mapping for years.

https://www.fantasycostume.net

Then wouldn't mind identifying things such as ZC version, PHP version, CEON URI Mapping version, etc...? Went to the site though and did not see any issue. What was done to correct it?

masterrusty:

Our site just stopped working. Not sure why. No matter what you click, you get the main page. Been using CEON URI Mapping for years.

www.fantasycostume.net

Two things...

Define what you mean by "stopped working"
What makes you think the cause is THIS module??

and then as mc12345678 suggests.. post some site details..

Several years ago, Conner posted that the ?chapter=0 added to the EZ pages was just part of the way CEON worked. It looks like there may now be a work around available and I saw one other person ask the same question.

I am NOT a developer, but I can follow instructions and do a lot of the work behind the scenes with installs myself if the directions are clear... however, due to my lack of background, there may be things I simply don't understand.

Specifically, this module is working GREAT with my upgraded v1.5.4 cart. (just upgraded 2 days ago). With the upgrade, all my products and categories, etc are good!
http://prowoodfingerboards.com/fingerboards/decks/black-label-fingerboard

Now that I am current, I am hoping I can go back to my CEON module and try to address an ongoing issue:

My EZ pages are picking up the chapter info at the end of the url and I don't use or want that.
See: http://prowoodfingerboards.com/about-prowood?chapter=0

Server Information
Server OS: Linux 3.12.35.1418868451 Database: MySQL 5.5.42-37.1
HTTP Server: Apache
PHP Version: 5.2.17 (Zend: 2.2.0)

Module © Copyright 2008-2015 Ceon - Files Version: 4.5.0 Installed Version: 4.5.0

**It looks like I have the ability to **

Remove Words:
This is a comma-separated list of words which will be removed from the auto-generated URIs. Single characters can also be entered but will only be removed if they are surrounded by spaces (e.g. “-” entered below will remove the dash from “Star Wars - Director's Cut” but not from “Spider-Man”). For example, if the store would like to remove “-”, “and” and “an” from the URIs you'd enter the following:
-, and, an

and

Character/String Replacements:
This is a comma-separated list of pairs of characters/strings and replacement characters/strings.
The characters/strings to be replaced in the auto-generated URIs should be separated from their replacements using “=>”. E.g. “£=>GBP, $=>USD”. Any spacing entered for a replacement will be used but replaced with the usual whitespace replacement character (so be careful not leave an extra space at the end of the text entered below if it is not intended!). Spacing entered for the strings/characters to be replaced will be removed/ignored; so it's fine to add a space after each comma, to make things easier to read.
To remove a character/string simply replace it with nothing. E.g. “£=>, $=>” removes £ and $ dollar signs from the auto-generated URI.

I have tried to add in the errant string '?chapter=0' in various ways, but I cannot get this to work for me. I did try to add a new ez page after I wrote the rule and the update note on the page was correct telling me .......com/party-site was correct, but when I pulled it up on a new window, the string was there and the url was ...... com/party-event?chapter=0

Can anyone tell me what I am doing wrong?
THANKS!