Extension upgrade requires additional permissions...

[albertop]

albertop @mateuszr42 last edited by

@mateuszr42 No is not like that. When clicking on "go to extension", in the extension box there is some specific slider, with that is very simple to accept the new permission for the extension.
You don't need developer mode, this is for other stuff, and the download you've done could not be appropriate for you.
That switch, I've used it thousand of times, even there are extension that tends to ask permission repeatedly. Now I don't remember the exact text of the switch, but it is very simple, /if you read it/ with some slowdown and calm ^_^ don't be in a hurry and try to slowly read every line by every switch. You will surely see it.

[albertop]

albertop @DeggTSK last edited by

@deggtsk Button on the right of message, "go to the extension". Simple.

[albertop]

albertop @vlads111 last edited by

@vlads111 Button on the right of message, "go to the extension".
You have /not/ to perform an upgrade, but instead, to /accept the permission change/, so to let the browser to update the extension. In the box read every "switch" description, you will find it.

[albertop]

albertop @Draker last edited by

@draker Button on the right of message, "go to the extension". Simple.

[albertop]

albertop @perdigao1 last edited by

@perdigao1 If you have unknown extension, you better remove it!

[albertop]

albertop @xxkernljrxx last edited by

@xxkernljrxx update your browser to latest version. Seems they have fixed the permission problems. You better do that before ajll.
Any way, right of message there's "go to the extension" button. In the first ext box that opens, you should enable permissions for the extension to access the webpages, or, give to the extension additional permissions if required.

[misterdk]

misterdk last edited by

I was receiving this error and was able to correct it by simply modifying the shortcut and specifying "Run as Administrator". After starting the application the message was gone. I then reverted back to normal (not run as administrator). It has been working fine since. It appears that there is an extension somewhere that requires admin rights in order to initialize.

[shampoo]

shampoo @albertop last edited by

@albertop hey so i was reading through your message because i am also having this issue with Opera GX and i couldnt find where i could enable/add permissions to the extension? so do you know where that is I am using Opera GX version 76.0.4017.208 LVL 2. so if you could just lead me to where specifically i can enable these permissions because i have gone through every option here and cannot find it?

[perdigao1]

perdigao1 @shampoo last edited by

@shampoo Hi, if I remember well, you need to start the opera with the flag --show-component-extension-options.

If you have a shortcut on the desktop, it is probably better to create a copy of it, then right-click and choose properties, choose tab called 'shortcut', and in the field target add to the end the flag. I think this is the way to get it working and remove the annoying extension.

Good luck

[LIAMRADA]

LIAMRADA @albertop last edited by

@albertop there's no "switch" to read

[crispypotato]

crispypotato @rplaye last edited by

@rplaye I can't seem to update that. There's no update button

[Cyber-Gypsy14]

Cyber-Gypsy14 @shampoo last edited by

@shampoo I've got the same doubt. Somebody please guide us.

[crispypotato]

crispypotato last edited by leocg

Found the problem!

Hey! I've had this problem for god knows how long, and I found the solution, For me at least. Go to your extension list, as it always begs you to do, and find Anything that has an update button by it. For me, it was Google Docs. It needed an update. Click the update button next to it, and you're all done. For safe measures, after you click that update button, go to the top of the page and click that update button.

[mryeezy001]

mryeezy001 last edited by

When upgrading an extension, additional permissions may be required to ensure optimal performance. This could include permissions to access certain files or folders, create and delete files, or make changes to the registry. It is important to ensure that any permissions required are granted before proceeding with the extension upgrade. Failure to do so could result in the extension not being able to run properly or at all. It is also important to note that some permissions may need to be revoked after the upgrade has been completed. It is possible to check which permissions are required for any extension prior to upgrading it, and this should be done to ensure that the upgrade process goes smoothly.

[Norby123]

Norby123 last edited by leocg

[Possible Solution] I have Opera One( developer v. 101.0.4829.0) and I just got this notification a few days ago, and no matter how many times I went to the extensions, there was nothing to update, nothing to give extra permission to.

I added --show-component-extension-options to the shortcut of Opera, opened it with that, and then when I went to my extension, there was a new component on top, Aria. I updated it, - it required permission to access browsing history (jeeesus...), - and after restart, it seems to be fine now.

You can delete the --show-component-extension-options part from the shortcut once you are done, but I'm gonna keep it there just in case.

[ShaeClark]

ShaeClark @Norby123 last edited by leocg

@norby123 Thank you so much for this!!
That's what worked for me & now finally that stupid warning is gone!

[redochka]

redochka @Norby123 last edited by

@norby123 it worked too.

To avoid creating a shortcut, on mac, make sure to quit opera (no other instance running) then in the terminal:

open /Applications/Opera\ Developer.app  --args --show-component-extension-options

[tmark]

tmark @Norby123 last edited by

@norby123 That was precisely my problem as well. The solution helped.

[water-exalted]

water-exalted @misterdk last edited by

@misterdk thank you, you just helped me breathe easier

[elBigBoss]

elBigBoss @misterdk last edited by

@misterdk Actually I can confirm, by the moment, this solved it for me. It also applies for the new Opera One.