Errors on 2.3 Beta

[emilyh]

Hi,
I'm not sure if this is what issues is intended for, but I just wanted to report some errors I got testing out the 2.3 Beta, in case this is useful. I get these errors when I open the Edit Entry page which has the google maps field type on it. Everything seems to be working on the field, but these errors are appearing at the top of the page.

EE v2.2.1 - Build: date 20110705

A PHP Error was encountered
Severity: Notice
Message: Undefined variable: lat_field
Filename: gmap/ft.gmap.php
Line Number: 149

A PHP Error was encountered
Severity: Notice
Message: Undefined variable: lat_field
Filename: gmap/ft.gmap.php
Line Number: 149

A PHP Error was encountered
Severity: Notice
Message: Undefined variable: lng_field
Filename: gmap/ft.gmap.php
Line Number: 150

A PHP Error was encountered
Severity: Notice
Message: Undefined variable: lng_field
Filename: gmap/ft.gmap.php
Line Number: 150

A PHP Error was encountered
Severity: Warning
Message: Cannot modify header information - headers already sent by (output started at /xxxx/xxxx/clients/ctaylor/system/codeigniter/system/core/Exceptions.php:170)
Filename: core/Common.php
Line Number: 405

Cheers, Emily

[objectivehtml]

Thanks for the feedback.

Do you have the setting enabled to pre-fill other custom fields with the latitude and longitude? It seems they may be blank and there may be an error. I haven't ran into this issue at all, but I have been upgrading the same installation a bunch of different sites to test. I haven't done a fresh install in a while, so this may be a good way for me to duplicate this error. As soon as I can duplicate I will certainly patch it.

Can you give you me a bit more information on the steps you did prior to seeing the error?

The next commit of the beta is a large re-write of the fieldtype codebase. Many enhancements are being made to improve the interface and API within the template. The goal is grant the user access to the entire geocoder response for each entry. I am still working out the logic, but you can expect a lot of improvement to the fieldtype in the very near future.

[emilyh]

Okay, I uploaded the fieldtype, installed it, then went to create a custom field of this type. I initially left the customize settings blank. When I went to create an entry using it I saw the errors posted earlier. I then went back to edit the custom field, entered content into all the custom fields, and saved that. Still got the errors on the edit entry page.

Hope this helps.

[objectivehtml]

Just wanted to update this thread. There is a new re-written fieldtype that is almost finished that addresses all these issues. There is a ton of new features, extendability, and even a new UI for I think is much improved.

I know this thread is a bit dated, but just wanted to post an update. If anyone is interested in the new fieldtype, check back shortly. The best place to contact me is on Twitter @objectivehtml.

[emilyh]

Good news. I'm in the last stages of development on a the site I was working on here and was just about to revisit this problem. Sounds like I'll have to turn the field back on and live with the errors until you release the update.

[emilyh]

Didn't mean to close this thread! Hoping you'll post here again when the update is out...

[objectivehtml]

I have an interactive demo of the new fieldtype. There are ton of new settings and options to make the map do different things. In the demo I have Waypoint Mode enabled, which allows to user to plot routes with waypoints (instead of markers).

I am shooting to have the beta branch of the plugin updated sometime this week to allow people to start testing stuff. If you need an immediate solutions, you can always try the latest v2.3_beta build. I'm not sure if it will do anything different or not, but it might be worth a shot.

Here is the demo
http://ee.saucepantest.com

[objectivehtml]

Just to let you know, I just updated the v2.3 beta branch that fixes this problem. Let me know if there are any more issues. Sorry for the delay.