Ajaxify – Support v2.0

Friday, December 12th, 2008 | Author: MaX

Any Comments, bugs , feature request about Ajaxify v2.0, please post it here.

For advanced paid support or special requests. Contact me through the contact form.

Known issues:

Stop ajaxify excuting based on onStart function return.
Fix false warning “warning: target “#Ajaxifytemp” couldn`t be found”
Fix back button on first ajaxify call.

Feature requests:

Loading Images via ajaxify.
Encode non safe characters in url’s before sending the request.
Change the page title based on the loaded content.

For advanced paid support or special requests. Contact me through the contact form.

__________________________________________________________________________

How to make ajaxify compatible with jquery v1.3.0 and higher?.

Open jquery.ajaxify.js with your preferred editor.
Go to line 58. You will see var ver = jQuery.fn.jquery.split(‘.’);

Mark it, and go down until you reach line 62. So the full text will be:

var ver = jQuery.fn.jquery.split('.');
if(ver[0] < 1 || ver[1] < 2 || ver[2] < 6){
jQuery.ajaxifylog('Error: Your jQuery version is old. Version 1.2.6 or newer is required.');
return false;
}

Comment it or delete it. its your choice.

Category: jQuery

You can follow any responses to this entry through the RSS 2.0 feed. Responses are currently closed, but you can trackback from your own site.

415 Responses to “Ajaxify – Support v2.0”

Pages: « 1 … 10 11 12 13 14 [15] 16 17 18 19 20 … 21 » Show All

MaX
March 31st, 2009 at 11:59 PM

JoeReynolds
No, the server output is wrong. why is the #ajaxContent div is inside pagination. and rightAd inside rightAdcode.

<div id="Pagination"><% Html.RenderPartial("IndexPartial"); %></div>
<div id="rightAdCode">Google ad javascript here</div>
<div id="topAdCode">Google ad javascript here</div>

JoeReynolds
April 1st, 2009 at 3:15 AM
Thanks Max, but I must still be missing something. Sorry.

I have this in server output:
```
<div id="Pagination"><% Html.RenderPartial("IndexPartial"); %></div>
<div id="rightAdCode">Google ad javascript here</div>
<div id="topAdCode">Google ad javascript here</div>
```
My ajaxify code is this:
```
$(document).ready(function() {
    $('.ajaxify').livequery(function() {
        $(this).ajaxify({
            loading_img: '/SiteImages/ajax-loader1.gif',
            loading_target: '#AjaxContent',
            loadHash: 'attr:rel',
			tagToload:{ '#Pagination':'#AjaxContent',
						'#rightAdCode':'#rightAd',
						'#topAdCode':'#topAd'}
        });
         window.scrollTo(0, 0);
        });
});
```
I run the page and then click on an ajaxified link. The first debug error is #AjaxContent not found (for the loading image set for AjaxContent). The next error is #Pagination not found, etc for each div.

I know I’m missing something simple, but how can the loading image be placed in #AjaxContent if there is no DIV with an id of AjaxContent when the loading image is called.

Does a div for AjaxContent need to be somewhere in the server output if it is going to be called? If so, where? Ditto for rightAd and topAd.

However, I do note that the history is updated in the url when I click on an ajaxified link.

MaX
April 2nd, 2009 at 2:29 AM
Pagination, rightAdCode and topAdCode should be in ur server output and AjaxContent, rightAd and topAd are in your page.

JoeReynolds
April 2nd, 2009 at 3:45 AM
I’m afraid I don’t see the distinction between “server output” and “page.”

Isn’t all the code in the page code?

Anway it seems my problem is in where the divs are placed. For example, I have a div of

<div id="Pagination"><% Html.RenderPartial("IndexPartial"); %></div>

I cant’t figure out where the div of:
is placed in my page code.

I’ve looked at your demo and tried all kinds of combinations, but no matter what I do I receive the error of

#Pagination couldn’t be found.

JoeReynolds
April 2nd, 2009 at 3:48 AM
In the prior post the div I don’t know where to place is

JoeReynolds
April 2nd, 2009 at 3:48 AM
Well, let me try again

JoeReynolds
April 2nd, 2009 at 3:50 AM
Code didn’t work, HTML didn’t work, straight entry didn’t work, this is a try using javascript:

JoeReynolds
April 2nd, 2009 at 3:50 AM
using blockquote:

JoeReynolds
April 2nd, 2009 at 3:51 AM
I give up.

MaX
April 2nd, 2009 at 5:04 PM
Could you provide me a test page?

JoeReynolds
April 2nd, 2009 at 7:52 PM
Here’s the test page:

http://www.gooutdoors.com/Fishing/Images/1

