We want to auto-populate k2 stories on page scroll. You can see demo at http://new.blabber.buzz/index.php?optio … temid=1478 . You will notice that when we reach end of one k2 story, next k2 story appears and URL also gets changed but social links on stories thereafter did not work.
Kindly let me know solution as how these social share links work on rest of the k2 stories also.
The page you linked to is restricted, so I can't see the issue. I tried to register with Facebook, but I get the following message:
URL Blocked: This redirect failed because the redirect URI is not whitelisted in the app’s Client OAuth Settings. Make sure Client and Web OAuth Login are on and add all your app domains as Valid OAuth Redirect URIs.
Twitter brings me to a red page with "0 - Bad request token!". That is usually caused by having the Twitter app setup incorrectly. I'd recommend checking out the Twitter Setup Guide and making sure the Callback URL is setup properly in your app.
I couldn't find a way to register otherwise on your site, and can't see the page without logging in. Once you get that going, let me know and I'll gladly help however I can.
As for the actual issue, can you let me know what's happening to the social buttons in the stories that pop in? Are the social buttons just missing or are the raw JFBConnect tags just showing?
Any details you can provide will help us understand ahead of time before we see the issue when we login.
I apologize on this. I forgot that you will not be able to view issue without login. Kindly login using credentials nirmalTest / nirmalTest
After that, you will be able to view issue at http://new.blabber.buzz/index.php?optio … temid=1478
It looks like social share links appear on page load only. When second page appear automatically on scroll, these social share links did not work. Kindly share your views on this and let me know how we can fix this?
I apologize for the delay in getting back to you! Thank you for sending the details on how to view the page. That helped a lot.
Once that's called, any new Twitter or Facebook widgets on the page will render properly. Those calls should be made whenever a new article (or batch of a few) are loaded into view.
Google+ doesn't have as easy of a mechanism to re-render their tags. Google+ is planned to shut down in April 2019 though, so we're not recommending using their widgets any longer.
I hope that helps, but if you need anything else, please let me know.