Fixed
Status Update
Comments
du...@gmail.com <du...@gmail.com> #5
@srfarley - I'd recommend you use the "New Issue" link instead of scope-creeping an
existing issue and expecting that to work out.
existing issue and expecting that to work out.
v....@gmail.com <v....@gmail.com> #6
Deleting an entire app would also be a good way to delete a borked datastore, which
seems to be a common issue.
seems to be a common issue.
lu...@google.com <lu...@google.com>
da...@gmail.com <da...@gmail.com> #7
This is a feature request - the ability to delete an application. But several things
should be noted:
1. There is now 10 apps given per developer
2. You can re-use an App id
3. Deleting an existing datastore is a separate issue.
should be noted:
1. There is now 10 apps given per developer
2. You can re-use an App id
3. Deleting an existing datastore is a separate issue.
du...@gmail.com <du...@gmail.com> #8
I want to change authentication options but it is not available so i need to delete
the application then recreate it. Hope both features will available soon.
the application then recreate it. Hope both features will available soon.
ja...@gmail.com <ja...@gmail.com> #9
fa...@gmail.com <fa...@gmail.com> #10
Being able to delete apps and rename apps is pretty fundamental. I wouldn't consider it to be low priority.
I'm trying to do some GAE development for clients, but I have almost run out of slots. When I was initially
playing around with the system, I was rather liberal with creating applications, and now with no way to delete
or rename them, I'm stuck with the application names I initially chose (and which I no longer want to use).
In the short run, it would be nice if there was an email address documented somewhere so we could ask for
the apps to be manually deleted or renamed (as is the case when more quota is needed).
I'm trying to do some GAE development for clients, but I have almost run out of slots. When I was initially
playing around with the system, I was rather liberal with creating applications, and now with no way to delete
or rename them, I'm stuck with the application names I initially chose (and which I no longer want to use).
In the short run, it would be nice if there was an email address documented somewhere so we could ask for
the apps to be manually deleted or renamed (as is the case when more quota is needed).
ko...@gmail.com <ko...@gmail.com> #11
As a workaround:
1. Create a new google account.
2. Add the new google account as a developer for the app you want to get rid of.
3. Remove your real account from the app.
I didn't try this yet, but it should work. Please let us know if it doesn't.
1. Create a new google account.
2. Add the new google account as a developer for the app you want to get rid of.
3. Remove your real account from the app.
I didn't try this yet, but it should work. Please let us know if it doesn't.
ph...@gmail.com <ph...@gmail.com> #12
yaakovsash,
I tried your proposed workaround. Unfortunately, when you give your applications
away to the other user, you don't get to create a new one.
I now have 9 apps on my dashboard, but I don't have the option to create another one.
I'm also a bit pissed off about the SMS authorization scheme they've introduced - it
may or may not cost me $5 because my cell phone company (Rogers in Canada) is evil.
It took me about an hour of messing around with their gateway and resending the SMS
to get my code. Not Google's fault really - but why build a dependency in on such a
brain-damaged third-party system?
App Engine is a pretty cool system that I'd like to promote as part of my
professional practice, but it's not clear to me that Google is positioning it as
anything other than a 'hobby' tool.
I tried your proposed workaround. Unfortunately, when you give your applications
away to the other user, you don't get to create a new one.
I now have 9 apps on my dashboard, but I don't have the option to create another one.
I'm also a bit pissed off about the SMS authorization scheme they've introduced - it
may or may not cost me $5 because my cell phone company (Rogers in Canada) is evil.
It took me about an hour of messing around with their gateway and resending the SMS
to get my code. Not Google's fault really - but why build a dependency in on such a
brain-damaged third-party system?
App Engine is a pretty cool system that I'd like to promote as part of my
professional practice, but it's not clear to me that Google is positioning it as
anything other than a 'hobby' tool.
gc...@gmail.com <gc...@gmail.com> #13
[Comment deleted]
ar...@gmail.com <ar...@gmail.com> #14
[Comment deleted]
ar...@gmail.com <ar...@gmail.com> #15
It seems a little silly.
This is one of the oldest issues.
This issue has never been addressed by anyone from google.
There is a published workaround that doesn't work.
The solution seems so ridiculously simple.
I can only assume that google can't delete applications, and that there is a limited
pool of slots for potential applications. Is this the case? *knock* *knock* google,
is anyone listening?
This is one of the oldest issues.
This issue has never been addressed by anyone from google.
There is a published workaround that doesn't work.
The solution seems so ridiculously simple.
I can only assume that google can't delete applications, and that there is a limited
pool of slots for potential applications. Is this the case? *knock* *knock* google,
is anyone listening?
xa...@gmail.com <xa...@gmail.com> #16
[Comment deleted]
is...@gmail.com <is...@gmail.com> #17
There is an interesting security issue arising when you reuse a domain name that has
been previously controlled by someone else. It's described in the "Domain
Contamination" article by Amit Klein
(http://www.webappsec.org/projects/articles/020606.shtml ). The idea of the attack is
to cause some malicious pages to be cached indefinitely.
been previously controlled by someone else. It's described in the "Domain
Contamination" article by Amit Klein
(
to cause some malicious pages to be cached indefinitely.
cb...@google.com <cb...@google.com> #18
It's also a deterrent to domain squatting. With only a limited number of apps, it
doesnt make sense to 'take' domains just because you can - in case you might want it.
doesnt make sense to 'take' domains just because you can - in case you might want it.
no...@googlemail.com <no...@googlemail.com> #19
Considering the two features, it would be nice to have a short period after creation
to enable deleting. In one case I set the wrong auth method for a domain and in
another I made a typo. The auth method is another issue but in the short term there
isn't a way around it which brings us to this issue and typo is human error however
if there was a period (maybe an hour after creation?) where it could be deleted this
would mitigate domain squatting and issues with domain contamination.
to enable deleting. In one case I set the wrong auth method for a domain and in
another I made a typo. The auth method is another issue but in the short term there
isn't a way around it which brings us to this issue and typo is human error however
if there was a period (maybe an hour after creation?) where it could be deleted this
would mitigate domain squatting and issues with domain contamination.
bl...@gmail.com <bl...@gmail.com> #20
I'm guessing removal is not as trivial as rm -rf but common now, you're Google.
ka...@gmail.com <ka...@gmail.com> #21
Ten slots does seem pretty meager especially when developers are just getting their
feet wet. If they get to the point of wanting to actually deploy apps "for real" this
could be a real issue. I know this is still Beta (it is Google after all), so maybe
this will get resolved eventually. Meanwhile, I'm starring this issue.
feet wet. If they get to the point of wanting to actually deploy apps "for real" this
could be a real issue. I know this is still Beta (it is Google after all), so maybe
this will get resolved eventually. Meanwhile, I'm starring this issue.
ol...@gmail.com <ol...@gmail.com> #22
Please fix this. In particular I want one operation in the dashboard that deletes all
the versions of an application and its data. If I have to pick one of the two,
deleting all the data at once is more important.
the versions of an application and its data. If I have to pick one of the two,
deleting all the data at once is more important.
ol...@gmail.com <ol...@gmail.com> #23
[Comment deleted]
Description
possible to prevent that event from bubbling up and triggering another
handler as well (e.g. map zoom for dblclick).
google.maps.event.addListener(area, 'dblclick', function(event) {
// ...
event.stopPropagation();
});