Just a quick note to say that the my Known Chrome plugin will now return an installable .crx file.
You’ll need the OpenSSL PHP extension installed, but if you do an installable .CRX file will be returned instead of a .zip. If you don’t have OpenSSL installed, the oldstyle .zip will be installed, however some people had problems with this.
I have a number of WordPress sites which use Dan Coulter’s Flickr API powered gallery plugin to render images from an attached Flickr account.
This plugin appears to no longer be maintained by the author, and I have previously written about having to make a couple of code changes in order to get it to work again.
Anyway, a little while ago, I noticed that my Flickr galleries had stopped working again, so here’s a fix.
Firstly, the Flickr API now REQUIRES that you connect to it via SSL. However, the Flickr gallery code uses the non-ssl endpoints.
So, in phpFlickr.php we need to update the endpoint URLs
var $rest_endpoint = 'https://api.flickr.com/services/rest/'; var $upload_endpoint = 'https://api.flickr.com/services/upload/'; var $replace_endpoint = 'https://api.flickr.com/services/replace/';
If you use the database cache, at this point you’ll need to reset it, since you need to rebuild the cache using the correct URLS.
To do this, open up mysql (or mysqlmyadmin) and open your wordpress database. Next, delete all the rows from the cache, e.g.
mysql> use wordpress; Database changed mysql> delete from wp_phpflickr_cache; Query OK, 904 rows affected (0.04 sec)
Next, it seems that there was a collision with the Flickr shortcode, seems something was already defining the code but was expecting different parameters (likely Jetpack, but I’ve not really investigated).
So, I modified flickr-gallery.php to define the shortcodes in the plugin’s init function, after un-registering the existing definitions, and altered the priority so that it was defined last.
Get the updated plugin on Github…
I do a lot of my day to day work on Github, as you may have noticed. So, to be a good #indieweb citizen, I figured it’d be nice to be able to at least comment on tickets from my own site.
Thankfully, Github has a pretty comprehensive API, so it turns out that doing this was pretty easy. So, I wrote a quick plugin for Known…
Install and activate the plugin in the usual way, and once enabled, you will have the ability to reply to comments and create tickets on Github. This is particularly useful when using the Known browser extensions (like my Chrome plugin).
To create a new ticket, make a reply to a plugin’s issues page, and to create a new comment, simply reply to the comment thread.
Let me know how you get on!
