Closed (fixed)
Project:
Drupad
Version:
6.x-1.8
Component:
iPhone app
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
4 Feb 2012 at 00:11 UTC
Updated:
23 Apr 2012 at 19:41 UTC
Drupad on iPhone crashes when loading some content creation forms from D6 site. CCK modules are not used consistently for each content creation form. Some forms that work include CCK extras etc. and others that do not utilize or utilize the exact same ones do not load and crash the app. So far I have not been able to commonalities.
I have attached a crash report from my iPhone.
| Comment | File | Size | Author |
|---|---|---|---|
| DrupadCrashReport.txt | 27.3 KB | el_reverend |
Comments
Comment #1
jchatard commentedHi sorry but your crash log doesn't give me much information.
Can you set me up a test account, that I can see it crashing by my self?
Please note, that I'm away for the rest of the week without Internet connectivity.
Thanks,
Jérémy
Comment #2
juliekj commentedI'm having the same issues.
Set up drupad on my test site awhile back and everything worked fine then, now I'm back to test some things before implementing drupad on another site and I can't edit existing or create new content....
It seems that the error has something to do with attached images - existing images. It want's to force me to always choose an existing image if I don't upload a new one.
This is the error from my log (sorry it's in norwegian, I've translated as best i can ;) :
Detaljer (eng: Details)
Type skjema (eng: Type schema)
Dato søndag, 26 februar 2012 - 3:40pm
Bruker admin
Plassering http://stallvikostre.jkjdesign.no/?q=drupad/content-forms/node-add/nyheter
Henviser
Melding Ugyldig valg i Existing images elementet. (eng: Message: Illegal choice in Existing images element)
Alvorlighetsgrad feil (eng: seriousness error)
Vertsnavn 80.212.177.176
Handlinger
Comment #3
jchatard commentedHi juliekj,
Sorry for the long delay. Have managed to identify any common pattern in the crash? A specific field? Any module?
If you are still experiencing this issue could set me up access to your site so that I can experience the crash by myself?
Thanks,
Jérémy
Comment #4
juliekj commentedSent you an e-mail with username and pword :)
-Julie
Comment #5
juliekj commentedI've managed to get it working sort of...
Unfortunatley not sure what I did.. tried a lot, and then suddenly it worked.
It still insists that I must attach an already existing image if I don't upload a new, if I don't I get the same error as desribed above. But when I attach an existing image it creates the new node.
Comment #6
jchatard commentedHi juliekj,
I just made a test on your site with the credentials you gave me.
I can reproduce, and I think I understand the issue.
It seems to work fine without uploading an image when you choose in Existing image the value - None -.
Which make my think that the issue is: Drupad should by default select this value - but doesn't and thus generates the illegal choice?
Can test this on your side, let me know if this is the issue, and tell me how you managed to configure your image field? Which module, which settings, etc. so that I can do this locally and make Drupad aware of this config).
Thanks,
Jérémy
Comment #7
juliekj commentedyes, that seems to be it.
Module: Image 6.x-1.1 & Image Attach 6.x-1.1
Not sure what settings you are after though...
Image module settings or Image attach settings on the node types?
Comment #8
jchatard commentedBoth :-)
So that I can reproduce this behavior on a local setup to deal with this issue.
Thanks,
Comment #9
juliekj commentedIs this what you need?
Image file settings
Default image path: images
Maximum upload soze: 2000 KB
Image sizes:
(Label - operation - width - height - link)
Original - Scale image - - - same window
Thumbnail - scale image - 150 - 150 - same window
Forhåndsvis - scale image - 640 - 640 - same window
Profilbilder - scale image - 200 - - same window
Image attach: enabled
Comment #10
jchatard commentedOh ok, I thought there were more options with those fields.
Will try this out!
Comment #11
jchatard commentedFixed in 1.14, submitted to Apple for review;