-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WordPress plugin not loading more than to page 2 #53
Comments
I'll be rewriting the plugin this week or next as it's using a very old version of infinite-scroll. I'll make sure its tested on the original etc. |
Cool, thanks for the quick reply :) |
Could you post a link to a live example we could look at? It would be really helpful! |
It's on my own server at the moment. You can look at it here: http://1-2-3.dyndns.org/ As you can see I'm using jquery.cycle plugin. I've tried disabling it, but infinite scroll still don't load further than page 2. Here's the loop.php: http://pastebin.com/Civ3n8xS |
Accidentally closed it... |
I think you need to use the pathParse feature. It says there's no more pages to get because it's trying to go to 'http://1-3-3.dyndns.org/page/2/'. Could you set |
I think I've turned debugging on now. I'm using the WordPress plugin, så I can't change it in WP-Admin. I changed the debug setting in wp_infinite_scroll.php. If I understand correctly, is it the actual numbers in "1-2-3.dyndns.org" that makes the plugin misunderstand the paging? |
Thanks for that! You need to use the
|
Thank you for your help. I am sorry, but I have no idea on how to use the pathParse option. I can see in the debug that the url is "split" in the wrong place. But I don't know what to write for the path parse to return the correct array. I tried to look at the infinite scroll web site, as well as google, but I couldn't find any description on how to use it. |
FYI, I don't know if the current WP has support for You just need to return the array above. Try adding this to your options.
|
Thanks. That's what I tried. It seems to return the same array as before. I can wait for @Beaver6813 to cover it :) In the meantime I will try to fix it. Cheers! |
At the moment the plugin doesn't do much more than insert and initiate infinite-scroll on the wordpress site. Seeing as its a plugin I'll just use wordpress's "current page" variable to feed it directly to the javascript, save the faffing with pathParse. The aim of infinite-scroll is to be as flexible and extensible as possible; the aim of the wp plugin is to work as easily and with as minimal configuration as possible. |
Hello guys, I'm sorry if I'm hijacking this thread, but I'm at the verge of pulling my hair out and I think my issue is related to OP's issue. |
I don't think we have the same problem. My problem was that infinite scroll misinterpreted my url (1-2-3.dyndns.org) as a page number. I think you need to set some kind of javascript in the callback function of Infinte-scroll. So it will reset the cufon font replacement for the next page that loads. If you can't get that to work you might want to try to import the font using CSS @font-face. |
@adriantomic speaks the truth. Try |
Hey guys, thanks for the replies and sorry for posting my issue in yours. We indeed have a different problem. The below is a callback, right? : Cufon.replace('content'); Should I then use cufon.refresh() instead of the Cufon.replace? Thanks again for the quick reply guys. |
$('#your-selector').infinitescroll({
/// your options
}, function(newElements) {
// this is where you specify your callback function
// 'newElements' refers to all of the new content the plugin loaded
Cufon.refresh();
}); You can also try |
Great plugin, but I have a problem:
When I use the infinite scroll on my WordPress theme, it only loads until page 2. Even though there are more posts on page 3 and 4 etc...
Without the plugin, there are navigation links to all the pages and they work, but infinite scroll seems to ignore the links after page 2.
My theme uses the original Twenty-Ten loop.php.
Thankful for your help.
The text was updated successfully, but these errors were encountered: