Unpublishing an item pending inline install review leaves the item in limbo

51 views
Skip to first unread message

j...@currentlyhq.com

unread,
Feb 23, 2014, 10:21:18 AM2/23/14
to chromium-...@chromium.org
I've published an update to one of my extensions that included turning on inline installations. I realised afterwards that I'd made a mistake in the listing so I returned to the developer dashboard in order to make an amendment. The only option next to the listing was "Unpublish", presumably because enabling inline installation has triggered the manual review process. I thought I'd try clicking on unpublish to see if this would allow me to edit the item and republish it, but alas I now have no options at all.

Would it be possible to have my extension removed from the review queue so I can go back and make these changes? The extension ID is: jnfmgpfpmmjdfadmnjeppjfjmnhnckcc

Lukas Zugge

unread,
Feb 23, 2014, 10:28:19 AM2/23/14
to chromium-...@chromium.org
That is a very good proposal, at least while the manual review flagging is still so unclear. So please Googlers: Make it possible to update an item that is in the review queue as long nobody at Google looked at it yet.  

j...@currentlyhq.com

unread,
Feb 23, 2014, 10:33:54 AM2/23/14
to chromium-...@chromium.org
Thanks Lukas. It's especially concerning to me that the manual review process disables the ability to edit an item (even if you then unpublish it) because I now don't have control over whether the mistakes I made in my listing will go live or not.

Andy Mitchell

unread,
Feb 25, 2014, 10:44:53 AM2/25/14
to chromium-...@chromium.org
Thanks for letting me know you posted this J. 


Currently, I have no control of an extension customers pay for, no alternative way to provide it to them (since Chrome 33 forces everyone to use the Webstore - which is now locked up), no way for new users to install, and I'm extremely concerned it may disable it for existing users (although this hasn't happened yet, fingers crossed it won't). 




On Sunday, February 23, 2014 3:21:18 PM UTC, j...@currentlyhq.com wrote:
Reply all
Reply to author
Forward
0 new messages