Why is it that the software developers who design FamilySearch think they are all knowing?
There are restrictions to being able to edit source dates and places within FamilySearch that have not been anticipated and there are also items recorded in indexed entries that are wrong but uncorrectable. When software designers enforce their limited ideas to restricted conditions (such as standard dates and places), some records become uncorrectable until such limitations are removed. For example, I find a relative who is recorded in an index entry of a christening record, but the child was actually never christened (see Josefa Petrine Jensen GD4V-SQ8). When one tries to point out the error, the software requires a standard date and a standard place when it is currently impossible to indicate there was neither a date nor a place! Also, I found a immigration index entry which indicates a woman is married when she is actually listed as a widow (wd) Maria Pacula 1913 New York, New York. There is currently no way to correct this. Also it is generally not wise to require exact standard place names when the user has little or no idea where the place actually lies, such as when there are more than one place names for a place in Galicia, where one place is now in Poland and the other is in Ukraine (and the user doesn't have enough experience how to determine which or where the correct place is). I have stated in years past that it is dangerous or at least unwise to FORCE the process of correcting place names because such is often as likely to produce errors as it is to correct them.