Re: Ceon URI Mapping v4.x
Quote:
Originally Posted by
schoolboy
As lhungil has said, you need to set up ADD-ON DOMAINS on your hosting account. In order to do this, the domain(s) you intend to ADD have to be registered domains and must be resolvable.
SOME hosts do not permit ADD-ON domains, and some do.
You should speak to your host about this, and if you can add more domains to your hosting space, then do this the proper way through C-Panel.
If you do not know how to do it, then provide the additional domain names to your host, and ask them to set up the ADD-ON domains for you.#
It takes less than a minute to configure an ADD-ON domain, so don't let them tell you it is a complex and expensive job. It isn't.
Quote:
Originally Posted by
lhungil
No problem, and make sure the
document root folders are not nested. They should look something like:
Code:
/username/ --+
|
+--public_html/
|
+--domain2/public_html/
|
+--domain3/public_html/
Quote:
Originally Posted by
schoolboy
If you intend to run eCommerce then a critical part of your business operation is a proper, reliable and knowledgeable host. It seems like you have gone with a "cheap and nasty" crowd in an effort to save yourself a couple of dollars. In fact, you have gone down a very expensive road... How long have you been spending on this problem of add-on domains? Setting up two or three add-on domains will take no more than four minutes if you are hosting with a good host. By now, you could have had three or four eCommerce sites set up and working well. Instead, you have made no progress at all.
You have puzzled over this for several DAYS, and you are no closer to resolving your issue.
Do yourself a big favour... spend a dollar or two more, and get with a good host.
Quote:
Originally Posted by
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.
nods in agreement with ALL of this!!! :yes:
Quote:
Originally Posted by
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.
I have to agree with EVERYTHING lhungil and schoolboy have said.. and wanted to only add this.. You said a MOUTHFUL when you said "The only thing is their support that could be better"
That my friend is your CLUE/HINT/BURNING BUSH, what have you that you NEED a new host for your website.. Schoolboy is right.. All the time you spent trying to figure this out, could have been avoided with the RIGHT hosting company.. You need one that is a HELP not a hindrance to your site and schoolboy rightly pointed out..
Re: Ceon URI Mapping v4.x
Following lhungil's example, I thought that it would be good to add this post to this support thread..
On another note:
This thread's purpose is to support "Ceon URI Mapping". It provides a place for people new to the module as well as experienced users of the module to interact and help each other install, upgrade, and use this module. It also provides a place for people to report any potential bugs they may have found (as well as fixes).
I would ask everyone who reads (or posts) to this thread keep the above stated purpose of this thread in mind. Kindly keep the posts in this thread relevant to the above stated purpose. I encourage people to discuss other topics, but please discuss them in a different thread in a relevant section of the forums.
For those asking for help: keep in mind the people on the Zen Cart forums are not here 24x7 and for the most part give freely of their personal time to help. It may take a couple days for someone to read your message. So be patient when asking for help. I would also re-iterate reading the "Posting Tips" (scroll up when posting / replying) is a good idea. Answering the questions found in the "Posting Tips" will help save time and helps give those reading your post a better picture of what might be causing the problem you are experiencing.
Thank You
Re: Ceon URI Mapping v4.x
ZC 1.5
I'm trying to determine what code should be placed in the .httaccess file to prevent certain URI's containing certain character strings from rewriting.
The code I have is for character string x45poty:
# Don't rewrite URI if contains "x45poty" string
RewriteCond %{REQUEST_URI} !^/*x45poty* [NC]
This doesn't work.
Any suggestions would be greatly appreciated.
Re: Ceon URI Mapping v4.x
Has anyone had issues with CEON not playing well with Captcha? The Captcha field does not appear on the contact or create account page when the URI is set. I changed the URI for the contact page to /index.phpmain_pagecontact_us and the Captcha now appears. But, the login page does not show the Captcha and then errors out when a new account is created, showing that Captcha was not entered. I tried changing the URI mapping on both the login and create account pages with no luck. So, I had to disable Captcha on create account.
Re: Ceon URI Mapping v4.x
Quote:
Originally Posted by
joepixel
Has anyone had issues with CEON not playing well with Captcha? The Captcha field does not appear on the contact or create account page when the URI is set. I changed the URI for the contact page to /index.phpmain_pagecontact_us and the Captcha now appears. But, the login page does not show the Captcha and then errors out when a new account is created, showing that Captcha was not entered. I tried changing the URI mapping on both the login and create account pages with no luck. So, I had to disable Captcha on create account.
Did you try a thread search to search this thread for CAPTCHA? If this has been an reported issue you ahould find the info that way..
Re: Ceon URI Mapping v4.x
Hi Guys, installed the plugin, added the code for .htaccess - I have an issue. If i have yourdomain.co.uk/blog ect and it's now showing the page not found.
Any ideas on what to do, or could someone include a fresh .htaccess file?
Thanks.
James
Re: Ceon URI Mapping v4.x
Quote:
Originally Posted by
PetleyJ
Hi Guys, installed the plugin, added the code for .htaccess - I have an issue. If i have yourdomain.co.uk/blog ect and it's now showing the page not found.
Any ideas on what to do, or could someone include a fresh .htaccess file?
Thanks.
James
What would be REALLY helpful is to post the .htaccess file.. (will keep folks from guessing a bit..) Also a link to the site would also help.. Are you sure the issue isn't with your blog's .htaccess file???
Re: Ceon URI Mapping v4.x
Hi Diva,
the link is: --- WARNING!! ADULT SITE! NSFW! http://naughtynightsuk.co.uk
If you try /competitions or /community ect you will see it comes up with the ZC sitemap.
I can confirm the directories are there.
Here's what's in the .htaccess file in the root.
## 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} !^/administration [NC]
# Don't rewrite editors directory
RewriteCond %{REQUEST_URI} !^/editors/ [NC]
# Don't rewrite bellsconfectionary directory
RewriteCond %{REQUEST_URI} !^/bellsconfectionary/ [NC]
# Don't rewrite logs directory
RewriteCond %{REQUEST_URI} !^/logs/ [NC]
# Don't rewrite blog directory
RewriteCond %{REQUEST_URI} !^/blog/ [NC]
# Don't rewrite wpimages directory
RewriteCond %{REQUEST_URI} !^/wpimages/ [NC]
# Don't rewrite tempEP directory
RewriteCond %{REQUEST_URI} !^/tempEP/ [NC]
# Don't rewrite bells directory
RewriteCond %{REQUEST_URI} !^/bells/ [NC]
# Don't rewrite adultshoppingdirect directory
RewriteCond %{REQUEST_URI} !^/adultshoppingdirect/ [NC]
# Don't rewrite toycleaner.co.uk directory
RewriteCond %{REQUEST_URI} !^/toycleaner\.co\.uk/ [NC]
# Don't rewrite waste directory
RewriteCond %{REQUEST_URI} !^/waste/ [NC]
# Don't rewrite shop directory
RewriteCond %{REQUEST_URI} !^/shop/ [NC]
# Don't rewrite cuminajiffy.co.uk directory
RewriteCond %{REQUEST_URI} !^/cuminajiffy\.co\.uk/ [NC]
# Don't rewrite parties directory
RewriteCond %{REQUEST_URI} !^/parties/ [NC]
# Don't rewrite te-amouk directory
RewriteCond %{REQUEST_URI} !^/te\-amouk/ [NC]
# Don't rewrite classes directory
RewriteCond %{REQUEST_URI} !^/classes/ [NC]
# Don't rewrite optional arrows directory
RewriteCond %{REQUEST_URI} !^/optional\ arrows/ [NC]
# Don't rewrite community directory
RewriteCond %{REQUEST_URI} !^/community/ [NC]
# Don't rewrite hub directory
RewriteCond %{REQUEST_URI} !^/hub/ [NC]
# Don't rewrite competitions directory
RewriteCond %{REQUEST_URI} !^/competitions/ [NC]
# Don't rewrite modules directory
RewriteCond %{REQUEST_URI} !^/modules/ [NC]
# Don't rewrite cgi-bin directory
RewriteCond %{REQUEST_URI} !^/cgi\-bin/ [NC]
# Don't rewrite 50shadesgrey.co.uk directory
RewriteCond %{REQUEST_URI} !^/50shadesgrey\.co\.uk/ [NC]
# Don't rewrite question directory
RewriteCond %{REQUEST_URI} !^/question/ [NC]
# Don't rewrite myfiles directory
RewriteCond %{REQUEST_URI} !^/myfiles/ [NC]
# Don't rewrite wpscripts directory
RewriteCond %{REQUEST_URI} !^/wpscripts/ [NC]
# Don't rewrite anglia-courier-services.co.uk directory
RewriteCond %{REQUEST_URI} !^/anglia\-courier\-services\.co\.uk/ [NC]
# Don't rewrite wp-content directory
RewriteCond %{REQUEST_URI} !^/wp\-content/ [NC]
# Don't rewrite affiliates directory
RewriteCond %{REQUEST_URI} !^/affiliates/ [NC]
# Don't rewrite languages directory
RewriteCond %{REQUEST_URI} !^/languages/ [NC]
# Don't rewrite kmlcommerce.co.uk directory
RewriteCond %{REQUEST_URI} !^/kmlcommerce\.co\.uk/ [NC]
# Don't rewrite sitemap directory
RewriteCond %{REQUEST_URI} !^/sitemap/ [NC]
# Don't rewrite extra_datafiles directory
RewriteCond %{REQUEST_URI} !^/extra_datafiles/ [NC]
# Handle all other URIs using Zen Cart (its index.php)
RewriteRule .* index.php [QSA,L]
## END CEON URI MAPPING REWRITE RULE
I couldn't upload the file due to invalid extension.
James
Re: Ceon URI Mapping v4.x
Quote:
Originally Posted by
mikebr
... I'm trying to determine what code should be placed in the .httaccess file to prevent certain URI's containing certain character strings from rewriting. ...
# Don't rewrite URI if contains "x45poty" string
RewriteCond %{REQUEST_URI} !^/*x45poty* [NC]
...
If you want to exclude all URIs containing the string "x45poty" (case insensitive) use the following:
Code:
# Don't rewrite URI if contains "x45poty" string
RewriteCond %{REQUEST_URI} !x45poty [NC]
Quote:
Originally Posted by
PetleyJ
Hi Guys, installed the plugin, added the code for .htaccess - I have an issue. If i have yourdomain.co.uk/blog ect and it's now showing the page not found. ... I couldn't upload the file due to invalid extension.
When checking I was able to get into the blog without any issues... Take it you were able to get things sorted? Without seeing the problematic behavior one can only guess what the problem was. Could you post what was needed for future readers of this thread?
Other thoughts:
When uploading I highly recommend using FTPS or SFTP with WinSCP, Filezilla, or similar. They do not care what the file extension is and using a secure version of FTP with an ecommerce site is always a good idea.
As for the matching to exclude the blog... Do you really have images for your blog at /wp-images instead of under /blog/wp-content? The less excludes, the simpler it will be to debug and the faster the request can be processed. If you want to exclude both /blog and /blog/someurl (some incoming links might incorrectly specify /blog instead of /blog/) you can change the RewriteCond for the blog to match the EOL or /.
Code:
# Don't rewrite blog directory
RewriteCond %{REQUEST_URI} !^/blog($|/) [NC]
I also noticed you are running multiple domains using nested Document Roots (public_html). This is not best practice and can lead to some negative situations. You may want to look into (or have your hosting provider) remove the nested Document Roots and provide separate physical paths for each domain. See this post for an example.
Re: Ceon URI Mapping v4.x
Quote:
Originally Posted by
lhungil
If you want to exclude all URIs containing the string "x45poty" (case insensitive) use the following:
Code:
# Don't rewrite URI if contains "x45poty" string
RewriteCond %{REQUEST_URI} !x45poty [NC]
When checking I was able to get into the blog without any issues... Take it you were able to get things sorted? Without seeing the problematic behavior one can only guess what the problem was. Could you post what was needed for future readers of this thread?
Other thoughts:
When uploading I highly recommend using FTPS or SFTP with WinSCP, Filezilla, or similar. They do not care what the file extension is and using a secure version of FTP with an ecommerce site is always a good idea.
As for the matching to exclude the blog... Do you really have images for your blog at /wp-images instead of under /blog/wp-content? The less excludes, the simpler it will be to debug and the faster the request can be processed. If you want to exclude both /blog and /blog/someurl (some incoming links might incorrectly specify /blog instead of /blog/) you can change the RewriteCond for the blog to match the EOL or /.
Code:
# Don't rewrite blog directory
RewriteCond %{REQUEST_URI} !^/blog($|/) [NC]
I also noticed you are running multiple domains using nested Document Roots (public_html). This is not best practice and can lead to some negative situations. You may want to look into (or have your hosting provider) remove the nested Document Roots and provide separate physical paths for each domain. See
this post for an example.
Hi.
Thanks for the advice.
The blog seems to run on and off, it's more the /competitions and /community that isn't working.
wp-images is for a different program altogether, not for WordPress.
James
