Tag Archives: Box

About Box’s cloud storage. See also Cloud.

Detecting if third-party cookies are disabled

If you have signed up directly with Kerika, we use the Box Platform to store your files for you — Box is a secure, reliable cloud service and we have been a partner with them for several years.

But we do all this for you: efficiently, quietly and behind the scenes.

Which means you may never notice (and, really, you shouldn’t have to…)

However, we found that some users automatically block third-party cookies (this is a browser setting available in all types of browsers).

This was causing problems for the preview function for these users: when a user clicks on a file attached to a card or canvas, that’s getting stored in Box by Kerika for that user, we use Box’s Preview function in the form of an IFRAME.

Using an IFRAME enables us to add some Kerika-specific features, like automatic version tracking, to the standard Box Preview function.

This, however, requires users to allow Box.com to set a cookie, and this can fail if the user has never permitted Box.com to set cookies, or is automatically blocking all third-party cookies in their browser: when you are using Kerika.com, Box.com is effectively a third-party to the connection.

We want to make sure people understand this can be a problem, so we have added some smarts to Kerika to detect when people who have signed up directly are blocking Box.com.

If this is the case, a pop-up dialog box will appear explaining why the Preview function won’t work correctly without allowing Box.com’s cookies to be stored in the browser.

How we manage your document versions

Kerika helps you (and your team) manage multiple versions of a document, and it does this so smoothly that you might not even have noticed…

Here’s how it works: when you add a file to a Kerika card or canvas, it shows up in the list of attachments, like this:

File attached to a card
File attached to a card

If you then attach another file to the same card or canvas that has the same name and file type, Kerika automatically treats it as a new version of the same file, rather than a completely different file:

Uploading a new version
Uploading a new version

In the example above, when a Team Member adds another document called Foo.docx to a card that already has a file attached to it with the same name and file type, Kerika treats the new document as a new version of the old Foo.docx rather than as two documents called Foo.docx.

How you access all these old versions depends upon how you set up your Kerika account:

If you are using Kerika+Google, these files are being stored in your Google Drive, and Google will manage the versions for you: you can find this under the File menu in Google Docs

Google Docs versions
Google Docs versions

And pretty much the same thing is true if you are using Kerika+Box: Box will take care of the older versions automatically, although their user interface is slightly different

Box version history
Box version history

And what if you signed up directly with Kerika, without using a Google or Box ID?

We provide an easy way to get to older versions of a file for users who signed up directly: when you are previewing a file, click on the Older versions of this file link on the top-right.

File preview
File preview

Kerika will show you a list of all the old versions that are available for that file, along with details on who uploaded those versions, and when:

Older versions
Older versions

 

Why the files in your Kerika+Box folder have random characters appended to their names

If you are using Kerika+Box, we store your Kerika files in your Box account: you can always go to Box.com, login using your Box ID, and see for yourself.

(But, please, don’t move them around!)

What you might notice is that the filenames in Box have some random characters appended to them. For example, a file that you might see listed inside Kerika as “Alternative Home Page” actually shows up with some random characters appended, like this:

URL appended to file names
URL appended to file names

The reason we do this with files we store in Box — and not for files we store in Google Drive, for our Kerika+Google users, is that Box doesn’t allow for several files within a single folder to have the same name.

(Google does, which is why we don’t need to append any random characters to the files we store in Google Drive.)

It’s very common for our users to have several files within the same board that have the same name: for example, our developers always attach an analysis document to each card that describes exactly what they are doing. (Yes, we are fairly fanatical about documenting our software!)

These documents are often the same for many cards: Analysis.docx or Results.xlsx or Mockup.png might show up hundreds of times within a single board.

Since all the files related to a single Kerika board are stored in the same folder in your Box account, this presents a problem: Box won’t allow for more than one file called Analysis.docx within a folder.

We get around this limitation by appending these random characters, so that effectively every Analysis.docx file has a unique name.

But, we also try to avoid confusing our users, so when we show a list of files attached to a card, we strip out the random characters:

Displaying files as attachments
Displaying files as attachments

And the same goes for downloading files: we strip out the random characters and give you a clean-looking file.

Changing your Kerika password

For folks who sign up directly with Kerika, we store the user password (in an encrypted form, of course), which means that these users can change their passwords directly from within the Kerika application by going to their My Account page at https://kerika.com/my-account:

Changing password for Google sign up
Changing password for Google sign up

For people who sign up using their Google or Box IDs, we rely upon Google/Box to manage their passwords: in fact, we never even see anyone’s Google or Box password, even for a second!

So, their My Account page looks a little different, like in this example of a Kerika+Google user:

Changing password for Google sign up
Changing password for Google sign up

 

Feature, restored: simple download of files previewed within the browser

We now allow users to sign up for Kerika directly, by using any email address. This version is powered by the Box Platform, which allows us to make good use of Box’s cloud storage technology while presenting a simple user interface for our own users.

Another cool feature from Box that we had integrated, as part of this new service, was to use their browser-based preview functionality — which came to Box as a result of their 2014 purchase of Crocodoc.

We use this preview feature with a simple IFRAME integration, which means we don’t add anything to it ourselves, but one downside of this approach is that if Box removes something from their preview capability, it can disappear from Kerika also.

This happened recently when they took away a button that allowed for a quick download of a file that was being previewed.

We have fixed this by adding our own “Download file” link within the Box Preview:

Downloading previewed files
Downloading previewed files