That's strange. Maybe it's a race condition issue which may vary depending on your computer. I've tried this before for logging click- throughs and it worked fine. What if you try to use $.ajax instead, and set the option 'async' to 'false', so that it waits for the AJAX response before the click- through occurs?
Other than that, I'm out of ideas. On May 29, 11:56 am, Up-Works <mich...@up-works.com> wrote: > On May 29, 2:54 pm, James <james.gp....@gmail.com> wrote: > > > Try putting a "return false;" at the end of your click code so that it > > doesn't go to the next page. See if the AJAX call works. > > (Theoretically, it probably still should not if it didn't before.) > > > I'm not sure what you're saying about the console displaying the text > > in red. Does it also contain any additional messages? > > In Firebug if the line is red, it usually means that the AJAX call did > > fire but something was wrong with the request, such as the page being > > called was not found, or a server-side error occurred on the page. > > If I return false it does call the AJAX .get() but obviously does not > load the url of the href.
