If it said that the operation timed out, then the only reason was that your server couldn't establish connection with Facebook within 500 milliseconds. The only way to possibly solve that is to increase cURL Timeout (ms) option. Try 1000 ms.
Thank you for your help, i set it as 2000 and i see now that different error (403 forbidden error)If it said that the operation timed out, then the only reason was that your server couldn't establish connection with Facebook within 500 milliseconds. The only way to possibly solve that is to increase cURL Timeout (ms) option. Try 1000 ms.
XenForo_Exception: DEBUG: cURL (facebook): The requested URL returned error: 403 Forbidden - library/EndlessHorizon/SocialShare/Listener.php:35
Generated By: Unknown Account, A moment ago
This usually happen with Facebook only. Since 1.4.0, if you haven't filled Facebook App ID and Secret in Admin CP > Options > Facebook Integration, the add-on will use FQL (kinda obsolete) . It has a rate limit, but it's not very well documented. But, once you've hit the limit somehow, it'll temporarily return 403 HTTP error code. When you reach this limit, the add-on won't show any share count for Facebook.Btw, why sometimes looks "zero" count bottom of the right corner and sometimes not ?
But then, that limit isn't high enough. If more than 200 different pages (which have the "share this page" widget, e.g. threads) gets visited within 60 minute, you'll reach the limit. Ignore the "per user" part. The method that I added in 1.4.0 will only use your App ID and Secret, so the limit is 200 API calls for the whole forums.Each each app is given an allotment of 200 API calls per user in any given 60 minute window.
Yeah.So, we catching the facebook api call limits, right?
Even then, they still have a rate limit. They probably logged your server's IP for the alternative mechanism. Wait for a few hours. And also, show me the cURL debug messages.I enter the facebook api id and secret key to our facebook integration but still i can't see the share count!!
Yes I enabled that. Still no luck, no count, even 0 (zero) does not appear@bibitbunga Are you sure that you've enabled the option? (screenshot attached on this message)

Hi@Mark T By default, there's no way to prevent that yet. You'll have to somehow check whether guest has the permission to view the current node, and then prevent the sidebar from loading. I don't know how to do it with a simple template conditionals yet, so I guess you'll have to wait for a while till I figure it out.
@bibitbunga Try to enable "cURL Debug" and "Cache Hit Debug" options. After that, load a random page, and show me the logs in your Admin CP's Server Error Logs.

<?php
var_dump curl_version();
Hi @BobbyWibowo I have uploaded the php content but if I load the URL, it shows blank.. http://www.kebunpedia.com/dumpcurl.php@bibitbunga You sure that you have cURL enabled? For some reason it couldn't fetch anything, but there was no error available either.
Try to make a new PHP file with these contents:
then show me the content.PHP:<?php var_dump curl_version();
And for the time being, you can try to enable "Disable cURL" option, so that the add-on will use file_get_contents() function instead.
<?php
var_dump(curl_version());
I have noticed share count errors with latest version. I have do not have them on at the moment. I have not had a lot of time to troubleshoot why this is. This is as soon as turned on. https://usaclash.comFixed typo with singular share count phrase in eh_socialshare.js template which caused phrase for singular share count to display incorrectly.
- Can I use share counts without cURL?
Yes, you can. By default, if you don't have cURL enabled, the add-on will usefile_get_contents instead. But then, you won't have the ability to set timeout. And if you want to prevent the add-on from using cURL even though you do have cURL, you can enable "Disable cURL" option on Admin CP.
$ctx = stream_context_create(array('http'=>
array(
'timeout' => 0.5, //In Seconds
)
));
echo file_get_contents('http://example.com/', false, $ctx);
We use essential cookies to make this site work, and optional cookies to enhance your experience.