Exception thrown when adding location to tridas.object in meta data browser

ltrr-arizona-edu / tellervo

Desktop application for measuring, curating, and analysing dendrochronological samples

http://www.tellervo.org

GNU General Public License v3.0

6 stars 4 forks source link

Exception thrown when adding location to tridas.object in meta data browser #36

Closed brews closed 8 years ago

brews commented 9 years ago

Tridas v1.2.0 on Ubuntu 14.04

To reproduce:

Launch desktop client. Login to Tellervo server. Open metadata browser.
Select tridas.object (site) without location information in left-side treeview. Select padlock in right panel to unlock editing.
Open "Location" element in right panel. Select to edit "Location geometry". Manually insert location in pop-up box (lat: 37.933; lon: -109.8). Select "okay".
In metadata browser select "Save changes".
Boom goes the dynamite. (Get popup on internal error while accessing resources.)

tellervo-submission.log is attached.

brews commented 9 years ago

This might be a part of a more serious problem, or a separate bug:

I've gone back and looked at Elements that I've entered lat lon from GPX on bulk entry. These are entries where the values seemed to have been accepted. If I go back and find these Elements in the metadata browser, Location's lat and lon appear to be empty.

On this same Element, I can attempt to correct the missing lat lons by putting lat lon values into the field through the meta data browser (connecting it with GPX file waypoints). They appear to read correctly in the GUI and I can confirm this in the outgoing Element's XML. However, reloading the Element in the browser after this exchange shows no lat lon.

brews commented 9 years ago

On sites that had location added in previous versions of Tellervo, the location still shows in Meta Data browser. I'm just not seeing lat lon from new bulk entry, through.

brews commented 9 years ago

As a workaround I tried to change location of a sample by creating a series and then editing through the "metadata" tab. After editing location, XML for [1] element gives message code 998:

"PHP Notice - Trying to get property of non-object."

This looks like it might be a different bug?

petebrew commented 8 years ago

Problem caused by a change in namespace handling for GML tags.