[Geomoose-users] feature editing in geomoose

[Bob Basques]

All, 

Sounds like there is a FORM value not being cleared between edits.   I'm not a JS programmer, but some sort of method upon submittal to set the fields all bank again needs to be executed when the form is submitted.  Somehow the previous values are being pushed through to the next edit cycle. 

bobb 



>>> "Gregory Roberts | Wendler" <groberts at wendlergs.com> wrote:


Hello all, 
   
I wanted to reply to this to see if anyone had come up with any other ways that this could be fixed. This is a problem that I have been dealing with for a while. 
   
Thanks, 
   
Gregory 


From: Jeffrey Schmitz [mailto:jeffreykschmitz at gmail.com]
Sent: Monday, January 17, 2011 5:48 PM
To:geomoose-users at lists.sourceforge.net
Subject: [Geomoose-users] feature editing in geomoose 

   
Hey everyone,

We followed the feature editing guide http://www.geomoose.org/docs/feature_editor.html and were able get features successfully added, edited and deleted from our database. The issue we are having is editing when new features are added with (or edited to have) blank fields. When you click to edit a field which has had a comments section left blank (for example), the field will be populated with the most recent comments field that was not blank and was edited. I realize this sounds a bit confusing, so here is an example:

Feature 1:
comments field: blah blah blah

Feature 2:
comments field:

Feature 3:
comments field: hahaha

If you first edit feature 2, the comments field will be correctly left blank.
If you edit feature 1 and then edit feature 2 the comments field will show up as blah blah blah
If you edit feature 1 then 3  then 2 the comments field will show up as hahaha

I'm guessing this is due to the fact that geomoose sees the comments field as null with a blank comment and thus, the most recent entry in the field persists (instead of filling it as blank).

To fix this, I have edited the identify.html file mentioned in the guide so that the edit link contains a space instead of nothing for any texts fields that are blank.

Like this:
'feature:comments' : '[comments] '

instead of this:
'feature:comments' : '[comments]' 

This seams like a hackish way to fix the issue to me, and I was wondering if anyone else has come across the issue. If so, how did you solve it? I assume this has something to do with how geomoose generates it's service input fields, and how it handles null values. I just can't figure out where this would be in the geomoose code.

Thanks!
Jeff   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20110128/b141fa64/attachment.html