Tony
April 3rd, 2009 at 5:59 AM
I posted this before but forgot to use the code tags. Here it is again: I’ve got it working perfectly. However, when I try to *also* use a jquery accordion plugin (this one: http://www.i-marco.nl/weblog/archive/2007/11/25/jquery_accordion_menu ), it no longer works. For example:

The following code works fine:
```
							<a href="#" rel="nofollow">Heading One</a>

								<a href="test1.html?action=tagtoload" rel="nofollow">Test 1</a>
								<a href="test2.html?action=tagtoload" rel="nofollow">Test 2</a>

							<a href="#" rel="nofollow">Heading 2</a>

								<a href="test3.html?action=tagtoload" rel="nofollow">Test 3</a>
								<a href="test4.html?action=tagtoload" rel="nofollow">Test 4</a>
```
However, if I replace the very FIRST UL with this:
So that the accordion plugin works, the links will instead load the actual pages (test1.html, etc) into the browser, rather than dynamically loading just the content into the target div.

Any ideas what the conflict is and how to resolve it?

Thanks.

Tony
April 3rd, 2009 at 6:04 AM

Ok, I used the HTML tag instead of the CODE tag. Here’s the code again:

<ul>
<li><a href="#" rel="nofollow">Heading One</a>
<ul>
	<li><a href="test1.html?action=tagtoload" rel="nofollow">Test 1</a></li>
	<li><a href="test2.html?action=tagtoload" rel="nofollow">Test 2</a></li>
</ul>
</li>
<li><a href="#" rel="nofollow">Heading 2</a>
<ul>
	<li><a href="test3.html?action=tagtoload" rel="nofollow">Test 3</a></li>
	<li><a href="test4.html?action=tagtoload" rel="nofollow">Test 4</a></li>
</ul>
</li>
</ul>

Ok, that’s the code that’s working with ajaxify. It’s loading into the target div on index.html.

Here’s the part where it falls apart. If the very first UL is this:
<ul id="menu1" class="menu">
Then the actual pages load in full (test1.html, etc.)

Asinox
April 3rd, 2009 at 11:19 PM
Well, is not working for me, i dont, i have my links with the target=”#container”, i have jquery reference fine, the reference to ajaxify is fine too, and im trying to using the simple example

$(‘.ajaxify’).ajaxify();

the links open in new window.

Thanks u for y plugin.

Asinox
April 3rd, 2009 at 11:21 PM
Well, is not working for me, i dont, i have my links with the target=”#container”, i have jquery reference fine, the reference to ajaxify is fine too, and im trying to using the simple example

$(’.ajaxify’).ajaxify();

the links open in new window.

Thanks u for y plugin.

Asinox
April 3rd, 2009 at 11:22 PM
my link’s have the reference to the class .ajaxify too

bobsoap
April 4th, 2009 at 1:40 AM
RE: THE IE CRAP/CLEARTYPE ISSUE

…but there is a lot of issues about IE rendering. its not just something that happens with ajaxify. as I remember it could be related to the windows clear type option. I would like to see you screenshots if you don’t mind.

Thanks for the offer – here’s a screenshot, this is how it looks in IE 7:

bobsoap
April 4th, 2009 at 1:41 AM
^^ hmm it didn’t take my image, here’s the link:
http://img14.imageshack.us/img14/1173/ajaxifyweatherinie.jpg

MaX
April 4th, 2009 at 10:50 AM
JoeReynolds,
Yor html page has a lot of mistakes. please validate your html page so we can move to the next step.

Tony
The href attr can’t be just # mark. change it to a valid attr or don’t set it at all so you can use the “link” option

Asinox
wrap it with $(document).ready();

bobsoap
Thank you bob. its realy a nasty one. I will see if it can be fixed on my side.

Tony
April 4th, 2009 at 5:52 PM

The href attr can’t be just # mark. change it to a valid attr or don’t set it at all so you can use the “link” option

Hmmm…I removed the href altogether, and it still doesn’t work. The only way I can get it to work is to remove the class=”menu”. I can leave the id=”menu” in there and ajaxify still works, so it’s obviously something in the accordion menu’s javascript. (The menu class triggers the menu.js script, so it’s got to be something in there that’s conflicting.) I know it’s not your problem, but if there’s anything in menu.js that jumps out at you, here it is in its entirety:

function initMenus() {
	$('ul.menu ul').hide();
	$.each($('ul.menu'), function(){
		$('ul.expand').show();
	});
	/*$.each($('ul.menu'), function(){
		$('#' + this.id + '.expandfirst ul:first').show();
	});*/
	$('ul.menu li a').click(
		function() {
			var checkElement = $(this).next();
			var parent = this.parentNode.parentNode.id;

			if($('#' + parent).hasClass('noaccordion')) {
				$(this).next().slideToggle('normal');
				return false;
			}
			if((checkElement.is('ul')) && (checkElement.is(':visible'))) {
				if($('#' + parent).hasClass('collapsible')) {
					$('#' + parent + ' ul:visible').slideUp('normal');
				}
				return false;
			}
			if((checkElement.is('ul')) && (!checkElement.is(':visible'))) {
				$('#' + parent + ' ul:visible').slideUp('normal');
				checkElement.slideDown('normal');
				return false;
			}
		}
	);
}
$(document).ready(function() {initMenus();});

Pages: « 1 … 10 11 12 13 14 [15] 16 17 18 19 20 … 21 » Show All

Any Comments, bugs , feature request about Ajaxify v2.0, please post it here.

For advanced paid support or special requests. Contact me through the contact form.

Known issues:

Feature requests:

For advanced paid support or special requests. Contact me through the contact form.

How to make ajaxify compatible with jquery v1.3.0 and higher?.

415 Responses to “Ajaxify – Support v2.0”

Polls

Recent Posts

Categories

Recent Comments

Tag Cloud