http://kiedynaurlop-konrad.appspot.com/ad/ is 404, i don't see any
problem. Have you setup app.yaml properly?
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com.
To
@Luca: Have you seen the list of supported Python libraries?
https://developers.google.com/appengine/docs/python/runtime#Pure_Python
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To view this discussion on the web visit
Solved the issue!
This was caused localy only be because the request used not 127.0.0.1 but
the name of my machine thus was creating a new session!
On Tuesday, May 22, 2012 8:32:19 AM UTC+3, savilak wrote:
I use BlobStore to store excel files as per Ikai's sample
(
Whats wrong with the datastore? Seems to be what its designed for -
storing data.
If its the 1Mb entity limit, surely its not very often that a paste
will be bigger than that. And when it is just break it into parts, and
have 'next part' pointer on the main entity.
While there are experimental
Since GAE SDK 1.6.6, my previously working code (GAE SDK 1.6.5) is not
working anymore. The problem is related to the creation of
UrlFetchTransport. I reduced the problem to the bare minimum in a
BadClassTest class;
When my BadClassTest looks like this :
public class BadClassTest {
I'd definitely use blobstore for pastes and keep a reference to that blob
in the datastore along with metadata you might have attached to that blob.
On Monday, May 28, 2012 9:56:13 PM UTC+2, Alex V. wrote:
Hi, i'm trying to figure out best way to do this. I basically want to
create a
Can you attach the testcase to an issue on the public issue tracker?
http://code.google.com/p/googleappengine/issues/entry?template=Java%20defect
Thanks in advance.
On Tue, May 29, 2012 at 2:11 PM, Koen Maes k...@koma.be wrote:
Since GAE SDK 1.6.6, my previously working code (GAE SDK 1.6.5) is
I will setup a minimal testcase and keep you posted when it's ready.
Thx for the follow up.
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To view this discussion on the web visit
I sometimes see this on dev_appserver when I use the datastore admin page
locally, afterwards I usually need to reset the dev_appserver. It doesn't
cause a problem on production, but I'll give Matt's suggestion a try.
On Monday, May 28, 2012 6:23:53 AM UTC-4, Amine Azariz wrote:
I am using
Hi Everyone,
Here I am trying to upload a file asynchronously to the blobstore. Below is
what I've done so far:
*html file*
form id=my_form enctype=multipart/form-data method=POST
action=/partner
input type=file id=my_file name=my_file/
/form
*js file*
Hello,
I already signed up for Google Apps to register domain statruth.com.
And i received a reply and call me to In order to fully activate your
account, you’ll need to verify ownership of statruth.com. For step by step
directions on how to do this, just log in to your Control Panel at
It's likely related to Google's multi-auth. Make sure you are completely
logged out of Google, then log into the one domain.
Another possibility is try different web browsers. This worked for me, but
probably because it changed login state.
I've seen this before from Google Apps. Something
BlobstoreUploadHandler will probably work best with
create_upload_url(/partner)
https://developers.google.com/appengine/docs/python/blobstore/functions -
that's what you want to set in form action=...
- try that and see if it works.
On Tuesday, May 29, 2012 12:41:36 PM UTC+2, Mohit
I get this error too. Because of what this error?
On 29 май, 04:13, Amy Unruh amyu+gro...@google.com wrote:
Eshe,
What is your app id? (You can email it to me directly if you like).
On 28 May 2012 14:49, eshe muta eshem...@dishcrunch.com wrote:
We're seeing this:
Server
I got confirmation from another user in the google-api-java-client group.
The workaround is to drop UrlFetchTransport and use NetHttpTransport which
seems to be supported nowadays on AppEngine.
see here :
https://groups.google.com/forum/?fromgroups#!topic/google-api-java-client/FJSsz5qo7pg
My
I implemented the same workaround. For the past two days, it worked. It
looks more elegant than I schedule another same job just for fail-over.
Thanks,
Will
On Fri, May 25, 2012 at 8:59 PM, weboo hidet...@gmail.com wrote:
I have same problem.
The cron job on dynamic backend instance does not
One additional consideration with Cloud SQL is that you only pay for the
instance while it is being accessed. If you only use your database for a
few hours per month then you will only pay for those hours (at $0.10 per
hour for a D1 instance).
Joe
On Tuesday, May 22, 2012 3:53:22 PM UTC-7,
17 matches
Mail list logo
