Need help? Check out our Support site, then

Disable Infinite Scroll with Custom CSS?

  1. Just tested again. It's off. I'm not sure whether I want it on or off, haven't decided yet. But I'll leave it off for a day or two just to prove it. :)

  2. And I can confirm that on my test blog using Twenty Ten with no widgets in the footer, the "infinite scroll" toggle still appears in my Settings Dashboard.

  3. Test Twenty Eleven then.

  4. justjennifer, that has been updated. So right now it should be working as mentioned earlier: if you are using an infinite scroll enabled theme with footer widgets, you'll see an option to turn off infinite scroll in Settings → Reading. Otherwise, you shouldn't see the option.

  5. Must have been an errant setting somewhere. Now in both Twenty Eleven and Twenty Ten, both with no footer widgets, the toggle does not appear nor am I seeing infinite scrolling on either.

    Too Much Coffee?

  6. We posted at the same time! See ^^

  7. @designsimply. Urgh. So if I understand correctly, I've just lost the option to turn it off on my Twenty Ten blog unless I add a footer widget. Is that correct?

    And if so, could you please comment on the technical aspect of my question in Specifically, the part about load times for third-world readers.

  8. That is the intention, yes. The option is currently for blogs that are using footer widgets.

    For the other thread, I saw that and I'm working on researching it as I wanted to make sure to post a correct answer. My sentiment is the same as yours (based on what I know), which is to say that I dont' think infinite scroll adds too much overhead for someone reading through posts because, after you start scrolling, new posts are only loaded when you get to the bottom of the list. I'll check up on it and I'll let ya know what I find out.

  9. It does overload the user's RAM after awhile though. That was my experience on Tumblr when I was following 100 blogs or so. I had to disable Infinite Scroll, as my computer would lock up and then the browser would crash.

  10. @designsimply. That's brilliant. Thanks. Correct answers are always better than quick ones. :)

    By the way, without any footers, the checkbox doesn't show up in my Reading settings anymore, but since I had turned it off earlier today, I'm still not on infinite scrolling. So I'm probably the only Twenty Ten blog in existence with no footer and no infinite scrolling. Makes me feel important.

    As a programmer myself, I hate hidden fields with hidden data -- that's one of the risks of arbitrarily hiding a checkbox. Is there a reason to hide it? Seems kind of silly to me....

  11. @raincoaster, I guess the same thing would happen if you clicked on the previous/next links over and over really fast?

  12. @jongleason, ya could be looking at a cached view or you were checking *just* before the change went through for you.

  13. Seems like the RAM overload would only be a problem if you used a lot of images (I don't) or if the user just kept scrolling down....

  14. I think the philosophy is to made decisions, not options. It's a very real, very interesting issue in programming. We want to add features and make updates. That gets harder to do the more features you add and the bigger you get. Finding an elegant solution is worth doing, and of course not everyone may agree on the end implementation. It's challenging and interesting imo.

    If you're interested in the ideas behind that philosophy, check out Neat stuff. :)

  15. Thanks for that. We deal with a lot of the same issues. Giving the users options adds complexity to code, which adds the potential for bugs, which makes unhappy users. And on the other hand telling the users what they want isn't necessarily a good plan. :)

    I think you are making a mistake on this one, though. You already have the complexity of an option -- you have to, because of the footers question. So now, you've created the added complexity of removing that option in some cases. And you haven't done it right, because I just checked a non-cached view on another computer. :)

    Here's a thought for you, though. Absolutely NO ONE who has footers wants infinite scrolling. NADA. You won't find anyone who has footers and has thought about it who wants it. Either they don't want footers, or they don't want scrolling. The two do not co-exist. It's actually silly to even give THEM the option.

    Those of us who don't have footers are the ones who would benefit from the option. If you are going to give it to anyone, you should give it to us. And since I'm such a nice guy as to point out this flaw in the design decision you've made, I hope you'll leave the little bug that I've mentioned here intact until I get a solid answer on my question about impact on 3rd world load times. :)

    Seriously, thanks for your help on this, and all the work you do.

  16. Blast. You're (partially) right. :) Infinite scroll is not showing up on your blog, but the option for it is gone from your Settings → Reading page. I suspect some kind of cache issue, perhaps it's server side. Invariably, digging into it may "fix" it for you, so I'll leave it alone in your case. I did test the option itself though, and it's working as intended on my test blog. I think you just skirted the fix!

    The option was added because of the footer issue, but do keep in mind that not everyone uses widgets or footers or blogs even in the same way, and it's also not set in stone. So I wouldn't say mistake, I'd say an attempt to make a decision instead of an option. But then again, I'm the unendingly positive person in some ways (and particularly stubborn in others). I like our users here at, and I think it's actually a differentiating factor amongst blogging sites, and so I'd like it to play out positively in the end. I'm biased, I know. :)

    So, as is always the case, it's a learning process. Hey, like I said, it's an interesting challenge to make decisions about such things. Too many options is not good, and it's not necessarily just about this one particular feature, but really, they all add up. Anyway, we'll continue to improve and work on it and balance innovation and work hard to make a truly excellent blogging experience.

  17. Thanks again. It's good to know I dodged a WP bullet, er, I mean, sad to know I missed a WP "fix". I'm pretty sure I can figure out how to get the feature turned on if I want to (and I probably will), so it's all good right now.

  18. I shouldn't have quoted that... my mistake. :)

    It's not a bullet!

  19. Whatever you say! :)

  20. Made decisions, not options.

    is the new "black." Everyone has glommed onto that as if it is some sort of holy grail, and just like with every other polar thing, no one bothers to see all the stuff in between the two extremes.

    The problem is, one size never fits all, and the way infinite scrolling is, and probably the way it will stay, is forcing pegs of all shapes into a square hole.

    Those people that have image heavy posts and has set their site to only show 2 or 3 posts so their sites didn't load like a digital tree sloth will now have 7 coming up with each load. There is no way to change that and from one comment Matt made, 7 seems to be his designated magic number.

    For photographers and artist that for their own reasons want to show only one post per page, they are now out of luck. You can have any number you want as long as it's 7.

    This is a major change to the way things operate here, and major changes like this should not be forced onto people. There should be choice.

    The only reason that themes with footer widgets can turn off infinite scrolling I suspect is that the devs couldn't figure out a way to bring back the footer widgets without disabling IS. If they had been able to figure out a way, then there would be no way to turn off infinite scrolling on themes with footer widgets.

    Any customer can have a car painted any color that he wants so long as it is black. -- Henry Ford

  21. It sounds like you're very upset. :(

    I can find out more about the 7 number if you'd like?

  22. If I were designing it, I wouldn't be using an arbitrary 7 number, I'd be using the setting that users have entered for posts on a page, to reflect the different types of blogs. FWIW.

  23. I never make assumptions if I can help it. I am, also, not perfect. I'll see what I can find out.

  24. @designsimply, I've received so many emails about this from people I've helped in the past, and from people I have either directly or indirectly helped in the forums, and for the majority of them, they have worked tirelessly getting everything just the way they want it and then along comes infinite scrolling. These "edge cases" as Matt puts it are real people with pride in their sites, and I can't help but sympathize with what they are going through, and yes, I can't help but be upset with this forced change.

    For me personally, I don't care anymore.

  25. It should be said, that no one knows the final form this is all going to take, and I've been trying to tell those that have contacted me that, but right now they are all left in limbo not knowing how radically their site and design is going to change. The one thing is, it is going to change, and for some that change is not going to be acceptable. Those pesky "edge cases."

  26. On decisions, not options:

    Ultimately these choices end up being technical ones, choices that the average end user has no interest in. It's our duty as developers to make smart design decisions and avoid putting the weight of technical choices on our end users.

    Do you think that infinite scrolling is a technical issue that the average end user has no interest in? It affects the entire homepage and how it is read. It is also a drastic change to what we had...

    I love blogging on wordpress and you guys do great work. But this whole thing--the way this was implemented and some of the staff responses to the initial surge of negative feedback--has made me just a little disappointed.

  27. @listlessink,


  28. @TSP, I haven't contact you, but I feel like the people that have - in limbo. I am terrified that I am going to wake up some morning and have my site looking like that. I do have a theme with footers so am safe for now, but I agree that the only reason those themes are safe is that they didn't know what to do with them. They might be working around the clock for all we know to try and get a way around that.

    I love blogging on WordPress, but I care about what my site looks like. I don't want every post I ever wrote showing up on the front page. There is a reason that I have an archive list - so people can look at older posts if they want to.

    I really don't know if I should just jump ship and move my blog before they figure out how to get it working with footers and wait and see what happens.

  29. My suggestion would be to look into options right now, but wait for the final form of this thing to see if it is something you can live with. Sadly, there aren't any real alternatives as far as blogging platforms out there that give you what does short of self-hosting. Self-hosting is easier than it used to be with the automatic upgrades on wordpress core, plugins and themes, but it still requires more work on your part.

    In other words, don't start packing yet, but I would probably go ahead and get the boxes. You can always return the boxes if you don't need them.

  30. listlessink, I'm sorry you feel disappointed. I'm working hard to help everyone with their CSS.

Topic Closed

This topic has been closed to new replies.

About this Topic