/ cloudinary

New Official update for the Cloudinary Ghost Storage plugin

I took time to update and fix some little things I had in mind for the Cloudinary Ghost Storage plugin, but I just to tell you everything in the right order.

@sethbrasile: where is the plugin creator?

No idea. I tried to reach him several times (and in several ways) in these latests months without success. Because the first version of the plugin was waiting for some pull requests to be fully compliant with Ghost 1.X.

I then check with the Ghost community if we could switch the link to the "official" plugin... and if someday @sethbrasile will come back we can put it back.
So, right now, the link to the plugin you can find on the Ghost Official Page is bringing to the fork hosted on my github space. And this version is updated and fixed!!


How can I install this version of the plugin?

This is the tricky part: as I wasn't able to get in touch with @sethbrasile I cannot get access to the NPM library to deliver the new version.
So I decided, for the moment, to change the name of the npm lib. You can find the new version here; and naturally install it via npm:

npm install cloudinary-store

On the repository you can find all the instructions to install it on your blog.

What are the news?

  • The exists method to check if an image is already on cloudinary is now working correctly (the API we were using was not the correct one)
  • There is a new configuration section to manage the file names. Schermata-2017-09-17-alle-18.43.06.png
    You can check the available parameters directly on the Cloudinary API documentation: https://cloudinary.com/documentation/image_upload_api_reference#upload
  • During the upload we use the original filename and not the browser random one
  • The manage of the file name allow to prevent duplicated images on your Cloudinary space. You can personalize this part with the Cloudinary API parameter (random name by cloudinary, base name + random part, only the original name, override or not in case of duplicated, ...)

You can get back to me, directly of with a github issue, if you have any ind of problem with the plugin.