Issue: Regression: Social bookmarking is gone

Yes, this is a regression. I've wanted to include Social Bookmarking icons and other ways to link externally as a sidebar block with 'top' positioning.

This report will remind us to put it back in.

Please consider this method so that privacy is also considered: http://xenforo.com/community/resourc...-privacy.2287/
You can see it in action on my dev site.
Would be nice if VW would pull all settings from the forum software.

XenForo uses www.addthis.com btw. This should be fairly easy to add.

Fixed in the next release. Social bookmarking options return at the page level as a sidebar block. It automatically includes:

For all forum platforms:
- BB-Code links to the current page, for both in-site and external links
- BB-Code image links for the current image (if an image), for both in-site and external links

For vBulletin platforms:
- social bookmarking links from vBulletin's Social Bookmark Manager
- facebook like for vBulletin 4, if the version has facebook like functionality, and the new toggle is enabled in VaultWiki: Miscellaneous

For XenForo platforms:
- facebook like, tweet, google +1, if XenForo has those options enabled
- addthis buttons, if enabled. If the tweet option is shown above, addthis will exclude the Twitter button, since it's a duplicate function. Facebook and Google buttons are not duplicate functions (Facebook like vs Facebook share, Google recommend vs Google bookmark).

Since VaultWiki 3 only had social bookmarking for the page as a whole, that's as far as this bug fix goes. If social bookmarking is desired at the discussion level, edit level, or comment level, separate feature requests should be posted. If alternate locations are desired for the buttons, such as a popup or link in the page's header rather than the sidebar, please post a separate feature request. As long as the links for social bookmarking appear somewhere, this regression fix has been satisfied.

I still need to figure out a way to implement privacy. I'm considering using a tunneling proxy so that the counts can be visible and you can still Like in 1 click, but I'm not sure if there's a good way to handle this for the AddThis service, since it has drop-down menus and such.

I think there will need to be a setting for privacy (full privacy, mixed privacy, and no privacy). Since every API is different, each anonymized button would need to have a specific handler. Since XenForo allows adding additional share buttons with template hooks and template modifications, this means that custom share buttons cannot be anonymized.

Good stuff!
Please let the user decide on privacy. Check out my dev site for an example of simple implementation.

Okay, privacy implemented. This has some performance implications either way (on or off), so it is a setting for the sidebar block site-wide. I really don't see a need to spend more time giving users a setting so that all the buttons are active all the time. The implementation is mostly unintrusive, since the buttons are styled the same way whether they are disabled or not.

If privacy is on, there is a little blurb at the top of the block explaining that the user might need to click twice. For AddThis, this means only the AddThis logo is visible, and the additional share buttons don't load until the logo is clicked.

If the user chooses to read it, there is also a tooltip explaining the deal with privacy concerns for sharing buttons.

VaultWiki will attempt to display the current share counts even if the button is inactive. This allows users to see how popular an item is even if they want their own privacy. However, this requires tunneling through the web server into each social media site, so there is some latency. VaultWiki caches these counts every 5 minutes to attempt avoiding this problem.