14 November 2017

Clippings 6 released!

The new WebExtension version of Clippings is now available for download from Mozilla Add-ons and the AE Creations website.

If you already have Clippings installed, it will be upgraded for you if automatic extension updates are enabled. Otherwise, open Extension Manager (Tools → Add-ons), then right-click on the entry for Clippings in the list of installed extensions and choose Find Update.

What's New
  • Compatible with Firefox 57 (Firefox Quantum)
  • The limitation on creating and pasting clippings in web pages with HTML frames has been eliminated with this release
  • Improved clippings and folders search in Clippings Manager

Things You Should Know About

This release has most of the features from version 5.x, although there are a few which are not available; most notably:
  • Adding or editing color labels on clippings
  • No prompts for placeholder values are displayed when pasting a clipping containing placeholders. Does not affect built-in placeholders (e.g. for the date)
Other things to note about the upgrade from previous versions of Clippings:
  • Due to WebExtensions being restricted from using any keyboard shortcuts that start with CTRL + ALT, the keyboard paste key has now changed - it is now ALT+SHIFT+Y (Cmd+Shift+Y on macOS).
  • If there were labels on clippings in the imported data source, they will be brought over to Clippings 6 with the import; the color labels will appear on the Clippings context menu.  However, labels cannot be edited for existing clippings, or added to new clippings. This will be fixed in a future release.

Help and Support

Questions and comments about Clippings should be directed to the AE Creations Help and Support forums, hosted on Google Groups.


Grzegorz Podgórski said...

after loading all my clippings from file .rdf and after restart the browser v.57, all clippings has gone!
And I cannot wrote any new clipping or folder - it doesn't work!
It's a huge problem;
please help?
Kind Regards

asafatmagento said...

1. All the clippings are now gone after the upgrade, I was not prompted to create a backup after and now they are all gone.
2. I am no longer able to map the shortcut key as I desire which creates a loss of productivity.

This is very disappointing that the update was done without any notification that the data would be lost and should be backed up and that the shortcut key is not static and cannot be changed either by the add-on or by an alternate add-on.

AE Creations said...

@Grzegorz Podgórski: Do you see any errors in the browser console when attempting to create a new clipping or folder?

@asafatmagento: Clippings 5.5 had notifications in the Clippings browser context menu and in Clippings Manager about the upgrade to Clippings 6, with links to instructions on preparing for the upgrade by backing up your clippings. To manually bring your old clippings into Clippings 6, locate the backup files that were automatically generated by your previous version of Clippings, and import the most recent backup file into Clippings 6. The change of shortcut key was required because WebExtensions are not permitted to use CTRL and ALT, so you will need to adjust to this change.

Grzegorz Podgórski said...

'Do you see any errors in the browser console when attempting to create a new clipping or folder?'
'Error creating clipping: OpenFailedError: InvalidStateError A mutation operation was attempted on a database that did not allow mutations.'
I hope that You find the way to solve of this problem?
Kind regards

Grzegorz Podgórski said...

Victory - I find the solution with problem in Fx v.57;
I always used the option Private Browsing:
When I switch off this option, all my clippings have returned and when I switch on PrivateBrowsing, all clippings have disappears!
I'm surprise that Clippings 6.0 doesn't work in Private Browsing option, because in Fx 56 add-on Clippings 5 working excellent in this option.
I hope that you find any solution?

Kind regards
P.S. My notebook has Win7 [64bit]

AE Creations said...

Thanks Grzegorz for sharing your findings! The legacy extensions didn't have to worry about private browsing mode affecting functionality, but it appears that is no longer the case with WebExtensions. I will see if it is possible to workaround it; hopefully this is not yet another constraint imposed on WebExtensions. Thanks again.