You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: recreated it as I accidentally closed when adding a comment
Firstly - thanks for this, it was exactly what I was looking for!
I am trying to use it with my google apps gae account.
Firstly, I when I created the application on gae I had this set:
If your application uses authentication, anyone with a valid Google Account may sign in. (This includes all Gmail Accounts, but does not include accounts on any Google Apps domains.)
So clicking on the admin page asked me for a Google account, which I wasn't using. Anyway, I then added a google account as a collaborator, and then tried to login to the admin link from DryDrop using this account, which results in:
'Error: Server Error
The server encountered an error and could not complete your request.
If the problem persists, please report your problem and mention this error message and the query that caused it.'
So I recreated the app, and selected this option:
"If your application uses authentication, only members of this Google Apps domain may sign in. If your organization uses Google Apps, use this option to create an application (e.g. an HR tracking tool) that is only accessible to accounts on your Google Apps domain. This option cannot be changed once it has been set."
However, now when I click on the admin link for the Google Apps version of DryDrop that I have uploaded, I get:
"404 - Unable to process the page
I'm sorry for inconvenience
What you can do now?
Remember, what have you done before it broke?
You have probably syntax error in your custom site.yaml. Please double check it and possibly fix it. Or remove your custom site.yaml altogether.
Normally you would clear cached resources from admin section, but at this point, the admin section is probably unavailable.
Go to https://appengine.google.com, select this GAE project and navigate to "Data Viewer". Switch to Resource entity and delete all cached resources. Then try to refresh this page again."
In the Datastore Viewer, I couldn't figure out how to navigate to resources, (possibly because there are none of that type?), however with the 'by kind:' selector set to settings (the only option), I see one entry, which lists
Thanks for creating this, and hopefully this will be comprehensive enough to sort this out :)
Pre-edit: Worth noting that by manually editing the site.yaml and entering my github address, the site does display properly - however the admin section still doesn't work.
The text was updated successfully, but these errors were encountered:
Strange.. After mapping it to use my Google Apps www.mydomain.com, I can access the admin from that page (and the settings were reset, too). However id.appspot.com still doesn't work, so I'll leave the ticket open
Update 2
Also, not sure whether to open up a new issue, but with the Google Apps version that works from my www.domain.com URL, my git pushes are appearing in the dashboard, however they say:
is not affected by incoming changeset for
so I have to flush the cache before the page changes.
Note that new files uploaded to the repo update fine.
Update 3
Okay, more updates. The admin page of id.appspot.com now works - this changed after I added that url as a post-receive hook as well in GitHub.
Rather strange...
Update 4
Sorry about adding as individual comments - hopefully it won't repeatedly notify you. I have compressed all updates down to one comment.
Note: recreated it as I accidentally closed when adding a comment
Firstly - thanks for this, it was exactly what I was looking for!
I am trying to use it with my google apps gae account.
Firstly, I when I created the application on gae I had this set:
If your application uses authentication, anyone with a valid Google Account may sign in. (This includes all Gmail Accounts, but does not include accounts on any Google Apps domains.)
So clicking on the admin page asked me for a Google account, which I wasn't using. Anyway, I then added a google account as a collaborator, and then tried to login to the admin link from DryDrop using this account, which results in:
'Error: Server Error
The server encountered an error and could not complete your request.
If the problem persists, please report your problem and mention this error message and the query that caused it.'
So I recreated the app, and selected this option:
"If your application uses authentication, only members of this Google Apps domain may sign in. If your organization uses Google Apps, use this option to create an application (e.g. an HR tracking tool) that is only accessible to accounts on your Google Apps domain. This option cannot be changed once it has been set."
However, now when I click on the admin link for the Google Apps version of DryDrop that I have uploaded, I get:
"404 - Unable to process the page
I'm sorry for inconvenience
What you can do now?
Remember, what have you done before it broke?
You have probably syntax error in your custom site.yaml. Please double check it and possibly fix it. Or remove your custom site.yaml altogether.
Normally you would clear cached resources from admin section, but at this point, the admin section is probably unavailable.
Go to https://appengine.google.com, select this GAE project and navigate to "Data Viewer". Switch to Resource entity and delete all cached resources. Then try to refresh this page again."
In the Datastore Viewer, I couldn't figure out how to navigate to resources, (possibly because there are none of that type?), however with the 'by kind:' selector set to settings (the only option), I see one entry, which lists
"id=1 site.yaml wfrict.appspot.com http://github.com/darwin/drydrop/raw/master/tutorial 1"
Thanks for creating this, and hopefully this will be comprehensive enough to sort this out :)
Pre-edit: Worth noting that by manually editing the site.yaml and entering my github address, the site does display properly - however the admin section still doesn't work.
The text was updated successfully, but these errors were encountered: