How can I include Jetpack Sharing buttons links within?

Hi, ib.property:

Let me look in to this and get back to you.

To help you, I realized that the entity &nbsp is greatly involved. In fact the problem tends to be solved when deleting the entity &nbsp from the text.

Interesting. Thanks for this tip.

I’ll treat this as a bug and let you know when it’s fixed.

Hi, ib.property:

My team and I have tried to replicate this using the default WP theme (2014). We’re unable to, I’m afraid.

This leads me to believe we’re facing a theme/style issue vs. a PLP issue.

Can you share a link or screenshot with us?

I use twenty fourteen theme too. I have manually deleted all final   to solve the problem, but it was not difficult to recreate the situation adding a final space and then insert   again. Here some example: first example , and turning the next page to find the sharing buttons first example last page . Then second example and turning the next page to find the sharing buttons second example last page.

Now, I don’t know if all the   were there before your plugin installation, maybe yes and then I think your plugin has interpreted the entity, or the empy space, as an additional page.

Hi, ib.property:

This is what I see:

:: https://www.dropbox.com/s/0m6buinvcfvrtlt/Screen%20Shot%202014-07-26%20at%2011.35.20%20AM.png

The buttons and PLP seem to be playing nicely.

Let me know if I’m missing anything.

You have missed the point: without the entity ” &nbsp” the page with the lonely sharing buttons does not exist and and the buttons would appear appear in the end of the previous page .

In poor words it would normally appear like this page which I have deleted the final &nbsp to solve the problem.

Sharing buttons must be placed in the bottom of the written part, not in a solitary empty page, in fact what readers should share, an empty last page like the example you send me or a page with pictures and words belonging to the article’s body?

Trust me, the problem is to persuade your plugin to not push sharing buttons to a next absurd empty page. I solved the problem manually get back and remove any entity &nbsp I find in the bottom of the post.

Better examples of perfect paginated pages ( and thus with the intervention of your plugin) are the following : first example and second example. Have you got it?

In short, the JetPack sharing buttons are appearing on a single, empty page after all the content pages?

Yes! JetPack sharing buttons must not appear on a single, empty page after all the content ( and images) pages. A reader can be irritated by turning the page just to see a series of sharing buttons which, at that point, are useless. A Pinterest user have no more images to pin with an empty page, and the same with a Facebook or whatever.

Perhaps, and without perhaps, it was my fault for all the entities &nbsp in the bottom of my posts. Nevertheless one should teach your plugin ( which is so indispensable to me) to get around, ignore all the final &nbsp and stay with the words and images group.

One may argue that a reader would easily bypassed the problem clicking the All command provided by Page link Plus. But my articles can sometimes be so heavy that one can prefer to turn pages next by next. I install your plugin with readers and, almost all, search bots and crawlers in mind.

As for me, I will keep to hold tight to Page link Plus and, if there is no way to solve the problem, I will continue to manually solve deleting the final &nbsp.

P.S: what about to include an autopagination after a x number of images also?

Hi, ib.property:

Yes, I think you’ve provided the best explanation for it. Namely, if you have a single space at the end of your post — whether one enters ” ” value in the HTML editor or enters a carriage return after all content in the visual editor — WP and PLP may interpret this as extra content.

I’ll enter this as a minor bug.

Until the fix is available, removing any final spaces/empty lines in either the visual or HTML editor should address this.

Finally, we’ll certainly take your autopagination suggestion under advisement.

Thanks again for your feedback.