Lethalmiko

@nickelaos92, my experience is that it picks the avatar of the article author and ignores all images, including the featured image.

When any story is published, a check of the source code in the browser one second after publishing shows that the OG tags are there and are correct each and every time. I have done this check for many times to verify. So how can the plugin authors claim that “at the time of the auto-publishing your OG tags are not there or incorrect”. Are you saying the OG tags appear magically after the story is already published? What mechanism would make OG tags not be there at publication but get inserted later? Something here is not making sense and it is best to just investigate without assuming that all of us are wrong. We all want this plugin to work and it doesn’t help to be defensive about its flaws.

What do you mean the cron is not set correctly? I copied and pasted what you put on your own website (editing the URL of course) as follows:

curl -s -H “User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64)” https://somewebsite.com/wp-cron.php?doing_wp_cron

Secondly, it doesn’t make sense for the library on the server to fetch Twitter perfectly every time but only fail when it comes to Facebook. That suggests there is something wrong with the way your plugin is set up to do Facebook autposts and as you can see from the posts above, there are several of us who have experienced this. surely this is not just a coincidence.

I run a VPS and I am the admin. I installed it from an image from the VPS provider and I assume they know what they are doing with respect to libraries and all that. I suggest you just do a thorough investigation rather than shifting the blame to hosting providers and server libraries.

• This reply was modified 7 years, 7 months ago by Lethalmiko.

From the log file today:

[Error] [Facebook - Facebook] - -=ERROR=- ERROR: nxs_Error Object ( [errors] => Array ( [http_request_failed] => Array ( [0] => Connection timed out after 45001 milliseconds ) ) )

I have seen the explanation about timeouts from the nextscripts website about the system binary library but it is not satisfactory because why does Twitter work every single time? Why doesn’t it also suffer from timeouts?

https://www.nextscripts.com/support-faq/

The reply to the original question is not satisfactory. I have also experienced the same issue. Autposting to Twitter works perfectly all the time but Facebook is becoming a problem. As of about a few days ago, the featured image is not picked. Instead the avatar of the author is shown. Sometimes it picks another image altogether. The “og:” tags are all set up correctly. Under the Facebook “post type” settings, it is correctly set to “Text Post with ‘attached’ link”. I have even put “Add Open Graph Tags” under Open Graph Tag settings but to no avail. I have the latest version of WordPress and the plugin. Please sort this problem out asap.

The proposed solution for the cron is still not working. Just today another post failed to go through on Facebook. And now there is another problem whereby for Facebook autoposts, it fails to pick up the correct featured image. Instead it picks the avatar of the author.

On “post type”, I had set the system to pick “Text Post with ‘attached’ link” months ago. It used to work but now with this change in the cron settings, it no longer works as before. Other social networks are working fine except facebook. The “og:” tags are all set and showing in the page html source code.

I also added to the functions.php this code

add_filter(‘http_request_timeout’, function(){return 60;});

• This reply was modified 7 years, 7 months ago by Lethalmiko.

OUTPUT AFTER MAKING RECOMMENDED CHANGES

Cron Check Results:
==== Cron was executed 11 times in 15 minutes ===

Your WP Cron is OK

Technical Info:

