We Keep Coding

Website links load but do not redirect to different page Wordpress, IE8

I've almost completed a website built in Wordpress, using a theme called WP Foocamp. My problem is that whilst the site looks great in most modern browsers, mobiles etc I am still struggling with IE8. I don't have an in-depth knowledge of javascript or PHP which makes this really difficult, but if I could find out where the problem is then I could research where to fix it.
Any help would be MASSIVELY appreciated.
The url is ipswichhalfmarathon.com

I recently did a complete answer on the subject of IE pre 9. Go and check it out here

How to make a form-filling google chrome extension

I was wondering if anyone could provide me with some links to some tutorials or explain (with some example code), how I would go about making a simple google chrome extension (or in any programming language or browser if that is impossible), how I would make an extension that can visit a specific site, fill a login form on that site, click some links and then do the same sort of thing on the linked to site.
Thanks

Personally, I would not use a chrome extension, but maybe a perl script. There is an extension called WWW::Mechanize that is designed exactly to do this kind of stuff.
You can find plenty of tutorials and examples, just google it.
Edit in 2021: the above recommendation has become a bit outdated since 2013. For a more up-to-date take, I'd still recommend a scriptable headless browser instead of an extension for most automation tasks, but probably not WWW:Mechanize. There are good lists of options, such as this one.

Why web browsers don't have jQuery built in? [duplicate]

This question already has answers here:
Why is jQuery not integrated within the browser
(7 answers)
Closed 4 years ago.
It seems like a good idea to me. or add the additional features to Javascript itself?

Because it's just one library of many. It may be popular but it's far from being the only choice. And it would also cause it to freeze at a particular version and make improvements much slower.
Plus there is little advantage anyway. It's fairly small and you can set it to be cachable indefinably by the brower so it will only be downloaded once anyway - if you have a new version it will have a new filename, so there is no harm in making it never expire.

I think this question should be a bigger discussion, but these answers are all bogus.
This is also 2 years later of course.
"it's just one library of many" - include the top 11 then.
"couldn't agree on common standard" - Kind of making jQuery a standard of it's own at this point.
"updated more often than browsers" or "make improvements slower" - So the browser won't have jQuery-1.9.x until next browser update, just don't put it in your project yet.
"Cache anyway" - Sure, it's still a transfer that doesn't have to happen, and there are a lot of people that haven't done a lot of surfing on their new device that you still want your site fast for and so on.
The thing is it is totally doable and would be better for the internet load; by how much is debatable. I could really see chrome at least replacing any net transfer to their CDN with a local copy, but I'm sure there is some legal, security or net neutrality issues with that. Just like I'm sure the main reason has something more to do with such matters and not these lame technical excuses that are obviously not thought through.
This could benefit other libraries too if developers could rely on the speed and availability of a complete library of tools like dojo, and not have to pick and choose just to cut weight. And also as most libraries have adopted the AMD or requireJS approach to package their projects, I believe there is a good argument for the enabling the browser to at least be informed of it's dependencies.

jQuery exists just because they (browser makers) couldn't agree on common standard.

You can consider jQuery to be a JavaScript plug-in. And browsers do not ship with plug-ins, otherwise the purpose of plug-ins would be irrelevant.

Plugins get updated more often than browsers - within a week the browser version of jQuery would be out of date :)

There's also the issue of versioning. Certain sites and extensions of jQuery require a certain version of jQuery. Right now it's up to the application to decide which version to use.

