I developed a Google Form add-on and tried to publish it in the G Suite Marketplace as private (only for my G Suite domain) by following this guide.
I did this more than 2 days ago and the add-on is still not visible in the G Suite Marketplace, but the guide says:
If you selected Private visibility for the add-on, the add-on should become available for use after a few minutes.
So I think there is some issue here.
Earlier in October, the guide was different as the publication in Chrome web store was also required. The new guide has no more steps to publish to this Chrome Web Store so I did not do this.
Here are some ideas of the root cause of my issue (the fact that it's not visible in G Suite Marketplace):
Chrome web store is still required (but the guide says it's no more required). I have some doubt as this guide has been changed a couple of weeks ago.
In G Suite Marketplace SDK, the "publish" tab is may be also required? But the guide explains only the "Configuration" tab. Is this "publish" tab now required?
The guide is wrong?
I need to wait more time?
My guess is that the root cause is number 2. I guess the "publish" tab is required but the guide does not require this
Edit
When I was typing this issue here, the user guide was updated. Now I see that it's again required to publish the app to the Chrome Web Store, this has just been added : "Step 5: Configure the Chrome Web Store listing and publish".
It seems the user guide has been updated again, there is no more step 5.
I manage to get my private add-on available as a domain app after "forcing" the configuration page to save new settings. Here is how.
After the migration, the configuration page was set up but the publish page only show this message
Please setup 'Configuration' tab before publishing.
But on the configuration page, the save button was disabled as all the fields have been imported from CWS.
To enable the save button, I only had to change the privacy policy URL with a new one and save.
After that, the publish page showed the classic settings and I was able to publish the add-on. It appears on the GSuite Marketplace Domain App a few minutes after that.
I hope it helps.
In addition, but you may have done it already, the project is attached to my organization in GCP and it is marked as internal-only
Related
I am deploying my site to Azure from VS 2017. After each deployment, I am supposed to clean the cache of my browser to get the latest version of the website (or use ctrl+f5 to ignore the cached content when refreshing). But, this is a problem for the end users.
This is a asp.net + react website. So, the client-side code is cached in the browser. I have WEBSITE_DYNAMIC_CACHE set to 0, but did not help. Any suggestions? Is there a solution to this?
In VS 2017 right-click on the project and choose Publish. Click on Configure, then make sure the box is ticked for "remove additional files at destination"
I don't have enough votes to post screenshots yet, sorry!
My formulas in Display --> visible seem to work while I am in Preview mode. But don't work when I access a Published version of the app.
Most likely it is somehow related to permissions configuration. In Preview mode you are always Admin. By default, when you create custom Deployment you are member of Admin role, but if you made some changes to default `Deployment' configuration it can result into the issue you are observing.
I am getting this weird error while setting up my cloud backend
when i deployed my app, the url Http://"app-id".appspot.com
is landing on this page
but the url http://1-dot-"app-id".appspot.com is lannding on the right page
everything else works and its not a welcome-file issue.
then in the developer console i tried to set the default version and it gives me a error.
They say its a temporary problem but i have tried this for 2 days...
Any suggestions ?
Found the solution after 3 days of googling and digging in settings.
This also works if your app engine project dosent have a default bucket.
go to the old developer console https://appengine.google.com/
goto main > versions and set the default version here.
the newer console didn't work for me !
Also,
goto application settings
scroll down completely till you see the title "Cloud intigration"
it reads: "Create a Google Cloud project as well as a Google Cloud Storage bucket and a new style service account for this application"
click create.
This option is not there in the newer console.
In my endeavour to gain use of the Youtube API I am required to follow the procedure defined here.
In this link there exists a Prerequisites section that states:
Register your application with Google so that it can submit API
requests.
This takes me here which is a page Titled: "Registering your Application". This page contains instructions stating:
To register a new application, do the following:
Enter the Google Cloud Console https: //cloud.google.com/console [hit my link limit LOL]
Select a project, or create a new one.
In the sidebar on the left, select APIs & auth. In the list of APIs, make sure the status is ON for the YouTube Data API v3.
In the sidebar on the left, select Registered apps.
I have done all of the above. I have also clicked on the project taking me to another page. I am however, unable to register the application.
My question to you is "Where do I find the "Registered apps" because it's not in the sidebar on the left.
Google even provide a video on the instructional page stepping you through it. Unfortunately the video appears to be for an older site.
I am running Firefox 25.0.1. and it doesn't work for me so any guidance would be appreciated.
Instead of Registered Apps, in new version you'll go Credentials under API's and Auth and create your keys there.
I tried everything to help you out but i couldn't find "Registered Apps" too. Have you ever tried "Credentials" ? I think it works for the same way.
They don't care much about updates i guess. That's why they did not renew the instructions and the video..
When I first created my Plone (4.1) site, I made a mysite.policy add-on to include some custom users and a custom workflow.
I need to make some corrections to both the workflow and the permissions. I updated the src to include these changes, but updating the package in through the Plone add-on manager (uninstall - install) does not work. As soon as I uninstall the status of all my entries switches to "local policy", so I cannot get the fine-grained status setttings back when I reinstall.
Also, the user permissions do not seem to change. Possibly because they were already created at set-up of the site. But I cannot figure out how to code a change to permissions versus a setup of permissions in the rolemap.xml. I assumed that whatever is in that xml is what rules my plone world, but that does not seem to be working.
So far I cannot find anything about this in the manuals and books I have at hand. Any hints how to solve this? Perhaps the only way to go about this is a series of manual changes through ZMI, but it is so much less elegant to do it that wat.
There's plenty of options. I'll try to describe a couple of them.
If your changes include only changes in Generic Setup profile of your site policy (./src/my/site/policy/profile/default/-files) and you don't want to automate the upgrade, you could simply update the profile-files and re-run those specific import steps for your policy:
Open ZMI (site/manage) for your site and look for portal_setup.
Select Import-tab when on portal_setup.
Select the profile of your site policy from Select Profile or Snapshot-list (the title of your profile is defined by the registerProfile-directive in configure.zcml or profiles.zcml of your policy product).
Click to select import steps for Role / Permission Map and Workflow Tool.
From the bottom of the page, deselect Include dependencies.
Click Import selected steps-button.
Go to portal_workflow-tool on ZMI and Update security settings, if your workflow update should modify permission in existing workflow states.
These steps should re-import only the selected import steps of you site policy product's Generic Setup -profile. Re-importing individual steps this way should be quite safe, but be careful: accidental clicks at portal_setup screens may have unpredictable consequences.
These steps can also be automated by defining something called Generic Setup Upgrade Step.
I hope that the default Generic Setup -profile of your site policy product includes metadata.xml with line <version>1</version>.
Update that line to <version>2</version>.
Open the zcml-file with registerProfile-directive and, after it, add
<genericsetup:upgradeDepends
source="1" destination="2" sortkey="1"
title="Upgrade my.site.policy (1 to 2)"
description="Upgrades my.site.policy's default profile from version version 1 to 2."
profile="my.site.policy:default"
import_steps="rolemap workflow"
run_deps="false"
/>
These steps should register such an upgrade step from the profile version 1 to 2, which re-imports steps rolemap and workflow (rolemap.xml and workflows.xml). You should be able to run the upgrade step from the Plone Site Setup's Add-ons-screen, where there should now be an upgrade button after your installed policy product.
As mentioned by #toutpt, the Collective Developer Manual has more examples on upgrade steps. If you have ever wondered, why it's recommended to use integers in metadata.xml, usually independently from the product's release version number', this is the reason :).
Any changes that need upgrade must be shown by increment the number in profile/default/metadata.xml (keep integer). Next you have to write an upgrade step. It will add an upgrade button in the addons control panel.
Please follow this tutorial to learn how to create an upgrade step: http://collective-docs.readthedocs.org/en/latest/components/genericsetup.html?highlight=upgradestep#upgrade-steps