Array
(
    [cronCheckStartTime] => 1501798022
    [cronChecks] => Array
        (
            [0] => [2017-08-04 00:07:01] - WP Cron called from 144.217.xx.xxx (Mozilla/5.0 (Windows NT 6.1; WOW64))
            [1] => [2017-08-04 00:07:40] - WP Cron called from 144.217.xx.xxx (WordPress/4.8.1; https://somewebsite.com)
            [2] => [2017-08-04 00:09:08] - WP Cron called from 144.217.xx.xxx (WordPress/4.8.1; https://somewebsite.com)
            [3] => [2017-08-04 00:11:42] - WP Cron called from 144.217.xx.xxx (WordPress/4.8.1; https://somewebsite.com)
            [4] => [2017-08-04 00:12:06] - WP Cron called from 144.217.xx.xxx (WordPress/4.8.1; https://somewebsite.com)
            [5] => [2017-08-04 00:13:37] - WP Cron called from 144.217.xx.xxx (WordPress/4.8.1; https://somewebsite.com)
            [6] => [2017-08-04 00:15:19] - WP Cron called from 144.217.xx.xxx (WordPress/4.8.1; https://somewebsite.com)
            [7] => [2017-08-04 00:16:42] - WP Cron called from 144.217.xx.xxx (WordPress/4.8.1; https://somewebsite.com)
            [8] => [2017-08-04 00:18:06] - WP Cron called from 144.217.xx.xxx (WordPress/4.8.1; https://somewebsite.com)
            [9] => [2017-08-04 00:20:22] - WP Cron called from 144.217.xx.xxx (WordPress/4.8.1; https://somewebsite.com)
            [10] => [2017-08-04 00:21:08] - WP Cron called from 144.217.xx.xxx (WordPress/4.8.1; https://somewebsite.com)
        )

    [status] => 1
)

Finally worked though some posts still fail to be autoposted.
—
Cron Check Results:
==== Cron was executed 11 times in 15 minutes ===

Your WP Cron is OK

Technical Info:

Array
(
    [cronCheckStartTime] => 1501750493
    [cronChecks] => Array
        (
            [0] => [2017-08-03 10:54:52] - WP Cron called from 144.217.xx.xxx (WordPress/4.8.1; https://somewebsite.com)
            [1] => [2017-08-03 10:56:11] - WP Cron called from 144.217.xx.xxx (WordPress/4.8.1; https://somewebsite.com)
            [2] => [2017-08-03 10:58:23] - WP Cron called from 144.217.xx.xxx (WordPress/4.8.1; https://somewebsite.com)
            [3] => [2017-08-03 10:59:11] - WP Cron called from 144.217.xx.xxx (WordPress/4.8.1; https://somewebsite.com)
            [4] => [2017-08-03 11:00:41] - WP Cron called from 144.217.xx.xxx (WordPress/4.8.1; https://somewebsite.com)
            [5] => [2017-08-03 11:02:19] - WP Cron called from 144.217.xx.xxx (WordPress/4.8.1; https://somewebsite.com)
            [6] => [2017-08-03 11:03:47] - WP Cron called from 144.217.xx.xxx (WordPress/4.8.1; https://somewebsite.com)
            [7] => [2017-08-03 11:05:11] - WP Cron called from 144.217.xx.xxx (WordPress/4.8.1; https://somewebsite.com)
            [8] => [2017-08-03 11:06:41] - WP Cron called from 144.217.xx.xxx (WordPress/4.8.1; https://somewebsite.com)
            [9] => [2017-08-03 11:08:16] - WP Cron called from 144.217.xx.xxx (WordPress/4.8.1; https://somewebsite.com)
            [10] => [2017-08-03 11:09:42] - WP Cron called from 144.217.xx.xxx (WordPress/4.8.1; https://somewebsite.com)
        )

    [status] => 1
)

Did the test several times but it doesn’t do anything. Even enabled WP Cron but it still does nothing when I click on the reload button. The cURL test works.

“Check is not started yet… Please reload this page in couple minutes.”

Email me I send you a copy of the plugin. Easy Social Share needs caching because it is a rather heavy plugin but I like its great features.

The infinite scroll works on every device I tested it with mobile caching off. There is a big red button at the bottom of any listing of posts labeled “Load More Posts” and it works normally when you click on it. It is also on the page you have linked to. I can send you a screenshot if you email me on admin [at] diggers [dot] news.

The WP Rocket plugin authors say that anything not activated may not work and yet they strongly recommend mobile caching when using certain plugins. To quote from the mobile cache settings page:

“Warning: If you are using one of these plugins, you must activate this option: WP Touch (Free Version), wiziApp, WordPress Mobile Pack, WP-Mobilizer, WP Mobile Edition, Device Theme Switcher, WP Mobile Detect, and Easy Social Share Buttons.”

It seems that the process of caching for mobile somehow interferes with your plugin. Anyhow, maybe the best is to reach out to the WP Rocket plugin authors and tell them about this problem. I really like both plugins and want to keep them but I don’t want to be forced to choose between a fast user experience and speed of loading. I already have enough problems with incompatibility issues with other plugins!!!

UPDATE: When I disabled WP Rocket, the button displayed correctly on mobile. Further investigation revealed that it is the mobile cache setting on WP Rocket which was causing the problem. When I unchecked the Mobile cache setting, the button works fine.

But I now have a new problem because WP Rocket strongly recommends using the Mobile cache if you are using one of these plugins: WP Touch (Free Version), wiziApp, WordPress Mobile Pack, WP-Mobilizer, WP Mobile Edition, Device Theme Switcher, WP Mobile Detect, and Easy Social Share Buttons.

I use Easy Social Share Buttons and after testing the site in tools.pingdom.com, it has become slower after disabling mobile cache. It used to load in 1.6 seconds but is now up to between 2 and 3 seconds.

Is there a way to make your plugin work even when Mobile cache is enabled in WP Rocket?

Thanks for the tip, although what is confusing about your answer is that the button loads properly on desktop and laptop on all pages, including the ones I posted. If as you say the JS does not load on those pages, then why does button render correctly on higher resolutions except on mobile?

On a Galaxy Note 2 mobile phone in Chrome or Opera, the button does not load here: https://diggers.news/local/

Or here: https://diggers.news/2017/04/

But it loads here: https://diggers.news/?s=zambia

On desktop and laptop, the button shows.

I also tried on another (smaller) phone and same thing happened. Let me know what you experience on your mobile phone.

Update: I found the solution which works here:

https://gvectors.com/forum/how-to-and-troubleshooting/reply-button-not-present/#post-983

The nested comments option was not active. I would suggest you put this as part of the solution in your post above.