Turns out it WASN'T the state field... it was the fact that once the
state was present, my geolocating script kicked in on page load and
tried to get a geocode for the address.
That makes a lot more sense.
--~--~-~--~~~---~--~~
You received this message because
I just moved my Django stuff from Dreamhost to Webfaction, and have
been trying to track down a lot of weird problems since the move. One
of the oddest is this proxy error problem.
If the user attempts to update their profile, it throws a proxy error
if the "state" field is in the form. The templ
2 matches
Mail list logo
