Friday, December 12th, 2008 | Author: MaX
When I released ajaxify v1.0 I didn’t expect that huge demand for the plugin. I thought its just a crap of code. but then, I remembered how it was difficult to start programming for me. So I decided to complete what I have started. I have created a special homepage for the plugin. Added new cool features. fixed v1.0 bugs. After hours of hard work. v2.0 released today. I hope you like it. And as always, any help, bug report, suggestion, confession…. don’t be shy.
(Please, dont post questions here about ajaxify. post it in the appropriate support page )
MaX,
Loading ...Category: jQuery
December 12th, 2008 at 4:06 AM
MaX, thank you very much! It really great. For me it is the most interesting plugin for jQuery what I have ever seen.
December 22nd, 2008 at 11:58 AM
Ajaxify: Instantly Ajax Static Websites…
Ajaxify is a jQuery plugin that converts all links in a web page into Ajax load-submit requests.
So, with a single line, you can turn a static website into an Ajaxed one.
It has support for:
History & bookmarking
Partial load from the output
Four…
December 22nd, 2008 at 1:34 PM
Good plugin !
Where is example.php in v2.0?
December 23rd, 2008 at 2:30 PM
What do you mean by “example.php”
if you are referring to an examples included in the packege, there is not in v2.0. I have created a full of example website. why do you need it anyway.
December 23rd, 2008 at 5:34 PM
Hi MaX,
Very nice. Could you please add the phpfiles to the download? Somehow I cannot figure out how to work with the example.php file as hotmonitor points out too.
December 24th, 2008 at 3:21 PM
[...] container where you want the content to be loaded in. Have a look at the demo page and read about version 2.0 on author’s blog. Spread this post [...]
December 24th, 2008 at 5:38 PM
how to use Ajaxify? I need for demo.php and example.php in download package? Is it free or not?
December 24th, 2008 at 6:53 PM
I’m sorry, I cant just post my website source code. You can still download v1 packege and see the example.php code here. Its the same for v2.
December 24th, 2008 at 8:50 PM
yes V1.0 works perfect.
December 24th, 2008 at 9:08 PM
do you know now how you can handle it from the server side? you can use the same concept for v2.
December 25th, 2008 at 7:32 AM
yes. concept are the same. I see
January 6th, 2009 at 9:52 PM
Nice job i develop somthing like your stuff but ussing the tittle atrr in the a tag for the target thing, you know… for xhtml strict compliance!
January 14th, 2009 at 2:10 AM
Will it work with Jquery 1.2.6?
January 14th, 2009 at 2:48 AM
it needs jQuery 1.2.6. And it doesn’t work for older versions
January 14th, 2009 at 2:59 AM
Thanks for the quick response! I’m looking at trying to implement ajaxify the following way.
A table with server side data: Example
edit | delete | name | address | city | state |etc.
I want to be able to click the edit btn and then have either an IFrame or Container beneath the above table open a form to edit the information.
Is ajaxify the right solution for this?
January 14th, 2009 at 3:05 AM
To clarify my first question the JQuery site shows that ajaxify works with v1.0.x of JQuery
January 14th, 2009 at 10:10 PM
I want to be able to click the edit btn and then have either an IFrame or Container beneath the above table open a form to edit the information.
Is ajaxify the right solution for this?
Actually, this is one of the main purposes of creating ajaxify. you can implement it on the traditional table or a modern one like flexigrid without any problems.
To clarify my first question the JQuery site shows that ajaxify works with v1.0.x of JQuery
You don’t have too. I know about that. it was a mistake. I couldn’t correct it because of jquery site limitation.
January 15th, 2009 at 1:51 AM
It works great! I do have a problem. I have a very large table of data 2000+ records. I have used the tablesorter and pagintion plug-ins.
The problem I have noticed is that from the first iteration of records i.e. page 1/xx Ajixify works fine. When I move to page 2/xx Ajaxify no longer works it opens another page instead.
Any suggestions?
January 15th, 2009 at 2:42 AM
I don’t know how your pagination plugin works, but most probably you need live query. check its example on the demo page.
Try to post your question in the support page next time.
January 15th, 2009 at 11:45 AM
Dear max,
Your plug in v2 is very cool. But I found an issue: History & Bookmarking. In your example, when I didn’t click the Link 1 yet, the target #sub_container is empty. When I clicked the Link 1, it displayed “This is page 1. Click on link 2 now.”, then I click Back button of the browse. It didn’t work. I clicked on the Link 2, and clicked the Back button, then, it worked.
That is a small issue but the people will make a question: “Is the plug in perfect?”.
Thank you for your plug in. It’s very useful for me but I’ll be perfect if there isnot the issue I tell you.
Many thanks.
January 15th, 2009 at 8:27 PM
Hi HTDUNG,
This is normally. Since there is no ajax request before you hit “Link 1″. The back button will not work. I know that this is should not happen. I will try in the next version to solve this in somehow.
There is something important you should know that there is nothing perfect in the world. specially when it comes to programming. The programmer tries to solve and eliminate bugs as much as possible. But will not be 100% perfect. In the same time you can consider the current version of ajaxify is stable enough to be used in a live environment.
January 17th, 2009 at 6:27 PM
Dear Max,
My last message tell you about “leak memory”, that’s my bad. I forgot to set the attribute `target` in anchor tags, and set up $.AjaxifyDefault.target . So, my computer was slow down when I clicked more links.
Your PlugIn is very very cool.
January 18th, 2009 at 9:12 AM
Dear Max,
Today I got an issue. When I load the Content using ajax, my document height is very high to fit the content height. When I load an other content shorter than old one, the document height didn’t fit to the new content height. It happens to IE (i’m using IE6). The document height in FF2, FF3 is fit. Show me how to fix IE document height when using ajax, pls.
I’m a newbie in Ajax. Thanks very much.
January 21st, 2009 at 2:47 AM
This is wasn’t the problem. the problem was as I have described it before in the support page.
Its a css problem. change your “height” to “min-height”.
February 6th, 2009 at 5:06 AM
Dear Max,
I’ve check my css file, but I can’t find down how to fix the height problem. I havenot set the height of td, div, table tags. I try to add style=”min-height: 300px;” into the td tag which contained the content div. There is no change. I got the issue when using IE6. I havenot check it with IE7. The FF2, FF3 is OK. When we make a website, we cannot force the visitors use only FF, right? Please help me.
This is my website for our form classmates http://www.trungvuongsaigon.com.
Thanks for your great jobs.
February 6th, 2009 at 11:34 PM
Sorry HTDUNG, but here we are disscussing ajaxify problems. not CSS problems. if you are unable to solve them ask a CSS expert. but really I have no time to investegate your problem. sorry again.
February 10th, 2009 at 6:11 PM
For HTDUNG have you tried this hack? http://www.dustindiaz.com/min-height-fast-hack/
By the way, I’m trying to load a remote page (test.php) and it has javascript functions that embed an swf using
swf plugin.
The problem is that it only loads html content and doesn’t execute any javascript function.
Any ideas?
Thanks
February 20th, 2009 at 8:02 PM
i think Ajaxify is a great plugin for Jquery. I have a question, how can I use ajaxify in order to get the information of other page when the page is loaded? Thanks
February 22nd, 2009 at 12:23 AM
Hi! Loving this plugin! Some thoughts:
I am building a web app that is all about progressive enhancement offering 100% fallback if no javascript is available – that means all of the links to be ajaxified are regex-replaced first before ajaxify gets a hold of them.
A huge part of this solution is the ability to use history. All is fine and good (given that only one container is used for all ajax loads), unless they reload the page….
If a page is reloaded, and the hash (page) they were on is located in a link that is NOT within the target container (like in a menu on the left, whereas the target is a container on the right), then all is well, ajaxify will analyze all the links that have been ajaxified, and if one matches the hash, then it will load that link.
If for instance though, I had links within the target container, that lead to further updates within that container, the hash will not match any links in the left menu (in this example) – therefore on page-reload, ajaxify will not match the hash with any links, and will be stuck on the default page.
A quick hack last night around line 87 added a ‘else if’ statement that says ‘if this ajaxify round doesn’t match the hash to any links, then just load the hash as a link into the container’.
else if (document.location.hash.replace(/^#/, '') != ''){ var reloaded = jQuery.extend({},jQuery.AjaxifyDefaults, options); thehash = document.location.hash.replace(/^#/, ''); reloaded.hash = thehash; reloaded.link = thehash; reloaded.loadHash = thehash; //jQuery(this).ajaxifyAnalyse(reloaded); jQuery.ajaxifyLoad(reloaded); jQuery.ajaxifyHash(reloaded); jQuery.AjaxifyFirstLoad = false; }VERY quick and dirty given that it only works with attr:href as the target (or if hash is a valid url) AND doesn’t yet perform any regex testing to make sure it’s a good link (no rules).
The biggest problem however is that it runs on every ajaxify… there may be multiple ajaxify references in a page with different options and different selectors… So this will try to match the hash on the first ajaxify, if it fails it will load the hash as a link before the other instances of ajaxify have a change to test the hash against the link.
The side effect to this is that if the second, third etc instance of ajaxify ends up matching the link while the first one is loading the link from the hash, it will load the link twice (asyncronous…) before the page is done loading.
This is a multi-faceted issue:
Any thoughts on how to follow the unmatched hash only after ALL the instances of ajaxify have run their course?
A quick-fix would be to stop it from link-hash matching and JUST load the hash (if it matched the rules) but that somehow seams like a cheat, especially if not all the ajaxify links have attr:href hash values.
Would you be interested in adding this alternate behaviour with rules (like if hash has the same current base-domain, etc, then) to your core application? I have to do something like it anyway, so I would love to contribute my thoughts, though not a heroic javascript programmer either ie: my “final” code might look like alpha to you
My final thought is this: I think that this plugin has a tremendous amount of potential, especially for people who are adhering to the rules of progressive enhancement. I would like to see project discussions on a threaded system like google groups, which could facilitate and foster open discussion and problem solving.
Thanks again for the great plugin!
-Zachariah
February 23rd, 2009 at 12:55 AM
To continue on the last thought:
Checking for a hash match on page reload would have to be an option (yes/no) and the valid hash pattern (like ‘this domain, or a regular expression) would also have to be an option.. The following assumes that both have been set (however the code won’t be in this example.
What I did was move the else if code up to before the
return this.each(function() {– so it runs before ajaxify starts to loop through selectors. if the option was set that the user wanted this behaviour, that should be no problem. That way it runs before ajaxify loops through anything, but the code does not return so it continues on and lets ajaxify loop through it’s selectors.
To avoid the ‘load twice’ issue if ajaxify subsequently loads the same link in it’s link-hash comparision, I added another variable
which gets set to false if the hash gets loaded on a page reload. Then, in the function ajaxifyLoad, this replaces the first couple of lines:
jQuery.ajaxifyLoad = function(current) { if (jQuery.AjaxifyNotReload == false && current.link == reloaded.link) {//check if on first reload there was a valid hash match and that this ajaxified link is that link //do nothing } else { //if this is not a first load that has already been matched, keep loadingto finish up, this is the new else if statement at the top before the each loop
jQuery.fn.ajaxify = function(options) { if(!jQuery(this).size()){ jQuery.ajaxifylog('Error: No matched element/s for your ajaxify selector " '+jQuery(this).selector+' ".'); return false; } //added by Zachariah else if (document.location.hash.replace(/^#/, '') != '' && jQuery.AjaxifyFirstLoad && jQuery.AjaxifyHasNotRun){ var reloaded = jQuery.extend({},jQuery.AjaxifyDefaults, options); thehash = document.location.hash.replace(/^#/, ''); reloaded.hash = thehash; reloaded.link = thehash; reloaded.loadHash = thehash; //jQuery(this).ajaxifyAnalyse(reloaded); jQuery.ajaxifyLoad(reloaded); jQuery.ajaxifyHash(reloaded); jQuery.AjaxifyFirstLoad = false; jQuery.AjaxifyNotReload == false; } //end added by Zachariah return this.each(function() {(please note that it still doesn’t check for an option to turn it on or off nor does it check for/against a matching pattern like ‘this domain’ or a regex expression
-Zachariah
February 24th, 2009 at 2:50 AM
Diseño web Valencia
Have you read the docs.
Zach
I really can’t understand why are you doing this? why do u need to use regex? what is the problem with my integration of the history plugin ? can you provide an example of your html links and structure?
February 24th, 2009 at 7:30 AM
indeed. I can see how my lack of explanation could be confusing.
The website is based of off joomla which provides an novel method for pulling two types of data with the same link structure only with minor differences.
loading a page with
“yourdomain.com/index.php?args”
will produce a whole page loaded with html, head, body, modules, components, etc
loading the same link with the simple addition of a ’2′ at the end of index produces a page with just the component (the main content minus the modules)
‘yourdomain.com/index2.php?args’
although this will still produce html, head and body, just no modules and other things
a final touch of adding ‘&raw’ to the end of the ?args will produce ONLY the component code, no layout, html, head, body…
So to truly ajaxify a link (load only the part that I need) without rewriting joomla, and also maintaining full functionality with javascript turned off, all I need do is take the existing link, replace index with index2 and add a ‘&raw’ to the end. If I do it in a regex replace then I only have to write the code once and the change is only active when it needs to be anyway (when javascript is enabled).
As far as the history integration, i’m not saying anything is wrong persay, only that if:
a link is clicked within a container that has already had content replaced within it by ajaxify (by a previous navigation) …ie that link wasn’t there before we navigated once with an ajax action…. and the page is ‘reloaded’, not back or forward, but reloaded, then the original page will load (without the link in question within the markup as it was loaded dynamically), ajaxify will analyze the links, and WON’T match the hash (since that link isn’t currently in the markup), therefore will just sit at the original page..
So if someone navigates 3, 4 or 5 levels deep into a series of ajaxified links within the target container (using livequery of course), and something happens to there connection and have to reload the page, or they bookmark that page, the current matching pattern will leave them lost, sitting 3,4 or 5 levels back from where they thought they would end up.
In my solution (I’m sure one of many), given the option is turned on, it will follow the link in the hash (created by attr:href) directly on ‘first load’ -> so any time the page is reloaded or someone bookmarks and comes back to the page. I also did finish writing a rule option to pass a validation regex in to make sure the hash was a real, fully qualified link… In my case, it verifed that the link was on my domain with index2.php?some known args, otherwise it continued on matching ajaxified links
so if in the bookmarked link someone had
yourdomain.com/something#http://yourdomain/index2.php?args
it will follow that link on reload however if it had:
yourdomain.com/something#link1 or
yourdomain.com/something#http://someotherdomain/cupcakes.php
it would instead try the normal matching analysis that ajaxify normally does.
I hope that’s clearer – currently the modified system is working flawlessly in my implementation no matter where the links are and where you reload/bookmark.
-Zachariah
February 26th, 2009 at 12:03 AM
Okay, its much clearer now.
For regex. There is a plan to modify the onStart event in the next version to accept returning the “options” object. and then you can use it like this:
. . onStart:function(o){ o.link.replace('index.php','index2.php'); o.link = o.link+'&raw'; // you can add it on params option too. return o; } . .If you are interested I will try to make a quick hack for you. although I’m sure you have figured it out already.
). deviant art uses the same method too. But I can’t add it to ajaxify as a feature because it will not fit for everybody.
And for history. yes the main problem is ajaxify doesn’t support multi levels. Your method worked for you because you have only one target. and you can ignore the other options too. I actually used this method in one of my projects (ajaxify had no name in that time
Last week I was thinking writing an article about integrating ajaxify with popular CMS’s. Your thoughts were very useful. It will defiantly help me write it much faster now as my knowledge still weak in joomla.
February 26th, 2009 at 1:40 AM
That option looks really very useful!
Anything I can do to help. Would love to brainstorm on a flexible means to add multi-level to this awesome plugin.
I see what you mean about my hack not working for everybody… The multi-level part only works if
1) there is only one target
2)the link href is gathered through the attr:href method in Ajaxify…
3)the href is a real server-resolvable address. If it were multilevel with anything else, like link1, link2 etc, it of course would break.
Joomla Ajax has been such a mish-mosh of random peoples poorly documented half solutions and bad javascript libraries. I have some super simple ideas for using Ajaxify and some extra plugin code to completely ajax-enable the whole CMS without hardcoding in any of the core code. My only fear is the massive volume of support requests I might get if I let it loose as open source
February 26th, 2009 at 7:39 AM
Well, right now I’m out of ideas and i don’t think that the inspiration will come soon.
Sorry guys
When you first wrote that you want to integrate it with joomla I checked joomla website and google for a plugin or extension or whatever that could do the same job but I was surprised. . All I found is for polls or comments. There is nothing complete as you said. I’m really interested in your ideas. If you don’t mind I would like to know what they are. May be we can work together to produce something to serve this CMS. or at least a good tutorial. And about the massive support request, don’t worry, when you get busy just put them in a forum or something and let them fight to the death.
March 31st, 2009 at 3:02 AM
Zachariah,
Not sure if your gonna check this or are subscribed, but I am in the exact same scenario as you (nationalcitypd.com). I am using a single target, using the attr:href method, and all hrefs are real addresses.
I’m having the same issue as you, of bookmarks with “multi level” links. I suggested to Max that in this case ajaxify could simply resolve the url since it has it, and he pointed me here.
I tried using your code, and it’s not working. I know the last thing you wanted was support requests, but I am curious if you or Max have any idea why your code wouldn’t work. I could share what I’ve done, or you can email me (codyjohnwilliams@gmail.com).
I know only enough javascript to hack around a little bit. I fixed the ampersands and implemented the code in the places you described. It works like regular old ajaxify though, its not loading hash urls that are not in the original page (“multi level” links).
Eeerrr, so close to perfection!
March 31st, 2009 at 3:46 AM
Hi Cody, I’ll email you directly, and if there are any significant lessons learned we can post them back on this thread.
-Zachariah
April 22nd, 2009 at 9:56 AM
This is a great plugin! Thank you very much!!
Greetings from Hungary!
June 23rd, 2009 at 3:29 PM
Why It isn’t work with jQuery 1.3.x? Are your looking for It?
Thks for your great work!
July 7th, 2009 at 10:39 AM
Hi,
Thanks for this great plug-in. I am only dealing with a small(?) problem.
I have a asp.net website (Umbraco), with a top navigation bar.
The hierarchy is something like this:
> Home
-> About us
-> Development
-> Projects
-> Contact
When I open the site, the ‘Home’ is automatically loaded (the default page). But when I then click on one of the other links on the menu, it opens in a new window, after that, all other navigation click on the newly opened window behaves as expected with AJAX, except the home link. When I click on the newly opened window, it opens in another new window.
When I watched the source code, the class and target are set correctly. Any idea?
O yes, the main.master is like this:
The contentplaceholder will get id “Content”. That’s what I put in the target label (I tried also container, but doesn’t work properly either).
Hope you can help me out of this?
Many thanks in advance.
July 7th, 2009 at 10:40 AM
Hi,
Thanks for this great plug-in. I am only dealing with a small(?) problem.
I have a asp.net website (Umbraco), with a top navigation bar.
The hierarchy is something like this:
When I open the site, the ‘Home’ is automatically loaded (the default page). But when I then click on one of the other links on the menu, it opens in a new window, after that, all other navigation click on the newly opened window behaves as expected with AJAX, except the home link. When I click on the newly opened window, it opens in another new window.
When I watched the source code, the class and target are set correctly. Any idea?
O yes, the main.master is like this:
The contentplaceholder will get id “Content”. That’s what I put in the target label (I tried also container, but doesn’t work properly either).
Hope you can help me out of this?
Many thanks in advance.
July 7th, 2009 at 10:53 AM
Hi,
Here a little addition: the behaviour I described, only appears in FireFox.
In IE it seems to work. In Chrome, it opens one of the sub pages on a new tab, after that, it stays on that tab and AJAX doesn’t seems to work at all
July 18th, 2009 at 1:20 PM
Sadly, ajaxify doesn’t seem to work in noConflict-Mode. The “tagToload”-Option is not perfomed after recieving data from an ajax call.
cu
tommy
August 31st, 2009 at 1:04 AM
I thought I wasnt going to like this blog but more I read the more I liked it.
October 22nd, 2009 at 9:48 PM
Here is a question I would like to throw out to the forum.
Question: When ajaxifying a hyperlink, is there a way to override the href? (with a modified version of the clicked link)
Reason: I’d like to maintain backward compatibility with older browsers, so I would like to munge a link on-the-fly to determine who is using javascript.
Example:
$(#menu a).ajaxify({ target:'#some_target', link:'http://some_new_link?ajax=1' });I know this code is incomplete and I need to wrap it in a function or .click(function(event) (I’m still working on that) but I thought I would throw this out there to see if anyone else has solved this issue.
I did see a post from max where he indicated that an onstart could be used in the next version. I tried this but it appears to not be in the current version.
Any advice or help that anyone has is greatly appreciated. TIA.
Marty
October 22nd, 2009 at 11:34 PM
Sorry to reply to my own post.
Arrggg!! It always happens, as soon a I post, I figure it out, and like usual, it’ soooooooo easy. Here is the answer….
$('.selector').livequery(function(){ $(this).ajaxify({ target:'#target', }); });It seems as though ajaxify appends ajax=true to the URI by default. So, all I had to do was to test for ajax in the cgi variable space and that tells me whether or not the page was called via ajaxify. Sweeeeeeet!!!
Max…THE MAN!!!!
December 20th, 2009 at 7:58 AM
Is it possible to call ajaxify from javascript? So instead of clicking on a link, you call a function?
I would like to be able to use a timer and/or keypress to append/refresh data.
(I hope it’s ok posting here for support – comments on the the v2.0 support page have been disabled)
December 21st, 2009 at 5:27 PM
@Alex
Sure, it’s easy. Assuming you have the jquery library and ajaxify correctly installed, you just reference the DOM element from within your function… something like this…
Here is a link to our site where we use ajaxify that is wrapped in a document.ready function….
Drip Irrigation (ajaxify)
View the source code and try the “add to compare” feature. You’ll see ajaxify used as well as some other jquery goodness. Feel free to copy our source code if it will help you.
If you have not used ajaxify before I suggest you get one of Max’s examples working first. Then wrap it in your function.
Best of luck, Ajaxify rocks!
December 21st, 2009 at 5:34 PM
@Marty
Thanks for the help – I figured out that I needed event:false; and then it would work as I had intended.
Nice site – I love the animation, very smooth & stylish.
April 2nd, 2010 at 9:51 AM
I having problems with the Jquery core 1.4.2 and UI 1.8.
If you use the button widget, the form data will execute normaly, like there’s no Ajaxify?
Does anyone know a solution for this?
I tried to submit with a input submit button and the submit event in ajaxify and even with a link to trigger a submit, but both ways do not trigger ajaxify, When changing to core 1.3.2 it works as it should.
Thank Joost
April 2nd, 2010 at 10:14 AM
an extra update:
the problem is not the core 1.4 but the button widget!
with the button widget you can make buttons from an anchor, just by adding class button to it.
if you do so the ajaxify will not work anymore!
June 7th, 2010 at 6:36 PM
Does Ajaxify support loading html snippet’s (say via jQuery load() function) or do you have to have a PHP or other server-side script?
If is does not, I would like to request that as a feature to be added.
Thanks.
August 16th, 2010 at 9:35 PM
Dear Max,
Ajaxify is exactly what I’m looking for, but darn if I can get it to work. I’m new to jQuery but as far as I can tell I’m doing what I’m supposed to:
1) I’m loading all of the .js packages in your distribution ZIP.
2) I’m giving the links a class of “ajaxify” and specifying a valid container, for example:
Still, no matter what I do, when I click on a link it opens in a new window. What am I doing wrong?
Many thanks in advance for any help you can provide!
Mike
September 23rd, 2010 at 3:54 AM
Has anyone gotten this error before….when the page first loads, firebug gives an error:
document.location.hash is undefined
It is on line 83 of the ajaxify.js file:
Anyone have any ideas? I cannot figure out why it is saying that is not defined. I created a stripped down test page and it doesn’t get that error, but it does on my actual page but I can’t find anything different.
Thanks
January 5th, 2011 at 12:48 AM
Hi,
ajaxifying links do work perfect, but i cant get the registration form working?
checked in firebug, i do get a response, but nothing shows up near the form!
$(document).ready(function() { $('.ajaxify').livequery(function(){ $(this).ajaxify(); }); }); $('#regform input').livequery(function(){ $(this).ajaxify({ event:'change', method:'POST', loading_img:'img/sloading.gif', loading_txt:'Working...', link:'backend/registreren.php?action=regsubmit&ajax=true', forms:'input' }); }); $('#form').livequery(function(){ $(this).ajaxify({ event:'submit', link:'backend/registreren.php?action=submit&ajax=true', forms:'#form', target:'#result', loading_target:'#b_demo-', loading_img:'img/sloading.gif', loading_txt:'Working...', method:'POST', animateOut:{'height':'toggle'}, animateIn:{'height':'toggle'}, onSuccess:function(o,data){ if(data=='accepted') $(o.target).html(' Thank you for your registration'); else $(o.target).html(' Your registeration couldn\'t be completed.'); } }); });This is what firbug shows:
response:
The name is already takenThe password must be at least 5 char.Password matchedPlease enter a valid email
$(“[name=submit]“).attr(“disabled”,true);
I am trying it for 2 days now, but nothing (as far as my knowledge goes) helps!
Many thanks for any hints!
January 17th, 2011 at 4:54 PM
Hi i have a problem with noConflict and loadToTarget.
Firebug givnt me en error message ; ( anybody an idea ?
btw really good script if i dont use the noConflict
greez
January 18th, 2011 at 1:00 PM
Hi, maybe i found the problem.
ajaxify.js line 267 -> jQuery.ajaxifyManip(current,jQuery(data).find(current.target));
returns NULL
but …
jQuery.ajaxifyManip(current,jQuery(data));
returns the hole DOM.
in other words “find()” dont work with “noConflict” ??
i never heared about it **confused**
any workarounds ?
greez
March 1st, 2011 at 8:14 PM
Why I can not use animation on my site
March 22nd, 2011 at 7:39 PM
I see that if we used a newer version of JQuery then your plugin will not work see that!
January 10th, 2012 at 2:59 PM
I am trying to use “AJAXIFY” plugin in my ASP.NET . I am unable to add this plugin. The Target page is loading in new tab. Can Please any one help me fast……!!!!
January 23rd, 2012 at 6:20 PM
People,
we still want to use ajaxify (2012).
But its not working on chrome new versions..
We have to update the history.js dependency to its new version..
Anyone have solution for this? If not.. anyone wants to help building a new one?