I have a .htaccess file which changes something.html to something/ with trailing slash and no extension.
I have been having problems adding a new site, this is due to a confliction with said .htaccess file so I've had to remove the .htaccess to make registering a new site work which obviously isn't ideal.
Is there a work around to this problem like adding the .htaccess file after the initial adding of the site?
Hi Rob,
So the problem is that PageLime likes to work with HTML pages, not just directory index pages. In fact, we try to guess your index page (index.php,index.html) if you don't provide one, and this is probably what's causing the issue.
So - here's what you can do to fix this: You can disable the .htaccess rules based on an IP. PageLime comes from a unique IP address, and using the condition:
RewriteCond %{REMOTE_ADDR} ^###\.###\.###\.###
I'm not an expert in .htaccess and URL rewritting, but a few simple Google searches for something like: "htaccess exclude IP" should do the trick.
This way, PageLime will be excluded from the rule and gets a chance to do its magic.
Hope that helps!
Best,
Emil
Hi Emil,
I have been searching for ages for a fix, and left a few queries on forums etc but is quite a specific thing to do. There are lots of guides for permission based rules which allow one (or multiple) IPs and exclude others, but scarcely the other way round. I have tried the following:
----------------
#Remove HTML extension
RewriteCond %{REMOTE_ADDR} ^174\.129\.6\.222
RewriteCond %{DOCUMENT_ROOT}/$1.html -f
RewriteRule ^(.+)/$ /$1.html [QSA,L]
#Stop it looping
RewriteCond %{REMOTE_ADDR} ^174\.129\.6\.222
RewriteCond %{ENV:REDIRECT_STATUS} ^$
RewriteRule ^(.+)\.html$ /$1 [R=301,L]
And the same as above with the addition of a "!" in front of ^174\.129\.6\.222 which is supposed to exclude a given IP from a rule ...
----------------
To be honest, I don't really know what I'm doing and the complexity of mod_rewrite doesn't help matters much!
I will persevere and hopefully someone will come to my rescue, this is a problem I foresee a lot of designers coming across as the vast amount of HTML / PHP websites out there nowadays are removing extensions for usability.
If it is all FTP based, surely the CMS could read the original file regardless of what the URL is ... is there no possible fix at your end?
Thanks guys!
Ok, so I have a so-so fix which isn't ideal but I will step through the process of my .htaccess file as best as I can for anyone else who might be facing the same problem:
# 404 ERROR
ErrorDocument 404 http://domain.com/404.html
Options +FollowSymLinks
RewriteEngine On
# REMOVES "www."
RewriteCond %{HTTP_HOST} ^www\.(.+)$ [NC]
RewriteRule ^(.*)$ http://%1%{REQUEST_URI} [R=301,L]
# REDIRECTS domain.html TO domain/ ~ REMOVED SO CMS CAN FIND ORIGINAL FILE
# RewriteCond %{THE_REQUEST} ^[A-Z]{3,9}\ /index\.html\ HTTP/
# RewriteRule ^index\.html$ http://domain.com/ [R=301,L]
# ADDS TRAILING SLASH "/" to URL
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_URI} !(.*)/$
RewriteRule ^(.+)$ /$1/ [L,R=301]
# REWRITE something.html TO SHOW AS something/ CMS CAN FIND ORIGINAL FILE
RewriteCond %{DOCUMENT_ROOT}/$1.html -f
RewriteRule ^(.+)/$ /$1.html [QSA,L]
# REWRITE something.php TO SHOW AS something/ CMS CAN FIND ORIGINAL FILE
RewriteCond %{DOCUMENT_ROOT}/$1.php -f
RewriteRule ^(.+)/$ /$1.php [QSA,L]
# REDIRECTS something.html TO something/ ~ REMOVED SO CMS CAN FIND ORIGINAL FILE
# RewriteCond %{ENV:REDIRECT_STATUS} ^$
# RewriteRule ^(.+)\.html$ /$1 [R=301,L]
# RewriteCond %{ENV:REDIRECT_STATUS} ^$
# RewriteRule ^(.+)\.php$ /$1 [R=301,L]
So, in short to allow Pagelime access to original files but still use pretty URLs your .htaccess file would look something like this:
# Redirect 404 Error
ErrorDocument 404 http://domain.com/404.html
Options +FollowSymLinks
RewriteEngine On
# Remove www
RewriteCond %{HTTP_HOST} ^www\.(.+)$ [NC]
RewriteRule ^(.*)$ http://%1%{REQUEST_URI} [R=301,L]
# Add trailing slash
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_URI} !(.*)/$
RewriteRule ^(.+)$ /$1/ [L,R=301]
# View .html and .php files without extension
RewriteCond %{DOCUMENT_ROOT}/$1.html -f
RewriteRule ^(.+)/$ /$1.html [QSA,L]
RewriteCond %{DOCUMENT_ROOT}/$1.php -f
RewriteRule ^(.+)/$ /$1.php [QSA,L]
You must include a <base href="http://domain.com/" /> below your <title></title> tags in the head to make the CSS work for pretty URLs, don't ask me why!
This isn't an ideal situation as it leads to duplicate content, being accessed from something/ and something.html which could harm SEO ranking ... however it's a quick fix until I can figure out how to exlude an IP from a given mod_rewrite statement.
Hope this makes sense, pass on to anyone who needs it!
Rob :)
You must log in to post.
