There are two main ways in which to redirect the browser using JavaScript, both of which look at the location of the window object. These are the location.href property and location.replace function.
location.href
The following example will cause the page to redirect to another page, keeping the browser history. This might seem like a minor point, but if you redirect a user to another page they will be able to click back, which will mean that they are redirected again.
<script type="text/javascript">
window.location.href="http://www.talkincode.com/";
</script>
location.replace
This works in the same way as location.href, but in this case the redirection will occur and no history will be kept in the browser. This means that if a user visits the page with this code on they will instead see a different page. This means that the user can’t click on the back button and view the page that redirected them. Here is an example of its usage.
<script type="text/javascript">
window.location.replace("http://www.talkincode.com/");
</script>
You can also add this to a link by doing the following, although the user wouldn’t be able to get back to the page that redirected them.
<a href="javascript:window.location.replace('http://www.talkincode.com/')" title="Talk In Code">Talk In Code</a>
It should be noted here that you will probably want to avoid doing this sort of redirect unless you really have to. For example, if you relied on a JavaScript redirect in an important part of a form process and the user has JavaScript turned off then the process is quite likely to break. The ideal situation is to use server side scripts and redirect rules to force the browser to redirect in a more robust manner. Also, in terms of SEO using a JavaScript redirect is pointless as search engine spiders will probably not understand them.
I recently talked about adding code to blogs and comments to WordPress and making sure that certain characters are encoded properly. So to simplify things I thought I would create a little set of regular expressions that takes a sample of code and convert it into a Wordress friendly format. It consists of the following function, which takes the value of a text area called tochange and runs some regular expression replace functions on it. I have kept the expressions as simple as possible so they are quite easy to understand. The g argument for each expression means that the replace will be done for all of the text.
<script type="text/javascript">
function changeIt(){
var text = document.getElementById('tochange').value;
text = text.replace(/&/g,'&');
text = text.replace(/"/g,'"');
text = text.replace(/'/g,''');
text = text.replace(/</g,'<');
text = text.replace(/>/g,'>');
text = text.replace(/^\s+/mg,' ');
document.getElementById('changed').value = text;
document.getElementById('preTag').innerHTML = text;
}
</script>
The only one which might cause an issue is the last one with the expression ^\s+. This simply matches for 1 or more white space characters at the beginning of a line. The m argument means that the ^ symbol will be used to mean the start of a line. You can test this function with the following HTML tags.
<textarea id="tochange" cols="50" rows="10"></textarea>
<input type="submit" onclick="changeIt()" />
<textarea id="changed" cols="50" rows="10"></textarea>
<pre id="preTag"></pre>
The first textarea is what you want to alter, the second is the altered text and the pre tag displays what the altered text will look like in your browser.
The following shell command uses the find function to find all files in or below the current directory that have the extension php. It then passes each file found onto a sed command which then replaces all <? with the longer <?php version.
find . -name '*.php' -exec sed -ie 's#<?#<?php#' {} \;
The -name argument in find will look at the base of the file name, that is, the file without any directory path. The -exec command is used to pass each file found onto another command, in this case sed is used.
Recent Comments