Right now two of the most popular open source content management systems are WordPress and Drupal. WordPress is very simplistic and easy to roll out, which is why there is nearly 80,000,000 websites using WordPress. Then you have Drupal which is a more robust content management system that needs a little bit more love to get things moving.
After a few months I decided to give Facebook Albums some love. With 2.0.4 I implemented WordPress's caching mechanism to cache Facebook API responses for better performance. Will it never occurred to me about clearing said cache if the widget or that post updates.
So now if you update your Facebook Album widget, it will clear the cache and reflect your changes (such as image limit.) Ditto goes for posts, anytime a post saves the plugin checks for the shortcode (<3.6.0 compliant ;)) and clears that albums cached output.
We've all been there - create this awesome responsive design for a client's website and then you have to try and slap a Facebook Like Box in there..somehow..without breaking your responsive work. Sucks, doesn't it? But it doesn't have to. Using a little jQuery you can cause the Facebook Like Box to re-render on window load or resize allowing it to become responsive versus hardcoded.