Bug - non-standardized info won't save
As of the past week or so, when I try create a new individual (and occasionally when I try to edit an existing one) the date and place information that I enter isn't being saved unless it corresponds to a standardized location. I work with a lot of rural villages in Poland, not all of which show up in the standardized places yet. I used to be able to enter the village name as it appears on a record (i.e. Rysiewko, Lipno, Poland) when I created an individual. Then after creating the person I could go back and choose the closest corresponding location (i.e. Lipno, Kuyavia-Pomerania, Poland) from the standardized database, while STILL leaving the original text I had entered with the more specific/correct information. Now, if I type out a non-standardized location while creating someone, it doesn't save. After the person is created, their birthplace field is blank, and the location I typed doesn't show up. This is a big problem--and really annoying because I had created several individuals with carefully typed out locations before noticing that none of those locations had saved. The same issue happens with dates. If I try to create someone with a customized date like "1756 or 1759" it won't save. The date field goes blank when the record is created.
A similar problem happens when I try to edit an existing person. I used to be able to save a standardized location, then go back and edit the text that shows to reflect the more correct location that isn't yet in the standardized place database. Now, when I choose edit, add a village name that isn't in the standardized database, and click save, the extra info I typed does NOT save. The record still only shows the original standardized location I had chosen.
This problem exists both in the app and the web browser version of the site.