Probably because browsers are hard to update. Some freature of JQuery may eventually make their way into javascript, and I believe some of it has just recently. (well the idea's anyways) It takes years to add a feature to something like javascript, where the JQuery library can just release a new version.
There is actually a firebug or firefox plug in that allows you to inject JQuery into the page.. but thats just a development tool

Adding jQuery [type] functionality to the browser's in-built JS implementation (or making it a 1st-class plug-in) would overcome one basic problem:
As many have said, jQuery is a JS library - meaning, in case the penny didn't drop - that it is written in JS and has to be interpreted at run-time.
Embedding it would mean that it could be written in native code for the OS, making it much more performant.

Adding WYSIWYG to a site that is not your own?

This website that I use has a WYSIWYG that ONLY works in IE. And I refuse to use IE or to tell my non-tech team to use IE.
I was wondering if there is a user script or browser plugin that would enable anyone to inject a WYSIWYG such as CKeditor.com onto any site textarea?
Edit: I would also be willing to work on it myself if anyone wants to help or give advice. We could then post it on userscripts or something ...

Since you don't have access to the code, anything you do will be a hack.
With that in mind, I would start looking at Greasemonkey. It is a firefox plugin that allows you to inject javascript code into any web page on your machine. Its a long road, but that's probably your first step.
One word of warning however: While I share in your dislike of IE, it sounds like your hatred has grown to the point where it is being counterproductive. Seriously consider whether what you are about to do is worth the effort.

You can use this extension in Firefox as long as you get at least a textarea in that CMS: https://addons.mozilla.org/en-US/firefox/addon/6147/

Would a Firefox extension that displays websites as if they were in IE do the trick?

I like Stargazer712's answer (look into Greasemonkey), but there is another option.
Suck it up and use IE for just this site.
Hey, I hate IE6 and 7 as much as the next Web developer. I advise non-techies to stay away from it, and to use Firefox or Chrome. My answer isn't meant to be flip or funny.
Sometimes, if you need to get the job done, you choose the best tool for the job (even if you don't like using the tool) to get the work done in the most efficient manner possible. In this case, it sounds like using IE to access this particular Web site takes care of the problem without a single line of code or documentation written on your part.
The alternative is spending hours finding (and testing -- because you won't be the only user) an alternative...or worse, spending hours or days developing (and, again, testing) your own code to fix the problem that, at the end of the day, is really only caused by your strong dislike of the one software application that works.

Recommendations for simple AJAX? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 9 years ago.
Improve this question
I want to get smarter in AJAX, but not sure which way to go. I have done some DHTML programming back in the day - like 8 years ago!, before it was called AJAX. I used emacs and hand-coded all the javascript, debugged via "Alert".
At this point I think there are frameworks out there that make things nicer and easier, but which ones? Where to start? Recommendations?
is jQuery indispensable? Just nice to have?
What about project SACK?
Firebug?
any other free libraries or frameworks you recommend? or disrecommend?
for a very simple project I found tons of pitfalls with FF vs IE compat. Without getting into a religious debate about who is right and who is wrong, what are some tips for navigating that minefield to produce apps that work and look mostly similar on any browser. One guy had a tip: insert * {padding:0; margin:0;} at the top of his .css stack, because FF and IE both have different default padding and margins for elements like UL OL etc. Is there a list of tips like this? Guidance?
I don't have a Mac and really don't wanna incur the test cost of IE, FF, Opera, Safari, Chrome, across all the myriad versions and platforms. Hints? Is there a 80% solution here? Like if I test on FF & IE, can I guess it will work on the others?
tips on tutorial sites, getting started? There's tons of info out there, which are the good places to go. In particular, because DHTML was around 10 yrs ago, my google searches are turning up some really stale information.
Debugging and development tools? I found an xpath just-in-time evaluator on the web on zvon.org. It was good but not as flexible as i wanted it to be. This is something I think would be invaluable. xsl and xpath have got to be the most opaque languages I have ever used. When I started with regex, there were just-in-time regex tools available, like Expresso, etc. Those were invaluable for developing and learning regex in the early days. Last night I spent waaaay too long fiddling with an xpath expression, and I'm wondering if there are similar JIT tools for xpath. And what about debugging and developing Javascript itself?
Mostly I am interested in the client-side aspects. I am not so much interested in integrated client+server approaches like ASP.NET AJAX, for now. If you told me about a client AJAX framework or development tool that worked only with Ruby, I wouldn't be interested.
Thanks!
EDIT: why did I get voted down? Is this a bad question to ask? It seemed perfectly reasonable to me? is it impolite?

it's usually even easier than the ajax() function above. mostly i just do ....
$('#mydiv').load('http://getsomehtml.php?op=loadmeup');
once in awhile add a callback
document.body.style.cursor = "wait";
$('#mydiv').load('http://getsomehtml.php?op=loadmeup', function() {
document.body.style.cursor = "default";
});
and I agree jQuery is indispensable. or something like it .. using raw javascript is a minefield of problems with all the browsers these days. I like visualjquery.com as a handy reference (but I wish Remy would update it to 1.3.2)
And I could not do my job w/o Firebug so that's totally required.
I run xampplite on a PC for testing. And I use NotePad++ or Eclipse PDT 2.0 for editing (esp for server-side PHP) and CVS and i'm good to go...
The way I do multi-browser testing is via a VM. I use Sun's VirtualBox and an XP virtual machine with all the browsers loaded up. I regularly use FF3 and IE7, so my VM has in it IE6, FF2, Chrome, Opera, and Safari. I sometimes use a Ubuntu 8.10 image but not really all that often.
For Regex get a copy of RegexBuddy - easily worth the $40

Personally I think jQuery is indispensable. There are a lot of browser differences with XMLHttpRequest. jQuery simplifies all that. Here is an example:
$.ajax({
url: 'document.xml',
type: 'GET',
dataType: 'xml',
timeout: 1000,
error: function(){
alert('Error loading XML document');
},
success: function(xml){
// do something with xml
}
});
You can easily change this to return JSON, HTML, etcj.
Also there are wrapper methods for this that greatly reduce the number of parameters like $.load(), $.post() and so on.
In reference to browser differences, I strongly suggest you start with a CSS reset like Yahoo's reset CSS (there are others).
In terms of development, Firefox is the standard, combined with Firebug (and typically YSlow). HttpFox and Web Developer are popular plug-ins too.

jQuery isn't indispensable, but it's very helpful.
never heard about it
I think one js framework is enough. So i recommend jQuery.
CSS reset is not going to fix all compatibility issues, but it can help significantly. For ultimate css reset see Eric Meyer's CSS reset.
Try http://browsershots.org/
I don't have any recommendation here.
For debugging javascript - firebug (firefox extension). You can also want to try fiddler to check what's passed between server and client.

For making Ajax requests, I use http://www.prototypejs.org/
For everything else, I write my own JavaScript. Even if it matter of fading a div, I still prefer to do it my way as a way of learning.
As to getting started, here is my quick tutorial:
new Ajax.Updater(domId, urlToAPage);
Where:
domId = anything on your html page that has an id, as long as it is not an input object.
urlToAPage = could be the page to contact and get the data from.
You can make the request more complex:
new Ajax.Updater(domId, urlToAPage, {method: 'post', parameters: pars} );
You can change method from 'post' to 'get'.
Pars can be anything. Further more, it looks same for post request. So if you want to make a request to a file called hello.php and send a post parameter with two arguments, then place the response into a div called 'hello':
var domId = 'hello';
var urltoPage = 'hello.php';
var pars = 'hello=1&name=hsbsitez';
read more: http://www.prototypejs.org/learn/introduction-to-ajax

I also would highly recomend using JQuery. It makes life so much easier.
One thing I learned about JS though is never to trust that it works. Just because you use JQuery and it works in a few browsers doesnt mean it works in the others.
You have to try it in as many borwsers on as many systems as you can.