Page 1 of 1

jQuery + XAJAX = Bad?

Posted: Mon Jul 07, 2008 8:37 pm
by nutkenz
I hope someone here has experience with (X)AJAX and jQuery. My problem is that I cannot seem to update a form field anymore after I've triggered a XAJAX function (which also updates the form field using jQuery).
Firebug output
Firebug output
xajax.jpg (58.81 KiB) Viewed 1846 times
In the FireBug output you can't see it, but the first update to 'x' works fine and the one after an ajax call does not... Can anyone please help me?

Re: jQuery + XAJAX = Bad?

Posted: Mon Jul 07, 2008 9:03 pm
by pickle
We're going to need to see your jQuery code, including your AJAX call so we can see what the situation is.

Re: jQuery + XAJAX = Bad?

Posted: Tue Jul 08, 2008 3:57 am
by nutkenz
They're all in the picture. It's not a regular AJAX call btw, but it uses the XAJAX PHP Library. I don't think the function called is relevant, just the response. Correct me if I'm wrong.

Re: jQuery + XAJAX = Bad?

Posted: Tue Jul 08, 2008 3:57 am
by nutkenz
They're all in the picture. It's not a regular AJAX call btw, but it uses the XAJAX PHP Library. I don't think the function called is relevant, just the response.

Re: jQuery + XAJAX = Bad?

Posted: Tue Jul 08, 2008 9:45 am
by pickle
PHP can't run client-side. You HAVE to have a javascript AJAX call if you're getting content from the server without reloading the page.

The JS is very relevant - how else are we supposed to know what the situation is?

Re: jQuery + XAJAX = Bad?

Posted: Tue Jul 08, 2008 10:08 am
by nutkenz
I'm aware of the fact that PHP can't be run client side... I'm using XAJAX however, which allows AJAX without the need for writing JavaScript.

For some strange reason, after I restarted FireFox and FireBug, the code did work as expected.

Re: jQuery + XAJAX = Bad?

Posted: Tue Jul 08, 2008 2:48 pm
by Ollie Saunders
Oh I thought XAJAX was another on of those silly variations on an abbreviation that meant essentially the same thing as the original but turns out it's a PHP library :-O
For some strange reason, after I restarted FireFox and FireBug, the code did work as expected.
Ahh yeah I've experience that. Pretty cool. Glad you got it fixed though.