Argumentum

I got this all wrong. This is not a theme problem.

The function the_posts_navigation in my theme is actually doing nothing. To confirm that, I removed the function from the theme file, and the posts navigation on my website is still working with no problems.

So my website is actually using the function the_posts_navigation from public_html/wp-includes/link-template.php, which is a core file.

WP-PageNavi instructions says:

In your theme, you need to find calls to next_posts_link() and previous_posts_link() and replace them.

But, in my website, the only file with these calls is link-template.php (https://core.trac.wordpress.org/browser/tags/4.4.2/src/wp-includes/link-template.php).

What should I do to use WP-PageNavi in my site, then?

Thanks in advance.

Just a quick update… It might be a coincidence only (I don’t remember seeing anything related to it in the changelog), but I published two posts after updating Jetpack, and Publicize worked on Facebook with no problems.

I also filed a bug on Facebook for Developers, as Jeremy suggested, but they gave it a “Won’t Fix” status.

Thanks, Jeremy. Activating the WP.me shortlinks did make Publicize use the long permalinks.

I just published a new post using Publicize on both Twitter and Facebook. What I got is this:

Twitter: correct title, correct image
Facebook: correct title, wrong image (no image at all, not even the fallback appears on the preview)

Now, the weird thing. When, five minutes later, I try to share the same post on Facebook again, manually, I get no image and no title. I get nothing, as the debug shows: http://goo.gl/eNlA5y. This is especially weird because Publicize at least was able to get the correct title; I get nothing, and I’m trying to share five minutes after Publicize did.

After I press “Fetch new scrape information” a couple times more, I finally get the right results.

Five minutes should be enough time for Facebook to get all the meta tags. I’m actually under the impression that, if I didn’t press “Fetch new scrape information” a couple more times, I would keep getting nothing even a few hours later.

Anyway, something is probably very wrong on my side. Thanks for your support.

Thanks, Jeremy. I’ll try to investigate if there’s something wrong on my side.

Things are very weird here. I did another experiment. It probably will not clarify things further (at least not right now), but I’ll post it anyway.

I published a post on WordPress and I used Publicize for Twitter only (I unchecked the Facebook box; these are the only two social networks I use). As always, the tweet was posted with no problems at all, with the correct featured image.

I waited a few minutes and then I went to share the post manually on Facebook. I was surprised – Facebook could not pull the featured image and not even the post title! The preview was showing the fallback image and a “Page not found” as the title. In fact, that is happening right now, and it’s been like 20 minutes since the post was actually published on the site.

Now, an important note (I think): that happens if I try to share the post with the shortlink used by Publicize (http://www.example.com/?p=X, X being the post ID). When I try to share the post with the long permalink, I can get the correct featured image and post title.

This is very weird. It’s like Facebook is having some problems to pull the right information when the shortlink is used.

To summarise:

1. When I use Publicize with Twitter and Facebook (shortlink is used in both cases):
Twitter: correct title, correct image
Facebook: correct title, wrong image (fallback)

2. When I use Publicize with Twitter only and, many minutes later, share the post manually on Facebook (shortlink is used in both cases):
Twitter: correct title, correct image
Facebook: wrong title (“Page not found”), wrong image (fallback)

3. When I use Publicize with Twitter only and, few minutes later, share the post manually on Facebook (long permalink is used on Facebook):
Twitter: correct title, correct image
Facebook: correct title, wrong image (no image at all, not even the fallback appears on the preview)

4. When I use Publicize with Twitter only and, a few more minutes later, share the post manually on Facebook (long permalink is used on Facebook):
Twitter: correct title, correct image
Facebook: correct title, correct image

Is it possible to set up Publicize to use the long permalink instead of the shortlink?

I would like to make some additional tests using the long permalink in Publicize.

I’ve successfully edited the file \inc\template-tags.php to show the right background images in the post navigation — just had to change the first parameter of get_adjacent_post from false to true.

Now I just need to know how I can use this in a child theme, since the file is in a subfolder. I have tried to simply copy the original directory hierarchy, but the file was not loaded. I suppose only the files in the root folder of the theme are automatically overrode by its respective child versions, then.

I see \inc\template-tags.php is loaded in the parent functions.php with require get_template_directory() . '/inc/template-tags.php';, but I have no idea how to override this require in a child theme.

Any help will be appreciated. Thanks again!

Thanks for the prompt answer.

Ops, I just realised this has already been discussed here: https://wordpress.org/support/topic/settings-localisation-options

Sorry.