Problem with Twenty Thirteen

Sorry for the late reply. It looks like you’ve switched to a different plugin on your site at this point, so I installed Twenty Thirteen on my site to test. The problem is that Twenty Thirteen includes an old version of the jQuery Masonry plugin, which has the imagesLoaded library included in it. This is causing a conflict with Shashin, which includes its own copy of imagesLoaded. Unfortunately it’s not a simple matter of setting Shashin to not use its own copy of imagesLoaded, as Shashin is designed around the current version of imagesLoaded (not the older one in Masonry).

The current version of Masonry does not include the imagesLoaded library. Updating the version of Masonry in Twenty Thirteen to the current one may solve the problem.

See here: http://masonry.desandro.com/appendix.html#upgrading-from-v2

I just tested the following, and it lets Shashin work with Twenty Thirteen:

1. Download v3.1 of Masonry: http://masonry.desandro.com/masonry.pkgd.min.js

2. Copy it to your wp-content/themes/twentythirteen/js folder

3. Edit the Twenty Thirteen functions.php file. Comment out line 166, like this:

//wp_enqueue_script( 'jquery-masonry' );

4. After the above line, add this:

wp_enqueue_script( 'jquery-masonry3', get_template_directory_uri() . '/js/masonry.pkgd.min.js', array( 'jquery' ), '2013-07-18', true );

Note this is a “quick and dirty” solution. If you want to follow proper WP practices, you would create a child theme and have it dequeue jquery-masonry, and then enqueue the new version there. That way you would not lose your changes if there is an upgrade to Twenty Thirteen.

Or if you want to go really crazy and remove Masonry altogether without breaking the theme, someone wrote a tutorial.