I read both discussions. The second OP says: "....setting the addon to not auto-update." Cannot see how to do that in the x-notifier options page. Do you know how?If so, pls be so kind to let me know. Thanks in advance. Jim
Go to about:addons, extensions, search for X-notifier, click on 'more' in its description, it will show full description. Below are the options to enable/disable auto update.
"....setting the addon to not auto-update." to me meant the addon needed to be set as needed. did not know it was a firefox setting function. No more, Jim
As you found out (from your posts below), there are two settings... one per individual add-on and one 'global' setting to disable all add-on updates. I don't know that we really have to disable add-on updates as they should recognize what FF version they are compatible with and simply not update on incompatible Firefox versions... and all the other add-ons will have to change for the newer Firefox as well, so perhaps the global disable is easier, although you might miss a few minor updates until the changeover. However if developers are lazy and don't set version compatibility numbers, there may be a problem...
Just for others reading this...
Per add-on disable: - Go to the Firefox menu (three horizontal lines in the upper right corner), click Add-ons, scroll to your specific add-on, click More, and scroll down to the Automatic Updates settings and choose On or OFF ...applies to just that add-on. No need to go to about:config.
Global disable: - The global disable can be found by going to the FF menu, clicking Add-ons, clicking the 'gear' icon and checking or UNchecking 'Update Add-ons Automatically. Again, no about:config necessary.
Apparently the new API/FF release will be in November... perhaps ...who knows what Firefox version will be released generally (not a beta version). I'm not going to bother with running X-Notifier 3.x on a beta version. At some point, they will 'flip the switch' and 3.x will quit working on the new update, whatever version number it is.
Disable Firefox automatic update: - Go to the Firefox menu (three horizontal lines in the upper right corner), click Options, click Advanced, click the Update tab, click 'Check for updates but let me choose...' or 'Never check'. Those choices are a greater security risk however, as you won't get bug fixes and security updates.
Since Firefox is a secondary browser I use for specific tasks, and not general browsing, I can probably stay on the old versions for a while. Hopefully, Tobwithu can improve the situation with the new API, someday.
@Kalimist: Firefox 50 is under development (beta). You are running some nightly build version. I expect the alpha release (nov 2016) will only work with X-notifier 4.0 and later (exclusively using the WebExtensions API).
I don't think so, that would be a suicide for Firefox, it is losing users in each version they launch and they could make it disappear with that radical move. Most of them use Firefox because of the addons. Chrome is a far better browser but the addons are worse IMHO.
You are right about my confusion with alpha-beta terminology. An alpha version is usually not feature complete and often unstable. The beta version follows and eventually becomes the pre-release version. But a nightly build is not one particular version. It is a general term for an in development updated version, I believe. Mozilla qoute: "Nightly builds of what will become Firefox 50 are currently available on the Beta channel." Meaning nightly builds exist for v.50, v.51 and v.52 (only for testing purposes).
So you believe Mozilla will not drop support for XUL and XPCOM, despite of what they are announcing, in fear of losing to much ground... When you are right I think this also depends on their success in forfilling all lacking development whishes for the WebExtensions API.
Do not disable all addons updates! You will probably have security flaws and all kinds of problems with the rest of the addons. Do what I said (the same that is explained in ghacks). The reason Mozilla has set that option partially "hidden" is because is very important to set it to auto update all addons by default.
I'm waiting for v.4 to work so I can activate multiprocess (huge performance increase for the browser). I only disabled auto update X-notifier setting temporarily.
I did do solely as you said and turned off solely x-notifier. I also stoped Fx auto updates,'requiring that I be notified before an update. Thank much for the heads up. the articles were confusing but I sorted them out and went the direction you specified. Was I a good boy Dad? He Haw. Thanks, Jim
jeroen
Sun, 09/25/2016 - 07:09
Permalink
X-notifier version
Pick version 3.5.23 for Firefox 49.0 from here:
https://addons.mozilla.org/en-US/firefox/addon/xnotifier/versions/
The Mozilla Add-ons page links to latest version 4.0.1 for Firefox 50.0, which involves radicle changes: http://xnotifier.tobwithu.com/dp/node/3365
JamesEJ
Sun, 09/25/2016 - 08:40
Permalink
reply
Thanks very much Jeron! Owe ya one.
I read both discussions. The second OP says: "....setting the addon to not auto-update." Cannot see how to do that in the x-notifier options page. Do you know how?If so, pls be so kind to let me know. Thanks in advance. Jim
Kalimist
Sun, 09/25/2016 - 09:13
Permalink
Go to about:addons,
Go to about:addons, extensions, search for X-notifier, click on 'more' in its description, it will show full description. Below are the options to enable/disable auto update.
JamesEJ
Sun, 09/25/2016 - 09:45
Permalink
reply
Oh, we are talking about a firefox modification, not an addon one. OK tks.
Kalimist
Sun, 09/25/2016 - 10:07
Permalink
I don't understand your reply
I don't understand your reply, sorry, what do you mean with "firefox modification"?
JamesEJ
Sun, 09/25/2016 - 11:21
Permalink
"....setting the addon to not
"....setting the addon to not auto-update." to me meant the addon needed to be set as needed. did not know it was a firefox setting function. No more, Jim
RpD
Fri, 09/30/2016 - 10:17
Permalink
Two settings
As you found out (from your posts below), there are two settings... one per individual add-on and one 'global' setting to disable all add-on updates. I don't know that we really have to disable add-on updates as they should recognize what FF version they are compatible with and simply not update on incompatible Firefox versions... and all the other add-ons will have to change for the newer Firefox as well, so perhaps the global disable is easier, although you might miss a few minor updates until the changeover. However if developers are lazy and don't set version compatibility numbers, there may be a problem...
Just for others reading this...
Per add-on disable:
- Go to the Firefox menu (three horizontal lines in the upper right corner), click Add-ons, scroll to your specific add-on, click More, and scroll down to the Automatic Updates settings and choose On or OFF ...applies to just that add-on. No need to go to about:config.
Global disable:
- The global disable can be found by going to the FF menu, clicking Add-ons, clicking the 'gear' icon and checking or UNchecking 'Update Add-ons Automatically. Again, no about:config necessary.
Apparently the new API/FF release will be in November... perhaps ...who knows what Firefox version will be released generally (not a beta version). I'm not going to bother with running X-Notifier 3.x on a beta version. At some point, they will 'flip the switch' and 3.x will quit working on the new update, whatever version number it is.
Disable Firefox automatic update:
- Go to the Firefox menu (three horizontal lines in the upper right corner), click Options, click Advanced, click the Update tab, click 'Check for updates but let me choose...' or 'Never check'. Those choices are a greater security risk however, as you won't get bug fixes and security updates.
Since Firefox is a secondary browser I use for specific tasks, and not general browsing, I can probably stay on the old versions for a while. Hopefully, Tobwithu can improve the situation with the new API, someday.
jeroen
Sun, 09/25/2016 - 09:28
Permalink
Correct, but...
You then probably also should prevent Firefox from updating to version 50.0, because X-notifier 3.5.23 will likely not work with that version.
(Deprecation of XUL, XPCOM, and the permissive add-on model:
https://blog.mozilla.org/addons/2015/08/21/the-future-of-developing-firefox-add-ons/ ).
JamesEJ
Sun, 09/25/2016 - 09:45
Permalink
very good thought!
very good thought! made the firefox changes. tks
Kalimist
Sun, 09/25/2016 - 10:03
Permalink
I'm using Firefox 50 (beta)
I'm using Firefox 50 (beta) and v.3.5.23 works good.
Regards.
jeroen
Sun, 09/25/2016 - 12:02
Permalink
Thanks
Then my expectation this dreaded moment has almost arrived is incorrect.
Lets hope it takes Mozilla forever.
jeroen
Mon, 09/26/2016 - 01:04
Permalink
@Kalimist
https://developer.mozilla.org/nl/Firefox/Releases/50#Changes_for_Web_developers :
"Firefox 50, based on Gecko 50, will ship in November 2016. This article provides information about the changes in this release that will affect developers. Nightly builds of what will become Firefox 50 are currently available on the Beta channel." and "Changes for add-on and Mozilla developers: Tbd"
@Kalimist: Firefox 50 is under development (beta). You are running some nightly build version. I expect the alpha release (nov 2016) will only work with X-notifier 4.0 and later (exclusively using the WebExtensions API).
Kalimist
Mon, 09/26/2016 - 06:22
Permalink
I don't think so, that would
I don't think so, that would be a suicide for Firefox, it is losing users in each version they launch and they could make it disappear with that radical move. Most of them use Firefox because of the addons. Chrome is a far better browser but the addons are worse IMHO.
You have a little confusion with the channels, read this: https://hacks.mozilla.org/2012/05/firefox-and-the-release-channels/
Right now, Stable version is 49, Beta is 50, Aurora (developer edition) is 51 an nightly is v.52.
jeroen
Mon, 09/26/2016 - 07:17
Permalink
Right...
You are right about my confusion with alpha-beta terminology.
An alpha version is usually not feature complete and often unstable.
The beta version follows and eventually becomes the pre-release version.
But a nightly build is not one particular version. It is a general term for an in development updated version, I believe. Mozilla qoute:
"Nightly builds of what will become Firefox 50 are currently available on the Beta channel."
Meaning nightly builds exist for v.50, v.51 and v.52 (only for testing purposes).
So you believe Mozilla will not drop support for XUL and XPCOM, despite of what they are announcing, in fear of losing to much ground...
When you are right I think this also depends on their success in forfilling all lacking development whishes for the WebExtensions API.
Kalimist
Mon, 09/26/2016 - 18:42
Permalink
The thing is, 99% of the
The thing is, 99% of the addons are still not converted to WebExtensions. Check this: http://arewee10syet.com/
Nightly builds are version 52, you can download them here: https://nightly.mozilla.org/
Beta builds aren't released every day (night) as nightly builds do.
jeroen
Mon, 09/26/2016 - 21:19
Permalink
Get it
Get it. Thanks!
jeroen
Sun, 09/25/2016 - 12:31
Permalink
Future of X-notifier for Firefox
Admin reported it will happen in the near future:
http://xnotifier.tobwithu.com/dp/node/3353
But apparently the near future has not yet arrived with version 50...
jeroen
Mon, 09/26/2016 - 00:38
Permalink
Deprecation Timeline
Mozilla (21 aug 2015):
https://blog.mozilla.org/addons/2015/08/21/the-future-of-developing-firefox-add-ons/
"We don’t have a specific timeline for deprecation, but most likely it will take place within 12 to 18 months from now."
So between now and februari 2017...
JamesEJ
Sun, 09/25/2016 - 16:21
Permalink
reply to all, re: Kalimist directions
Kalimistabout and all: Did the about:addons ....... routine you suggested. But also researched and read the Mozzila Blog... How to turn off add-on updates (https://blog.mozilla.org/addons/how-to-turn-off-add-on-updates/
So I also went the "about:config" route. Seems there is both an addon method and a Fx method to achieve the same ends results
Fingers crossed here guys. Am I ok with addon updates now?
Edit: With more research, this GHacks article seems to have cleared matters up between the two addon updates on-off methods. http://www.ghacks.net/2011/11/01/how-to-turn-off-automatic-updates-for-i...
Guess I am good but comments are sure welcome.
Kalimist
Mon, 09/26/2016 - 06:31
Permalink
Do not disable all addons
Do not disable all addons updates! You will probably have security flaws and all kinds of problems with the rest of the addons. Do what I said (the same that is explained in ghacks). The reason Mozilla has set that option partially "hidden" is because is very important to set it to auto update all addons by default.
I'm waiting for v.4 to work so I can activate multiprocess (huge performance increase for the browser). I only disabled auto update X-notifier setting temporarily.
JamesEJ
Mon, 09/26/2016 - 08:50
Permalink
I did do solely as you said
I did do solely as you said and turned off solely x-notifier. I also stoped Fx auto updates,'requiring that I be notified before an update. Thank much for the heads up. the articles were confusing but I sorted them out and went the direction you specified. Was I a good boy Dad? He Haw. Thanks, Jim