@tnowak It seems to me that life would be much easier for everyone if Opera would simply close Opera Add-Ons and build support for the Chrome Web Store into Opera. Why not let a 800 billion dollar corporation with 98,000 employees do the moderation work and store maintenance for you - for free? It works for Vivaldi. It works for Brave. Without Opera Add-Ons, Opera staff could spend more time draining those bug queues – or taking longer weekends

It sure would be infinitely easier and cheaper for both developers and Opera if the Opera team would allow extensions to be loaded from the Chrome Web Store as the Vivaldi and Brave browsers do.

Here is my math:

Cost for developers to submit and Opera to review extensions = X
Cost if we just used the Chrome Web Store = 0

X divided by 0 = ∞

Does anyone see a mistake in my math?

17 days after submitting, an update to my extension was still not published. So I opened its page and, in the General tab, switched on the checkbox I want my extension to be available for auto-publishing. Also, in the Conversation tab, I entered a remark explaining the situation and asking if there was anything else I needed to do to make the new checkbox setting effective. Although I have not received a answer to that question, my extension was published 59 minutes later. Lesson learned: Switch on the checkbox I want my extension to be available for auto-publishing.

I wonder why Opera exposes that checkbox. The accompanying text implies that not all extensions will meet the criteria for auto-publishing. But it does not cost anything to try, other than some CPU time on Opera's server, so I wonder why the system does not just try auto-publishing automatically for all extensions and updates? That must be the way the Chrome and Firefox stores work – my Chrome and Firefox extensions are always approved within minutes.

I must update my June 19 post to report that I am now having the same problem as the rest of you all. I submitted very minor updates (1 or 2 lines changed) to my two extensions on August 25 and am now still waiting after 31 days, with not even any communication. Very sad.

(I too get instant reviews for all other browsers. Chrome's reviews are instant, Firefox' are instant for me because I distribute on my own, and Vivaldi's are instant because they use Chrome's Web Store.)

@burnout426 said in Very long extension moderation process:

Also, Opera can install extensions from chrome.google.com/webstore.

Are you sure of that? The last time I checked (which was years ago), Opera did not support installs from the Chrome Web Store. Vivaldi does. Edge does. Brave does. So now, Opera does? When did that change?

17 days after submitting, an update to my extension was still not published. So I opened its page and, in the General tab, switched on the checkbox I want my extension to be available for auto-publishing. Also, in the Conversation tab, I entered a remark explaining the situation and asking if there was anything else I needed to do to make the new checkbox setting effective. Although I have not received a answer to that question, my extension was published 59 minutes later. Lesson learned: Switch on the checkbox I want my extension to be available for auto-publishing.

I wonder why Opera exposes that checkbox. The accompanying text implies that not all extensions will meet the criteria for auto-publishing. But it does not cost anything to try, other than some CPU time on Opera's server, so I wonder why the system does not just try auto-publishing automatically for all extensions and updates? That must be the way the Chrome and Firefox stores work – my Chrome and Firefox extensions are always approved within minutes.

@tnowak It seems to me that life would be much easier for everyone if Opera would simply close Opera Add-Ons and build support for the Chrome Web Store into Opera. Why not let a 800 billion dollar corporation with 98,000 employees do the moderation work and store maintenance for you - for free? It works for Vivaldi. It works for Brave. Without Opera Add-Ons, Opera staff could spend more time draining those bug queues – or taking longer weekends

It sure would be infinitely easier and cheaper for both developers and Opera if the Opera team would allow extensions to be loaded from the Chrome Web Store as the Vivaldi and Brave browsers do.

Here is my math:

Cost for developers to submit and Opera to review extensions = X
Cost if we just used the Chrome Web Store = 0

X divided by 0 = ∞

Does anyone see a mistake in my math?

No, @iann0036, as I said at the beginning of my post, I think 32 hours is good. I think I got it good.

Good news - My two extensions got published 32 hours after submitting updates. It may have helped that I submitted a Comment containing a short (~50 words) change summary with each one.

Well, my two extensions were also published today, after 35 days.

The first one was published 45 minutes after the extension of @nirantali, at Sep 29 2017 9:28:19 AM UTC, and the second one was published 3 minutes later, at Sep 29, 2017 9:26:13 AM UTC.

Thank you to the Opera Extensions Team.

I must update my June 19 post to report that I am now having the same problem as the rest of you all. I submitted very minor updates (1 or 2 lines changed) to my two extensions on August 25 and am now still waiting after 31 days, with not even any communication. Very sad.

(I too get instant reviews for all other browsers. Chrome's reviews are instant, Firefox' are instant for me because I distribute on my own, and Vivaldi's are instant because they use Chrome's Web Store.)

I submitted updates to my two extensions on Saturday 2017-06-17. They were approved and published two days later, on Monday 2017-06-19. "It works for me."

Thank you, @shwetankdixit. Maybe your changes have not been published yet, but in the documentation I still see this path:

/Library/Google/Chrome/NativeMessagingHosts/...

That should be corrected to:

~/Library/Application Support/Google/Chrome/NativeMessagingHosts/...