Very long extension moderation process

[A Former User]

A Former User last edited by

I have two extensions waiting moderation for more than 4 months now, I have not received any message of what the problem is or when they will be reviewed. This is nothing serious. Both extensions were published by Chrome and Firefox in just a few hours. I do not know how to contact Opera to ask. It is really frustrating and exasperating.

[burnout426]

burnout426 Volunteer @Guest last edited by

@timerestart When you visit the Chrome store in Opera, Opera should ask you if you want to install https://addons.opera.com/en/extensions/details/install-chrome-extensions/ so that you can install Chrome extensions. Does your Chrome version of your extensions work fine in Opera?

[A Former User]

A Former User last edited by

O-Addons is fading away...

[A Former User]

A Former User @burnout426 last edited by

@burnout426
Not at all, because my add-ons need to use an auxiliary application for method 4, if I install the chrome add-on then in method 4 reboots chrome not Opera!!!

[burnout426]

burnout426 Volunteer @Guest last edited by

@timerestart

[phermium]

phermium last edited by

I've had an extension that I submitted back in Feb. I just kinda forgot about it until earlier this week because I had a few users request my extension be released on Opera (officially). I pushed another update and am still waiting for a response of any kind. Is there a way that I can find out what is wrong (if there is anything)? This has been a very difficult process compared to Chrome and Mozilla.

[A Former User]

A Former User @phermium last edited by

@phermium i am in same case, if you know something about what we can do please advise me. This is frustating, they don´t answer.

[A Former User]

A Former User last edited by

Guys, there is nothing wrong with your extension. I too have been waiting 9 months and it is now obvious that it isn't going to happen.

It is perfectly clear that Opera have stopped supporting extensions.

My advice is to tell people to use another browser, and don't waste your time porting your extension to opera (even though it only takes 5-10 minutes to do so, that is still 5-10 minutes you could more usefully spend doing something that might bear fruit one day)

[devartstaff]

devartstaff last edited by

Still in moderation for a last 6 months:
https://addons.opera.com/en/extensions/details/tmetric-extension/

[A Former User]

A Former User last edited by

Wow, this is disappointing - my Firefox extension is approved within a few minutes, my Chrome extension is approved within hours, having published an Opera version yesterday and wondering why it was live yet, I searched and found this thread.. it looks like I'm in for a long wait!

Can anyone tell me what subsequent updates are like - does it also take months to approve new versions of a previously approved extension?

I'm not sure I'll bother publishing here in future if it's really as bad as it looks like it will be.

[A Former User]

A Former User @Guest last edited by

@danhumphrey it seems like trying to provide extensions for Opera is pointless.

[A Former User]

A Former User last edited by

I've been trying to get them to make the updated version of Metamask available, but they're totally unresponsive. The version on Opera is 3.14.1, while other browsers have 4.9.2, which has more functionality.

The Metamask people submitted the upgrade some time ago (though I don't know exactly when).

You get the impression that Opera is a somewhat amateur operation.

[A Former User]

A Former User @Guest last edited by

@rklamp they certainly aren't taking extensions and extension developers seriously. We take time to develop, test and publish an extension to support the Opera browser and they ignore us and fail to review and approve them - it's pretty disrespectful.

[igorjerosimic]

igorjerosimic @Guest last edited by

@danhumphrey For updates it used to be couple of days, now it's months.

[A Former User]

A Former User @igorjerosimic last edited by

@igorjerosimic what a joke! Thanks for the update.

[A Former User]

A Former User last edited by

6 months also. No reply. It's a joke.... lol

[A Former User]

A Former User last edited by

I checked dates - update to previous post. It's 9 months in review. No response at all.

[A Former User]

A Former User last edited by

What a waste of time, I give up. I have deleted my extension - I'm sticking to real browsers.

[tprockow]

tprockow Opera last edited by tnowak

Hi all,

to shorten publishing time and deal with the long moderation queue we will introduce soon auto-moderation process. With that change you will be able to release your extension quicker and gather feedback from real end users.

Right now we are in testing phase, so please help us to improve it and adjust for yours and ours needs.
Please submit your extension or update existing one and you will see if your extension will pass auto-moderation. While preparing extension please keep in mind acceptance-criteria and give us as much information as possible like link to privacy policy or license. Please use as less permissions as possible, rethink if you really need eg. access to all data on all websites. We will calculate reputation points for your extension and content of manifest file is a part of that calculation.

When internal testing of auto-moderation will pass our expectations, we will make it publicly available during incoming weeks.

Thank you for your support.

[A Former User]

A Former User @tprockow last edited by

@tprockow That's very good to know.

I went ahead and tried going through the upload process but always got into the queue. I went as far as deleting my extension entry and trying with a new one (since it was never published in the first place, anyway).

An annoyance: the displayed warnings are really off the mark and can easily be bypassed.

• As in, just because I have an svg in my extension, it complained about http://www.w3.org/2000/svg not being in the manifest.

• Because I'm using Rollup as a bundler and support other browsers, I don't have chrome.notifications directly in the bundle — it shows up as const t = (chrome || browser); t.notifications.create(...), so Opera complains that I'm not using any of the requested permissions. Adding a chrome.notifications.get || chrome.storage.local.get; anywhere is enough to suppress it.

• I had https://*.domain.com/, so it complained that https://specific.domain.com/ wasn't in the manifest.

• I added https://specific.domain.com/, so it complained that https://specific.domain.com wasn't in the manifest (and this url was never hit anyway! it was just in the code to create links!).

I'm really only going through these because some users have been dying to have my extension on Opera, but, as a completely free extension with zero upsides for me, there's just no justification for trying to get into this browser if this process isn't improved.