Title: Problem with Twenty Thirteen
Last modified: August 21, 2016

---

# Problem with Twenty Thirteen

 *  Resolved [Brian1](https://wordpress.org/support/users/brian1/)
 * (@brian1)
 * [12 years, 6 months ago](https://wordpress.org/support/topic/problem-with-twenty-thirteen/)
 * Hello,
 * This appears to not be a problem that is not unique to Shashin. Using the wordpress
   theme Twenty Thirteen Shashin does two things that are not normal.
 * 1/ The images will not open up in a pop up with navigation tools. They simply
   open up in the same tab as a normal page with no navigation buttons.
 * 2/ Captions are not showing up either for the listing of folders or the individual
   photos.
 * I have tested this with Twenty Twelve and Shashin behaves properly.
 * I tried PWA+PHP Picasa Web Albums and it suffers from the same problem….working
   in Twenty Twelve but not in Twenty Thirteen.
 * Any help is greatly appreciated.
 * [http://wordpress.org/plugins/shashin/](http://wordpress.org/plugins/shashin/)

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Thread Starter [Brian1](https://wordpress.org/support/users/brian1/)
 * (@brian1)
 * [12 years, 6 months ago](https://wordpress.org/support/topic/problem-with-twenty-thirteen/#post-4282975)
 * Here is a link to the Album;
 * [http://burtsgh.com/album/](http://burtsgh.com/album/)
 *  Plugin Author [Mike Toppa](https://wordpress.org/support/users/toppa/)
 * (@toppa)
 * [12 years, 6 months ago](https://wordpress.org/support/topic/problem-with-twenty-thirteen/#post-4283021)
 * 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](http://masonry.desandro.com/appendix.html#upgrading-from-v2)
 *  [ganfoud](https://wordpress.org/support/users/ganfoud/)
 * (@ganfoud)
 * [12 years, 5 months ago](https://wordpress.org/support/topic/problem-with-twenty-thirteen/#post-4283038)
 * hi
    i didn’t understand how to update the version of Masonry in Twenty Thirteen,
   anybody can help? thanks
 *  Plugin Author [Mike Toppa](https://wordpress.org/support/users/toppa/)
 * (@toppa)
 * [12 years, 5 months ago](https://wordpress.org/support/topic/problem-with-twenty-thirteen/#post-4283039)
 * 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](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](http://slobodanmanic.com/444/flexible-horizontal-sidebars-wordpress-twenty-thirteen-child-theme/).
 *  [mrwweb](https://wordpress.org/support/users/mrwweb/)
 * (@mrwweb)
 * [11 years, 7 months ago](https://wordpress.org/support/topic/problem-with-twenty-thirteen/#post-4283055)
 * Please don’t edit theme files directly! You’ll lose your changes whenever the
   theme updates.
 * Instead, just use `wp_dequeue_script()` in a child theme or [mu-]plugin.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Problem with Twenty Thirteen’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/shashin.svg)
 * [Shashin](https://wordpress.org/plugins/shashin/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/shashin/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/shashin/)
 * [Active Topics](https://wordpress.org/support/plugin/shashin/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/shashin/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/shashin/reviews/)

## Tags

 * [twenty thirteen](https://wordpress.org/support/topic-tag/twenty-thirteen/)

 * 5 replies
 * 4 participants
 * Last reply from: [mrwweb](https://wordpress.org/support/users/mrwweb/)
 * Last activity: [11 years, 7 months ago](https://wordpress.org/support/topic/problem-with-twenty-thirteen/#post-4283055)
 * Status: resolved