Publishing the latest version of my code while retaining the existing WebApp URL works well in Google Apps Script. The command is Deploy > Manage Deployments > Edit > New version > Deploy.
However, I always have to do it twice because it leaves the Description as "Untitled". I then execute Deploy > Manage Deployments > Edit > {paste in new description} > Deploy, leaving the version unchanged while resetting the Description back to the desired string.
Clearly this isn't a major issue, but it would be nice to know what I'm doing wrong.
Related
Purpose:
To be able to use clasp run on VS Code
I did...
followed this instruction. https://github.com/google/clasp/blob/master/docs/run.md
And I could successfully finish steps 1 - 4. As long as I know, I could get everything I was expecting.
Problem:
But on step 5, I got this error message below, check this screenshot.
screenshot
Error 403: access_denied
The developer hasn’t given you access to this app. It’s currently being tested and it hasn’t been verified by Google. If you think you should have access, contact the developer (xxxxxxxx#gmail.com).
Learn more
Request Details
The content in this section has been provided by the app developer. This content has not been reviewed or verified by Google.
If you’re the app developer, make sure that these request details comply with Google policies.
access_type: offline
response_type: code
redirect_uri: http://localhost:38159
client_id: xxxxxxxxxx.apps.googleusercontent.com
scope: https://www.googleapis.com/auth/script.webapp.deploy
Comment:
Does anyone know how to solve this problem? And thank you for reading.
Environment:
OS: Ubuntu 20.04.4 LTS
OS Type: 64-bit
GNOME: 3.36.8
Windowing system: X11
IDE: VS Code: 1.66.2
Node.js: 16.13.0
clasp: 2.4.1
Your project is still in testing; you either need to add the account you're trying to authorize as a test user, or set the project's publishing status to "In production" i.e. publish it.
Here's a video that shows you how: https://www.youtube.com/watch?v=x_NPvk0pk8g
The sidebar in that video isn't quite up to date however: I recommend searching for oauth in the top bar while having the appropriate project selected and clicking on OAuth consent screen.
Is there a way to restore previous Google Apps Script Editor Versions?
I accidentally deleted a big portion of my code in the Google Script Editor. In the new editor, I do not see a way to restore versions.
In the old editor, I can go to File > See version history (please see image).
Unfortunately, this only goes back a few hours.
Is there a way to retrieve a version from yesterday?
TIA
You can try reverting to the legacy editor to access your script revision by clicking on the "Use legacy editor" button on the top right of the Apps Script window.
Even if you weren't already using clasp, when you created those versions, you can still use it now to retrieve the code for them. However, this only works if you created an explicit version of the code, under deployments, even if you didn't actually deploy them.
First install NPM, then:
npm i #google/clasp -g # install clasp
clasp login # login to your Google account
mkdir some_folder
cd some_folder
clasp clone <ScriptId> # replace <ScriptID> with your script id
clasp pull --versionNumber X # replace X with version number you want
I write basic web apps for my personal use and am only one step above a noob. The current version of my web app runs a different code.gs file than the one that is saved, i.e., the code.gs file that comes up when I open the project from the apps script dashboard. I can't find the currently running file in the previous deployed versions in the Manage Deployments dialog. It seems to me that a version is running that is kind of inbetween deployments. Is there a way to display and edit the file that is currently in use by the web app? Thank you.
To run the latest code you can create a new version.
On the new IDE you can't see the previous version code, on the old IDE if you go to File -> See version history.
But to run the script you have on the screen on the new IDE, you have to deploy a new version.
I have a simple source-to-image deployment in Openshift (some webpage with HTML and Javascript). The deployment was built from an Apache template, fetching code from a repository in GitLab.
Now there is a new release of the webpage at GitLab that must be deployed. I tried to redeploy, but Openshift fetches again the commit initially deployed, not the HEAD. How can I force Openshift to fetch the HEAD of the repository?
The trick here is to do a re-build, instead of a re-deploy. Only the re-build fetches the most recent source from the repository. One must go to Builds > Builds, select the one corresponding to the deployment and then click on the Start Build button:
I have my site up and running, but because of number of changes, i decided to publish an updated version. Before doing so i have made backup of my files and databases on the host, just in case.
Now this is what i did: Publish Nop.Web used FTP, configuration is set to release and from file publish options checked Delete all existing files prior to publish, as i was publishing to the same folder wwwroot. After publish was completed NopCommerce installation appeared (btw i would like to use the same db i used before) even tho settings.txt from the project I was publishing had the correct string path. I tried 2-3 times to pass the installation with no success (error: One or more sequence... something like that), checked settings.txt on the host and it was empty (no idea why), but i just edited it with the string path.
Now installation is gone i have my site running again with all the products and user information (i assume that means string path to db is good), but my theme is reseted to default, like all my changes to it (footer links, background, logo, favicon..etc etc) only thing that stayed as it should was the nivo slider widget that has the correct pictures displaying on this 'reseted' theme.
Checked General settings for theme settings if its the correct theme selected.
Also i have noticed this, i assume with those 2-3 unsuccesful install tried i have made some changes in db
http://i.imgur.com/wfXQYj6.png
Any suggestions how to sort this whole thing, before publishing i was running my site locally and it was good, i have backups of db and files(ones that i used before this publish)
I am using Nop version 3.4 and arvixe hosting. Sorry for my long post but i wanted to describe my steps and error as detailed as possible.
Thanks for reading and looking forward for your suggestions about this.
I haven't tried publishing features of NopCommerce version > 3.10, but you can try a more "manual" approach to make sure that files are properly updated on the server.
In short, you get files from your local machine which are needed for the built website and you upload them to your website folder on the server. You can make a backup and empty the server website folder first.
I presented that approach in this answer:
How to deploy nopCommerce 3.5 to new server from source?
You can check this batch script to see which files need to be sent to the server. The script also includes some suggestions about what else you may need to do to update the website on the server: https://gist.github.com/dan-mirescu/c14cc72e3f8ecca988b7
For Publishing the NopCommerce Application website below is the step:
Step : 1 - Publish the Nop.Web project.
Step : 2 - Publish the Nop.Admin project.
Go to the publish folder where your publish created
Step : 3 - Cut all dll from the Administration and Paste all dll to bin folder which in main bin folder for whole project
Step : 4 - Copy two things from your source project and in App_Data folder Settings.txt and InstalledPlugins.txt which is not published in your publish file so paste this two files in your publish folder in App_Data. (You need to change the connection string in Setting.txt as per your database host).
Step : 5 - Now you need to copy whole plugins folder from your source folder (but remember this plugins folder you need to copy from the Presentation folder not from the main source where the solution file are there.).
Step : 6 - Now your publish have been ready.(now you can deploy on hosting server)