Disabling auto updates, saving certificates, displaying full url and grouping tabs?
-
samkook last edited by
By looking at the description, all it does is rename the opera_autoupdate.exe which was already discussed in here, but it also set the next update time for extensions very far in the future inside the preferences file which is nice to know how to do and is still there in v20.
It also suggest that the extensions also get updated silently.
-
blackbird71 last edited byI only wish I had a dollar for every software update/patch that broke something on users' systems. Over the many years I've used computers (from the very earliest days), I've seen one program after another get updated and break somebody's system... DOS, Windows, AVs, browsers (of all kinds), drivers, and apps of every description. In every single case, the software creators were "absolutely, positively" certain their updates were thoroughly tested to be OK before issuing them - and in every case where problems occurred, it was eventually found there was something the creators had overlooked in the update that collided and broke something in certain system configurations. In most cases, updates/patches were fairly quickly re-issued with "fixes" for the user-encountered problems - but that is small comfort to the users who had to repair/rebuild/restore their messed up software after the crashes. And I simply cannot believe Opera ASA will suddenly, magically break that universal pattern.
"Bold" users employ auto-update for every piece of software on their systems. "Old" (experienced) users employ manual updates for virtually all their software, only applying them if the early-adopters encounter no problems. Note: there are no both "bold" and "old" users. Silent/auto-updating is a recipe for eventual user disaster, the only questions being when and how a problem will hit. That is what turns "bold" users into "old" users - and it's called 'wisdom gained by experience'. Opera seriously needs to rethink not putting an auto-update disable option into Blink Opera, if only in the Flags section.
-
lem729 last edited by
I certainly think the option ought to be with the user. If one has the option, I can think there are two views on whether to use auto-update. Quite frankly, I just have no time to manually deal with automatic updates across the board (and if I tried to (if I added this additional work to my life) I think I'd have a breakdown :). Further, even if I see the update sitting in my inbox (for my decision on installation or not), it would be hard for me to have any idea whether it is harmful or not. In most cases, if I have the choice, I will, therefore, hell be damned, auto-update. (And I believe, probably 95 percent or more of users would choose that course). I do it with Windows, with my browsers and with extensions. And I don't feel that bad about it. I choose to let go a little bit. The work and agony of trying to control every nickel and dime, isn't worth in value what I will get in return. I have on occasion been burned
But usually, there's a way back from the abyss even then. Reinstalling a program, system restores, etc.A few times in the past though, I have chosen against automatic updates.. For instance there was an Opera Presto browser I really liked. Opera forced an install -- new version -- on me I didn't like. I had to hunt to find the old browser, and then I restored it, and chose no updates. I also once needed an earlier version of Flash because the latest version was preventing Dragon Naturally Speaking from working on my computer, so I prevented updates there. I didn't want to be automatically updated into Dragon not working again. On my Ipad, I had an app that was letting me read supposedly premium articles at a new site. Now, haha, I wanted to find out how to prevents updates to save the wonderful feature (but I wasn't quick enough to solve that problem and got auto-updated out of the feature. So I do understand why some people might opt for no automatic updates, and others might want to have the ability on a case by case basis (as I have occasionally done) to opt out.
-
samkook last edited by
The best of both worlds is to have a software check for updates automatically and ask you to install them or not with a changelog displayed. That way, one can judge if an update might break something important and one can choose to backup certain things, wait a few days or just go ahead and update if it all seems harmless.
FlashFXP updates work exactly like that and I love it, it makes life so much easier.About updates breaking stuff, there's a software I need to install on some computers and when it needs updating, we have to reformat the whole computer and reinstall everything with a fresh install of that particular software being the first thing done or things always go badly.
-
lem729 last edited by
The more knowledgeable the person is, the less the burden of making the decision. For me, I see constant windows updates, browser updates (all of browsers) (Opera 20 and Opera 12.17 are my prime but I have all of the other major browsers on my computer -- Internet Explorer, Firefox, Chrome), I have 20 extensions alone :)in Opera 20 , almost as many in Firefox and Chrome (some even in Opera 12.16) (So let's say 60 in all) (wow, no way do I want to deal with all of the updates. I choose "automatic" in order to keep "sanity" and let the flood come and sweep me away if it will. I accept that. For others -- who limit the extensions they take (and the browsers they have on their computer) -- it might be relatively easy to make an instant decision and no big deal. The choice should be with the user. And those users who have the background and knowledge to exercise it well are the ones who ought to be most concerned about having the option. And as I indicated, occasionally I have in the past and might in the future -- if I had the choice -- opt to review an update. Finally, users who choose not to take an update may risk losing security protection -- even if only a week or two while they test the waters to see what people are saying about the update before making a decision on whether to install it.
-
blackbird71 last edited by
I certainly think the option ought to be with the user. If one has the option, I can think there are two views on whether to use auto-update. Quite frankly, I just have no time to manually deal with automatic updates across the board (and if I tried to (if I added this additional work to my life) I think I'd have a breakdown :). Further, even if I see the update sitting in my inbox (for my decision on installation or not), it would be hard for me to have any idea whether it is harmful or not. In most cases, if I have the choice, I will, therefore, hell be damned, auto-update. (And I believe, probably 95 percent or more of users would choose that course). I do it with Windows, with my browsers and with extensions. I have on occasion been burned
...I use my computers quite heavily, and I believe in being largely in control of them and what they do. One of the major problems with auto-updates is that they occur at a time of the software creator's choosing, not the user's. This is one of the key problems that eventually turned me from a "bold' user into an "old" (experienced) user. The last thing I want, right in the middle of an intensive or critical computer operation, is for a piece of unrelated software to decide to auto-update itself - particularly if that involves rebooting. In the same vein, I want to be there at the computer when updates do occur to observe if any hiccups happen, especially upon a reboot, so using a task scheduler to delay auto-update to the dead of night has its own associated problems (assuming the software even allows scheduling its update checks).
The other major problem, of course, is that updates sometimes break systems. Most of the time, I wait about 1-2 weeks after an update is issued to test the waters about early-updaters' experiences... that's what Google is for. I'd much rather be a little late to the party with updates than risk crashing my systems the day of release. In the case of Windows, for example, every 2nd/3rd patch Tuesday or so, there will be reports of some patch that causes various users certain sometimes-major problems, and these can be easily avoided when I manually update. This has saved me from literally dozens of hiccups over the years. Likewise for AV program major updates, and so on.
Obviously, other computer users may have different thoughts about this. But I'm where I am on this because of hard lessons learned over the years. The most important lesson being that I, as a user, am the one who pays the full price of lost time and data when a flawed update is auto-pushed my way and crashes my systems or files. I simply will not accept that risk, and I know many others feel the same way. After all, they are my computers, not the software makers', and I am responsible for and in control of what is done to them. So I watch the effects of updates on others before committing my systems (and resources) to them. Hence it is essential that all my software have some means of disabling forced updates; that, or I will either find an "unofficial" but effective way to block updates or else remove the software off my system. Software creators can notify me that updates exist, but they must let me choose when or even if I will allow the updates to occur.
-
A Former User last edited by
You can also use an environment variable to make Opera auto-updates stop.
Go to Windows's System / Advanced System Settings, in the Advanced tab click the button to manage the Environment Variables and add one called "OPERA_AUTOUPDATE_DISABLED". Done.
-
lem729 last edited by
@rafaelluik
Do you know if that would include automatic updates for extensions (both the Opera ones, and the chrome ones that work in Opera)?
-
samkook last edited by
And which value do you put inside? Does it matter?
Edit: Putting the same thing inside does work at least so that's good.
It's less easy if we do want to update at some point than the command line switch, but it has the benefit of blocking updates however opera is opened. -
blackbird71 last edited by
You can also use an environment variable to make Opera auto-updates stop. ...
Thanks! That's one more tool for the toolchest...
-
tzo2k15 last edited by
The problem with the disable option from a shortcut is that this option only works when using the shortcut. If you open Opera from an email web link or link form another program (such as Keypass)then update will be active.
Which is precisely the reason why I am so opposed to auto-updating schemes that can't be turned off by a user from within a program itself. There may be a hundred legitimate reasons why a user wants/needs to block updating, but there are dozens of ways around his blocking unless it's done within the program itself, by design. Probably the most assured method of blocking Blink Opera currently is to change the updater file extension to .xxx or something similar... but even that has some risks attached (a repair re-install, for example).
Yeah, well it seems all custom functions are getting phased out/changed without our input, even opera's very own help page has inaccurate information....That, and the DRM built into this browser hereby marks my departure, and deletion of this program...
I will, however still remain here to see if this browser is made in the future for the actual user base rather than for administrators/office managers, as I don't use this browser to surf the Internet at work..
So goodbye Neo-Chromium, hello Vivaldi as my actual Opera!
-
starry001 last edited by
All this is great, but none of the suggested methods work in the MacOS version. Or if they do, I haven't figured it out yet.
I don't allow anything to auto-update, this is my machine, I will choose what to put on it, thank you. If I can't choose by official or unofficial methods, I won't use it.
-
starry001 last edited by
I found a way to disable the auto-update feature in the MacOS version of Opera.
Go to the Applications folder and click on the Opera.app while simultaneously pressing the "Control" key you will get a pop up menu. From that menu, select "Show Package Contents" which should be your second option.
Then a window opens with a folder that says "Contents." Open that and then you will see a bunch of files and folders. Open the folder that is labeled "MacOS."
Inside you should find a set of "exec" files. There is one called "opera_autoupdate"
I renamed that to "opera_autoopdate," (just one letter wrong so I can change it back if doing so did something bad) and then closed everything and launched Opera as usual.
When I opened the opera://about page the app said it was checking for updates for about 5 minutes then displayed "An error occurred while checking for updates."
The app behaves normally in every other way.
So apparently I accidentally found the way to disable updates on the MacOS version of Opera. I was just fooling around and didn't think it would work, but it does.
Hopefully this will help others.
-
-
starry001 last edited by
This is an three month old thread in the Windows forum. You must want to post in the Mac forum
I searched the site for help on disabling auto-updates, this is the thread I was sent to. I wasn't even aware there was any specification regarding OS, just a general discussion. I would have specified Mac OS in my search if I was provided the option to do so.
