Basically duplicated http://www.smoothprint.co.uk at http://www.comitservices.co.uk/ben/ocart, I imported the old database into the new one and edited the php.ini files so they aren't both connected to the same database
However now the SEO friendly links aren't working and i'm not sure how to rectify this. Any ideas?
Make sure you have edited your .htaccess file's RewriteBase value. On your original store, it will have been
RewriteBase /
and for the new store it should be
RewriteBase /ben/ocart/
Although usually just removing the line completely will allow the file to work with both of those stores
Related
I have an url www.example.com/english/magazine-one/offline/download.pdf, where I want to access the download.pdf but shows magazine-one.pdf (the magazine folder name) instead without actually renaming the PDF file.
So I have managed to come up with this in my htaccess
RewriteEngine On
RewriteRule ^(.*)offline/magazine-one.pdf$ $1offline/download.pdf [L]
This allows me to mask the URL and access the pdf directly from magazine-one.pdf. However, when I access download.pdf the url still does not change and point to magazine-one.pdf.
Would be great if someone can throw some ideas in.
I inherited a large WordPress site: I was looking at the Wordfence live logs when I found users not loading a particular PHP page. I investigated and through an FTP client I found the file was where it was supposed to be. I used some network tool (in Chrome, Opera and Firefox) and, again, I found that file was returning a 404.
So, I found in the root of the website a short htaccess file containing this line:
RewriteRule ^wp-content/(.*)\.php$ [R=404,L]
I commented this out and reloaded the website: no error anymore. I must say, the error apparently doesn't cause anything strange to the website. But I would like to eliminate it.
I suppose this rule is meant to avoid someone can make a direct HTTP request to this and any other PHP file in that directory: in this case I suppose this file I'm talking about is called from an include, not directly, because in WordFence what I see is an error coming after a user accesses directly other pages, not this one in particular.
Anyway, I would like to rewrite this rule so that it stays the same as now, except for that php page. The PHP page is in the path of the theme:
wp-content/themes/themeName/core/css/customized.css.php
Is this possible? Any help is appreciated
If you want to exclude that specific php file from the RewriteRule, you can add a negative lookahead to the regex, like so:
RewriteRule ^wp-content/(?!themes/.*/core/css/customized\.css\.php$)(.*)\.php$ [R=404,L]
The url : http://test.something.com/ is the login page of the application. By default it calls a page 'login.cfm'. But it doesnt shows in the url. May be it is defined in the server file as a default page.
What I want is, when i access this url [http://test.something.com/], the url should also show the called page i.e. the url should look like : http://test.something.com/login.cfm everytime.
I dumped the cgi variables and below is the stack for the same. I was wondering whether i have to change the cgi.http_referer or cgi.http_host.
Or do I need to change some file on the server side? I am using Apache.
EDITED:
what you are asking might be a browser dependent issue. In the Browser there is option to trim the URL from the address bar, which might be the case for you.
Please check this link and get it confirmed.
http://www.cnet.com/how-to/how-to-show-the-full-url-in-firefox/
Still if you want to change your application's URL to look something else then you can try "URL rewrite"
You can check this link for URL rewrite.
http://www.iis.net/learn/extensions/url-rewrite-module/user-friendly-url-rule-template
(You forgot to show the cgi scope dump, fyi)
Are you certain that Application.cfc/Application.cfm isn't just showinng the login page? Also look in any header files. That's the likely scenario always showing the login page.
Anyway, you can use .htaccess to do just this but it's not clear whether you want each subdirectory to its index.cfm, or if you want to redirect to the root.
If you want the redirect to the index page of the current directory (/something/ redirects to /something/index.cfm)
RewriteCond %{REQUEST_URI} !\..*$
RewriteRule ^((.*)$) /$1/index.cfm [L,R=301]
If, instead, you want it to redirect to the root folder, that's a pretty simple change
RewriteCond %{REQUEST_URI} !\..*$
RewriteRule ^((.*)$) /index.cfm [L,R=301]
The L in both examples stops processing of rules after that, so if you have other rules in .htaccess, that may be a concern.
The R flag (R=301) is important to cause the URL to visibly change, creating the effect you want.
I'm about ready to pull my hair out on this. Basically, I've changed an old .asp site (that used queries for products) to a .php site (that also uses queries, but for different parameters). Trying to get my htaccess redirects to work. The bottom line is that I need to pull the query strings out at certain times, but not others.
Here is the form of the old URL for a product, product ID in this case being "101":
http://www.example.com/shopping/shopexd.asp?id=101
There were a lot of products, and as my new site does not use queries for products, so I just want to redirect them all to my new home page.
If I use something like this:
RedirectMatch 301 ^/shopping/(.*) http://www.example.com/
Then it leaves the ?=101 at the end, giving me:
http://www.example.com/?=101
I can't use a blanket "get rid of all queries" type of approach because the new site does use them for other things, like order ids or category ids.
You need to use mod_rewrite rule to strip existing query string.
put this code in your DOCUMENT_ROOT/.htaccess file:
RewriteEngine On
RewriteRule ^shopping/ http://www.mysite.com/? [L,NC,R=301]
Here ? in the end is used to strip off any existing query string.
This might seem a bit basic and something that's been asked quite a lot around here, but I have a small .htaccess problem (mod_rewrite).
I'm working on a MVC framework for PHP (like everybody else...) and all traffic goes through index.php which then routes to the required controller and method. All that goes well. The structure is roughly something like this:
application
controllers
models
views
cache
framework
public
assets
img
css
js
index.php
.htaccess
For an URL like myapp.com/css/ I need o load the CSS controller, index function. But for URLs like myapp.com/css/style.css I need to fetch the file from the public/css/directory
I'd hate writing /public/ for each file I want to include, so basically I need to redirect all traffic to /public/ if it's an actual file and keep the normal rewriting rule for all other URLs. I'm planning to use this in production and it would be much easier to let frontend developers do their stuff the way they normally do it and then just copy paste stuff into place instread of going through CSS to modify paths and such.
I came up with this:
RewriteEngine on
RewriteRule ^(img|css|js|assets)/(.*).([a-z]{3})$ public/$1/$2 [L,NC]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php/$1 [L,QSA]
But it has some obvious flaws. I don't mind having to set directories in the first regex, but checking that the path is a file the way I do seems rather unreliable. Using RewriteCond to check that it's a file didn't work for some reason and I think this method can fail for URLs like myapp.com/img/this-is-actually-an-article.aaa Of course, extensiuons can also be longer than 3 characters and I need to check that that's safe as well.
What's the best way to go about this? How do you guys ussually do it? Or is this a wrong approach from the very begining?
The -f isn't working because the requested file is /css/style.css whereas the file on disk is /public/css/style.css.
I see no problem with declaring some predefined namespaces that you can't use in your application (like img, css, js, assets).
Eventually I think you will move to a situation where plugins for your framework can no longer decide where their resources are, the framework should decide it for them and possibly even load it for them. This resolves all your current issues as no plugin code will ever need to know anything about URLs. Regardless of your rewriting strategy I think this is something to aspire to.