Mike Toppa

What I didn’t realize is that WordPress’ auto-update function no longer runs the plugin’s activation hook (it used to), even though the message says it is activating the plugin – http://core.trac.wordpress.org/ticket/17833

The auto-update behavior is something that is not possible to test without an actual upload of a new version to the repository. That was the main source of people’s troubles. The quirks with Fancybox were due to me having to rush to replace Highslide, as its not compatible with the licensing requirements of the wordpress.org repository (it has a Creative Commons license, not GPL; my bad for not being aware the licenses are not compatible).

If you are happy with Highslide, and you don’t need multi-site support, you’ll be fine staying on 3.0 for now. The main changes in 3.1 are multi-site support and the switch to Fancybox.

I haven’t forgotten this. I got sidetracked by the need to switch the viewer to Fancybox.

Sorry for the late reply. The latest version will give you a more detailed error message now if there is a synchronizing problem, so we can track down what the problem is.

I inadvertently introduced a bug in the version I uploaded a few days ago. If you get the latest version that problem is fixed.

I’m not sure. Someone sent me a French translation that they wrote and said it worked fine for them, so I think the Shashin code is ok.

The fancybox code is all in javascript so I can’t add the translation function to it.

I just learned that when the automatic plugin update shows you a message saying its deactivating and reactivating the plugin, it’s not really doing it:

http://core.trac.wordpress.org/ticket/17833

As Sergey said, you will need to deactivate and reactivate Shashin in your plugin menu after updating.

I just uploaded version 3.1.3 which address several Fancybox issues.

Also, so you know, I had to switch to Fancybox in order to keep Shashin in the wordpress.org repository, as Highslide is not compatible with the repository’s GPL licensing requirements. It was a lot of work switching to Fancybox, and it wasn’t something I was originally planning to do.

waggles, what do you mean it “wipes out all your photos”? That definitely should not happen. If I can help you debug, let me know.

Hi Sergey – I’ve taken a closer look at the Facebook Like button implementation. I don’t think it will make much sense to add this to Shashin after all. The Like button requires that you are “liking” a specific URL, so it won’t make sense to include the Like button when showing a picture in Highslide, since it’s showing pictures through Javascript. For the thumbnails, they are embedded in WordPress posts or pages, and there are already plugins available for adding Facebook Like buttons to posts and pages (or to put it another way, if I added a Like button for Shashin thumbnails, there would be no way to distinguish liking the pictures from liking the post they are in, since they are at the same URL).

Looks like you posted this question twice – http://wordpress.org/support/topic/plugin-shashin-how-to-have-the-description-album-summary?replies=1