Could you try to style the spinner, like we do for the Twenty Thirteen page:
http://plugins.trac.ww.wp.xz.cn/browser/jetpack/tags/2.5/modules/infinite-scroll/themes/twentythirteen.css
That might explain why we don’t see the spinner on your site yet.
Let me know if it helps.
I added in your styling and was able to determine something.
I have wrapper as false since I am using <ul id="infinitescroller">
So that means that your scroller is not supposed to put in a <div> </div> wrapper, which is operating correctly.
BUT..
Unfortunately, it’s also not putting in an <li>...</li>wrapper around the javascript and <span class=”infinite-loader”..</span> it’s just inserting itself at the end of an
<li></li>
element like this:
<ul is="infinitescroll">
<li> item one</li>
<li> item two </li>
<script id"infinite-handle">...</script>
<div id="infinite-handle">...</div>
</ul>
Which means that it won’t show as you can’t just put elements at an end of a <ul><li></li></ul> list without an <li>...</li> around it.
Do you know of a solution?
Here is my function code as it currently stands:
function clear_news_infinite_scroll_init() {
add_theme_support( 'infinite-scroll', array(
'container' => 'infinitescroll',
'footer' => false,
'footer_widgets' => false,
'wrapper' => false,
'posts_per_page' => 6,
'render' => 'my_child_infinite_scroll_render',
) );
}
add_action( 'after_setup_theme', 'clear_news_infinite_scroll_init' );
function my_child_infinite_scroll_render() {
while ( have_posts() ) {
the_post();
?>
<li class="col-md-4 col-sm-6">
<?php get_template_part( 'templates/parts/content', get_post_format() ); ?>
</li>
<?php
} }
Thanks!
OK. I solved it. Not sure if it’s HTML grammatically correct, but I used CSS to put it in the correct place:
To the .infinite-loader CSS I added:
position:fixed;
bottom:30px;
left:20px;
Now it’s permanently (while showing) in the lower left corner of the browser.
On a side note.. it looks like I broke the forum somehow!
Yes, you used <li> tags without the code buttons – that does it! I fixed it for you :).
Great! Thanks for fixing that!
