X
Tap here to go to the mobile version of the site.

Support Forum

can not get topcashback notifier to work with firefox

Posted

I have recently become a firefox "convert" but I just can not get the topcashback notifier to work. I have read many things but no matter what i try it always says its unregistered

I have recently become a firefox "convert" but I just can not get the topcashback notifier to work. I have read many things but no matter what i try it always says its unregistered

Chosen solution

Hi,

Required add-on signing for extensions is new in Firefox version 43. Back in February 2015 it was announced that, for a safer add-on experience, all extensions will have to be verified and signed by Mozilla before they can be installed. More insight into that decision is contained in Mozilla's April 2015 blog post.

Extensions hosted on addons.mozilla.org are automatically signed. If an extension you wish to use is distributed by a third-party, it must be signed before you can install it. Unsigned extensions that you have already installed will be automatically disabled. Please ask the add-on developer or vendor if an updated and signed version of the add-on is available. You can also visit addons.mozilla.org to see if there's a signed version of the add-on you can install.

This signing requirement is mandatory in regular release and beta versions of Firefox. For testing purposes, it will still be possible to configure Firefox Developer Edition and Nightly versions to run unsigned extensions. For more information, please see Add-on signing in Firefox and https://wiki.mozilla.org/Add-ons/Extension_Signing.

You can visit the mozilla.addons.user-experience group to further discuss add-on signing.

Read this answer in context 0

Additional System Details

Installed Plug-ins

  • Google Update
  • NPWLPG

Application

  • Firefox 43.0.3
  • User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0
  • Support URL: https://support.mozilla.org/1/firefox/43.0.3/WINNT/en-GB/

Extensions

  • RoboForm Toolbar 7.9.15.9 ({22119944-ED35-4ab1-910B-E619EA06A115})

Javascript

  • incrementalGCEnabled: True

Graphics

  • adapterDescription: AMD Radeon HD 7340 Graphics
  • adapterDescription2:
  • adapterDeviceID: 0x9808
  • adapterDeviceID2:
  • adapterDrivers: aticfx64 aticfx64 aticfx64 aticfx32 aticfx32 aticfx32 atiumd64 atidxx64 atidxx64 atiumdag atidxx32 atidxx32 atiumdva atiumd6a atitmm64
  • adapterDrivers2:
  • adapterRAM: 256
  • adapterRAM2:
  • adapterSubsysID: 05921025
  • adapterSubsysID2:
  • adapterVendorID: 0x1002
  • adapterVendorID2:
  • direct2DEnabled: True
  • directWriteEnabled: True
  • directWriteVersion: 10.0.10586.0
  • driverDate: 8-21-2015
  • driverDate2:
  • driverVersion: 15.201.1151.0
  • driverVersion2:
  • info: {u'AzureCanvasBackend': u'direct2d 1.1', u'AzureFallbackCanvasBackend': u'cairo', u'AzureContentBackend': u'direct2d 1.1', u'AzureSkiaAccelerated': 0}
  • isGPU2Active: False
  • numAcceleratedWindows: 1
  • numTotalWindows: 1
  • supportsHardwareH264: Yes
  • webglRenderer: Google Inc. -- ANGLE (AMD Radeon HD 7340 Graphics Direct3D11 vs_5_0 ps_5_0)
  • windowLayerManagerRemote: True
  • windowLayerManagerType: Direct3D 11

Modified Preferences

Misc

  • User JS: No
  • Accessibility: No
Seburo
  • Top 10 Contributor
  • Moderator
782 solutions 5728 answers

Chosen Solution

Hi,

Required add-on signing for extensions is new in Firefox version 43. Back in February 2015 it was announced that, for a safer add-on experience, all extensions will have to be verified and signed by Mozilla before they can be installed. More insight into that decision is contained in Mozilla's April 2015 blog post.

Extensions hosted on addons.mozilla.org are automatically signed. If an extension you wish to use is distributed by a third-party, it must be signed before you can install it. Unsigned extensions that you have already installed will be automatically disabled. Please ask the add-on developer or vendor if an updated and signed version of the add-on is available. You can also visit addons.mozilla.org to see if there's a signed version of the add-on you can install.

This signing requirement is mandatory in regular release and beta versions of Firefox. For testing purposes, it will still be possible to configure Firefox Developer Edition and Nightly versions to run unsigned extensions. For more information, please see Add-on signing in Firefox and https://wiki.mozilla.org/Add-ons/Extension_Signing.

You can visit the mozilla.addons.user-experience group to further discuss add-on signing.

Hi, Required add-on signing for extensions is new in Firefox version 43. Back in February 2015 [https://blog.mozilla.org/addons/2015/02/10/extension-signing-safer-experience/ it was announced] that, for a safer add-on experience, all extensions will have to be verified and signed by Mozilla before they can be installed. More insight into that decision is contained in Mozilla's [https://blog.mozilla.org/addons/2015/04/15/the-case-for-extension-signing/ April 2015 blog post]. Extensions hosted on addons.mozilla.org are automatically signed. If an extension you wish to use is distributed by a third-party, it must be signed before you can install it. Unsigned extensions that you have already installed will be automatically disabled. Please ask the add-on developer or vendor if an updated and signed version of the add-on is available. You can also visit addons.mozilla.org to see if there's a signed version of the add-on you can install. This signing requirement is mandatory in regular release and beta versions of Firefox. For testing purposes, it will still be possible to configure Firefox Developer Edition and Nightly versions to run unsigned extensions. For more information, please see [[Add-on signing in Firefox]] and [https://wiki.mozilla.org/Add-ons/Extension_Signing]. You can visit the [https://groups.google.com/forum/#!forum/mozilla.addons.user-experience mozilla.addons.user-experience] group to further discuss add-on signing.