Known Issues With Clippings 6

Below is a list of known issues with Clippings 6, along with suggested solutions.

I'm prompted to import my backup file after the upgrade, but I didn't create one.

Problem: Some users either forgot to, or didn't get around to, creating a backup of their Clippings, or they somehow missed the user messages in Clippings 5.5 to do so, or they did not upgrade to Clippings 5.5 to see the user messages in the first place. Regardless, the clippings are seemingly "lost."

Solution: Follow these steps:

  1. Use the file manager application on your system (e.g. Windows Explorer) to find the Clippings data source location. Depending on your previous settings, it may be your Firefox profile folder, or another folder located elsewhere.
  2. Open the data source folder and locate the Clippings backup folder. It should be named "clippings-backup" or ".clipbak".
  3. Open the Clippings backup folder and locate the most recent backup file. Copy this to your Desktop or Documents folder.
  4. Open Clippings Manager, then Tools → Import, and then select the backup file.

Import of the Clippings backup file failed.

Problem: When attempting to import the clippings backup file in the Welcome to Clippings 6 page, or from Clippings Manager, the clippings don't appear.

Solution: The database that Firefox uses to store extension data may be inaccessible, corrupted or otherwise not set up correctly. Do the following:

  1. Check that Private Browsing mode in Firefox is not turned on. Clippings won't work in Private Browsing mode. Then restart Firefox and try again.
  2. If that doesn't work, Refresh Firefox, then reinstall Clippings and import your clippings backup again.

My clippings disappear when I'm using Private Browsing mode.

Problem: When opening the Clippings menu on the browser's context menu while Firefox is in Private Browsing mode, none of the clippings and folders appear. They reappear when switching to a normal browser window.

Solution: None at the moment, other than to avoid using Clippings in Private Browsing mode.

The keyboard paste shortcut key has changed to ALT+SHIFT+Y. Why?

Problem: The keyboard paste key was changed in Clippings 6 to be ALT+SHIFT+Y. Many users are having difficulties adjusting to it, while others hate it with a passion.

Response: Get used to it. The old CTRL+ALT+V shortcut key had to be changed because WebExtensions are not allowed to use CTRL and ALT together (apparently, it conflicts with the AltGr key on European keyboards). Alternatives were considered, but ALT+SHIFT+V displays the View menu in the top application menu bar in Firefox, and CTRL+SHIFT+V pastes as plain text. Emacs users may find the new shortcut key to be vaguely familiar, as the paste ("yank") key used in that text editor is CTRL+Y.

I don't see the placeholder prompt dialog when pasting a clipping with custom placeholders.

Problem: In past versions, users would be prompted to fill in the value of a placeholder when pasting a clipping. No such prompt appears when doing the same with Clippings 6.

Solution: Upgrade to version 6.0.2, which brought back this feature.

I want to share my clippings with my other machines on my network. Can I do this in Clippings 6?

Problem: Users have set their Clippings 5.x data source location to a network share so that they can use the same clippings on different machines.

Response: WebExtensions such as Clippings can no longer access the local file system on their own, so Clippings 6 couldn't store its data in a data source file like it did in previous versions. It now stores all its clippings in a database provided by Firefox. For now, your options are either to manually import and export across your computers, or consider installing Firefox ESR on your machines so that you can continue to use Clippings 5.5.x and be able to access your clippings on a network share.

Exporting to a Clippings 6 data file or to an HTML document results in a blank file.

Problem: Some users have reported that exporting clippings doesn't work.

Solution: Upgrade to version 6.0.2.1, which contains a fix for this issue.


Back to the Help Index