Ceon URI Mapping v4.x

[lagcher.r]

This sounds like an issue with the way your hosting company (or you via cPanel) configured the new domain. You need to define separate public_html folders for each domain (cPanel calls them "document root"). This eliminates the need for complicated .htaccess rules in each folder to handle redirections caused by two domains sharing a document root.

If your hosting provider has your site structured with "/username/public_html"... You can configure separate document root folders using cPanel for the second domain. This MUST be done when the domain is added. If it was not you would need to remove and re-add the domain. Under cPanel go to "Domains" > "Add-On domains". You should see the option to remove existing domains and also the option to add a new domain. One of the fields when adding a domain is "document root". This would then become "/username/domain2/public_html". Why the extra folder in the middle? So your new domain has somewhere to place sensitive files such as "cache", "logs", and other data if needed.

If your hosting provider does not give you write access to a folder below the "public_html" (document root) folder, you may want to look at a different provider. Having a place to store sensitive data is a good idea, and lets you setup multiple domains with less hassle.

I have a few clients who have multiple domains hosted with companies using cPanel and this method works well.

Alternatively you can add an exclusion to the .htaccess rules added by CEON URI Mapping to exclude requests made for domain2.com. But you will have to make a number of changes in domain2.com for domain2.com's .htaccess rules to work with CEON URI Mapping... It will be easier and better in the long run to just configure both domains on the server (via cPanel) with separate "public_html" (document root) folders.

Can this also be done with an ftp client?

[lagcher.r]

This is a respectable and well known host in the netherlands. I did not choose this webhosting because it was"cheap" I chose it because it had been recommended by many statisfied users. The only thing is their support that could be better.

[schoolboy]

Are you able to configure add-on domains by yourself? Or do you rely on "support" which looks like it takes some time to respond.

A GOOD host will permit their users significant levels of server management - particularly when eCommerce is involved.

Again... you need a host that HELPS you run your business. If this one is not up to being your "partner", then go find one that is. It matters not if they came "highly recommended"... if you cannot get the level of management and service you require, they are a hindrance to your business.

[lagcher.r]

Your right, i'm going to contact them tommorow. If they can't help me I will be looking for a better hosting
company.

[lhungil]

Correct, one should not have multiple "alternative" URL modules installed. One could leave the Ultimate URLs .htaccess in place (before the CEON rules), but doing so will probably cause unneccessary redirects. As part of switching - One would want to enter the old (Ultimate) URLs into the CEON URI database.

Hello Diva,
There IS INDEED an issue with Ultimate SEO and FEC evidenced by days of dialogue on forums and according to everyone else, including Numinix AND ihungil, author of the plugin. Obviously you have not used both plugins on site.
cheers, Mike

Actually both Ultimate URLs and FEC can operate together. I've posted on this topic before and Diva is one of the contributors who helped narrow down the issue (caused by Numinix altering the default Zen Cart administrative configuration flow - and - Ultimate URLs depending on the stock Zen Cart administrative page for managing configuration options). They are not incompatible with the appropriate patches to the Numinex code installed.

Any further discussion on the topic of Ultimate URLs and Numinix modifications to the Zen Cart administrative configuration process does not belong in the CEON URI thread, but over at the Ultimate URLs (or FEC) support threads.

[DivaVocals]

Correct, one should not have multiple "alternative" URL modules installed. One could leave the Ultimate URLs .htaccess in place (before the CEON rules), but doing so will probably cause unneccessary redirects. As part of switching - One would want to enter the old (Ultimate) URLs into the CEON URI database.


Actually both Ultimate URLs and FEC can operate together. I've posted on this topic before and Diva is one of the contributors who helped narrow down the issue (caused by Numinix altering the default Zen Cart administrative configuration flow - and - Ultimate URLs depending on the stock Zen Cart administrative page for managing configuration options). They are not incompatible with the appropriate patches to the Numinex code installed.

Any further discussion on the topic of Ultimate URLs and Numinix modifications to the Zen Cart administrative configuration process does not belong in the CEON URI thread, but over at the Ultimate URLs (or FEC) support threads.

BOOM! But what the heck do I know since I've "obviously" never used these two together...

[Chargin]

Hi all, Ive recently migrated a ZC site from one server to another using the transfer tool. Currently the site, after this transfer, cannot access the admin folder, or /blog. /blog/wp-admin does work though. /admin/login.php gives a blank page and /admin/ gives a 500.shtml error page not found.
What could I check here? The new server is using php 5.3 same as the old, ZC is 1.39h. Ive tried renaming the htaccess files in root and admin but with no success. It looks to me like CEON is the cause but cant say for sure. Perhaps theres a way to disable it via phpmyadmin?

[Chargin]

Hi all, Ive recently migrated a ZC site from one server to another using the transfer tool. Currently the site, after this transfer, cannot access the admin folder, or /blog. /blog/wp-admin does work though. /admin/login.php gives a blank page and /admin/ gives a 500.shtml error page not found.
What could I check here? The new server is using php 5.3 same as the old, ZC is 1.39h. Ive tried renaming the htaccess files in root and admin but with no success. It looks to me like CEON is the cause but cant say for sure. Perhaps theres a way to disable it via phpmyadmin?

Well its all fixed, turns out it was php being at 5.3 and zend was not enabled. Nothing to do with CEON!

[panservolvo]

First of all, I have had this module installed for several years, so my server host does have the required specifications.
Now I have created a fresh install of zc 153 and I am trying to install this module again.
I have uploaded all the files. When I try to log into admin I get a blank page 500, error.
If I upload all the backup files the same error occurs.
If I delete all the CEON- files in admin and upload the backup files, I am able to log in to admin again.

Any suggestions to what may be the problem?

ps: I can't link to the page with the problem because its a live environment so I had to delete the module to be able to use admin.

[augie0041]

Well ... don't change the name of the zc_install directory, delete it immediately. It should not be on the server under any name at all.

As for changing the name of the admin folder again, yes that is a good idea, but security by obscurity is not security at all.

There should be no way in even if the admin folder name is public. Changing it just reduces the volume of hacking attempts.

Thanks Enzo and Hairydog, I changed my admin folder name, and deleted the install folder. So what else am I doing wrong? Haha. I turned off the rewrite instructions for now so I can use my site without getting 404 errors.