AddThis announced support for sharing of HTML widgets today
Photo Credit: Hofstra
which led us to post about their announcement. Originally, this post was going to be a review of the AddThis HTML widget sharing service
. The news was good for widgets and those interested in widgets; from users to developers to marketers and publishers.
As we began writing about the impact of the announcement and thinking about the widget sharing service, we reflected on the widget space as a whole and some thoughts of late began resurfacing. The various thoughts, questions and ideas prompted us to rethink and change change the post entirely. This is now a generic look at widgets and the possible resurgence of widget conversations in 2011.
This is pure speculation and we are obviously biased towards this view. Indulge us, read the post and let us know what you think.
A few days ago, we’re not sure the exact time, something changed which caused problems when sharing an AddThis WordPress plugin enabled blog page to Facebook. The FB shares do not have the correct page title, description or images. This problem actually affects any page that uses the AddThis code specified in the technical section later in the post. However, we are only going to address the plugin related problems at this time and provide you with a simple patch.
Here’s a quick little patch for the WordPress AddThis plugin. Follow these instructions at your own risk. This patch has only been tested on WP 2.9.2 and AddThis Social Bookmarking Widget 1.6.1. We do not guarantee the patch nor do we take any responsibility if something breaks.
This patch will only fix pages that are considered by WordPress to be A Single Page, Single Post or Attachment (WP Codex: is_singular). These pages are probably the majority of your important shares.
WordPress 2.1.2 was released a few days ago. There were potential issues with 2.1.1 depending on when you obtained the download. To be safe, 2.1.1 in its entirety has been deemed dangerous. If you are running that version, you should upgrade to 2.1.2. Get the latest version of WordPress here. For more information on the specifics, check here.
While updating to the latest version of WordPress we decided to enable caching too. As we add more services and increase traffic, performance began to suffer. With caching enabled, the site is much snappier (if you’re not the first one to view a page or the cache on that page hasn’t expired). We chose to go with WP-Cache plugin for ease of use and deployment. Everything appears to be functioning, but please let us know if anything looks odd.
Update: We have disabled WP-Cache for now. There were too many places where we had real-time dynamic content that really shouldn’t be cached. So, rather than identify all locations and excluding them from the cache, we are optimizing the entire site.