This is weird. I have an extension that is not available through the webstore because it's marked as private and is still pending review. However, I see the weekly users count increasing.
When the counter was at 1, I thought it was somehow tracking my own usage of the locally built .crx extension because the manifest contains the public key. But now it's at 10?
Is there some kind of accidental public link to pending extensions that I don't know about?
When you published your item as private that means only the trusted testers you set could see and install your extension. Besides that, the team in Google which handles the manual review and marked your item as Pending Review (maybe due some policy violation) could see and install your extension ether (probably for testing). Those status data would be counted as well probably. To my best knowledge, there's no kind of accidental public link to pending extensions like you said.
Related
I developed an extension for VS Code helping users manage their services in Azure. I found that some of our extension users were not aware of the new features after the extension was upgraded. Is there a way to show extension's release note automatically e.g., a popup window or a new opening tab after users upgraded their extensions?
The simplest (no more than 10-20 lines of code) you can do is (even if no VS Code API),
When the extension initializes, check if a file SHOWED is in the extension folder.
If not, pop up and notify your users of the release notes. These are typical functions in VS Code API.
After the notification, generate a zero length SHOWED file there.
Since every extension updates move to a new folder where no SHOWED file exists, your code can always notify the users with release notes again.
When I tried to download load runner free trial its asking for business email. how to download the setup?
This is an issue you need to take up with Microfocus. Keep in mind the license for the evaluation version is not for production use.
As a commercial tool, the vendor expects that at the end of your trial, if the tool meets your needs that you will have the means to purchase it. They6 will want to have salespeople follow up. Having a public email prevents that type of activity in most cases.
I know this looks like a dumb question, but I just found out that, last month, something terrible happened to my GitLab instance: someone signed up on it and became admin himself, without my invitation, as I was the only administrator. So he wiped off every internal and/or private project inside of it, groups too (and I don't even know whether he had stolen all of them before erasing or not, I'm worried because they were proprietary code). How did it happen? Does this have anything to do with, since the version was CE-13.3.0? If so, would version upgrading be enough to be safer, or should I make some particular configurations, such as disabling sign up page?
It is best to follow "GitLab instance: security best practices", which does include indeed:
Ensure open sign-up is disabled on your instance.
Open registration is disabled by default on self-managed instances with GitLab 13.6 and above installed.
If new sign-up is enabled and your instance is open to the internet, anyone can sign up and access data.
Administrators who would like to further restrict access on their instance can follow our documentation on how to configure user access.
Regarding the CVE mentioned, follow also "Action needed by self-managed customers in response to CVE-2021-22205", in your case: "CVE-2021-22205: How to determine if a self-managed instance has been impacted" (unless the log events have been wiped out as well).
I have a couple of months using Google Chrome Web Developer dashboard. Everything was very normal, publishing an updated version was taking around 30-40 mins, now that I added a few elements to my extension such as popmotion.js it keeps requiring manual revisions and my extension gets into "Pending for Review" state for so long.
My question is: Is this caused by something I could have done in the code? Is it possible to get rid of this condition that keeps telling Google's services that my extension needs to be manually reviewed?
Thanks in advance!
According to this link, Pending review means the Chrome Web Store automated systems have flagged your item for manual review.
Some of the reasons an item could be flagged for manual review include:
The item may have an NPAPI plugin, which requires a signed agreement from you. Check your email account associated with the item for an agreement notification from our abuse team.
The item is suspected to contain or to be distributed by malware or unwanted software.
The item is suspected to violate one of the developer program policies.
The item may have already been previously removed for a legal or policy violation, and has been resubmitted.
The item requests powerful permissions that require in-depth review.
Ok,
So about a year ago (I think) google went through a transition where they made Google Apps accounts "real" so we could use them in places like the Chrome Web Store. Unfortunately, prior to that happening I had written some extensions that were under the now conflicting account. So, now what I've got is a two accounts where the old extensions are under this conflicting account and anything past that date is under the new account.
So, it is time to upgrade some of these (old extensions), what I'd like to do is move the extensions under the apps account in a way that doesn't cause problems for the users. Does anyone know a way? It seems like the only option is just to place the extensions under the new account and delete them under the old account, but then I think all of the users would have to know to install the new one.
Thoughts? Has someone gone through this process?
EDIT: As #artur-nowak pointed out in the comments it is now possible to transfer extensions between accounts using this form.
If only your extensions were hosted outside Chrome Web Store (CWS) it would be possible to solve this by modifying update_url in manifest.json (so that extensions will start to download updates from another source). But they are not, and CWS doesn't allow you to modify the update_url param. Because of that, I believe you have two options left:
wait for google to add 'change ownership' function in CWS
or add your extensions to CWS again as a desired user and update the old ones to display a popup/notification "please update" with a link to the new version. Users should be more eager to update if you include some new features to attract them. Also, it will be less annoying from them if config will be preserved. To achieve this, export settings to bookmarks panel (it will be easy to access them) and import them in the new version of extension when it's installed.