Closed (fixed)
Project:
Geolocation Field
Version:
8.x-1.x-dev
Component:
Geolocation field
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
14 Jun 2016 at 10:26 UTC
Updated:
8 Jul 2016 at 11:54 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
pminffixed typo
Comment #3
christianadamski commentedHey pminf,
1.) As mentioned in your linked issue, submitting empty lat / lng values despite field being required was already fixed.
2.) The required empty field is highlighted as erroneous, so it's not like the user has no idea what's happening.
I agree the message is not as helpful as it could be.
Comment #4
christianadamski commentedDo you use the default widget to input your data?
Comment #6
christianadamski commentedAdded "#required" parameters to the lat/lng widget. It will now correctly state the field names that are missing, as well as indicate that little red *.
Comment #7
pminfSorry for the missing information. I opened this issue because it seemed to be fixed in version 7.x but not in 8.x. It might be related to the Geolocation Google Geocoder widget.
W've checked your last fix but it didn't work.
Steps to reproduce on simplytest.me:
You get the error message "This value should not be null." and the geolocation field is not marked as invalid (see screenshot).
Comment #8
christianadamski commentedPlease test again with the latest 8.x-1.x-DEV release. The 8.x-1.5 branch does not contain any of these changes.
Comment #9
pminfI've tested the 8.x-1.x branch on simplytest.me which equates to the 8.x-1.x-DEV release. Same problem here.
Comment #10
christianadamski commentedOoooh, we're talking about the geocoder widget now. Yeah ok, I was talking about the default one. Yeah ok.
Comment #11
christianadamski commentedComment #12
christianadamski commentedComment #13
christianadamski commentedComment #14
christianadamski commentedComment #15
christianadamski commentedAdded more appropriate messages for geocoder widget and HTML5 widget.
Comment #16
christianadamski commentedAdded tests as well.
Comment #18
christianadamski commentedComment #23
christianadamski commentedFailure is ok. I already committed this, so Patches do not apply anymore.
Comment #24
pminfThank you! Serverside validation now seems to work as expected. But what about clientside validation? If I don't set a value, I should not be able to submit the form (like required plain text or file upload fields).