You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if I open the Quick Edit screen and make a slight change and Save, or even don't change anything but click Save instead of Cancel, the plugin gives a geolocation error if I try to approve the submission. So, it looks like if any "save" function is performed in the Quick Edit, it requires a Geolocation check.
I'd like to propose that clicking Save in Quick Edit automatically perform the Geolocation check (as well as Saving) so that a two step process isn't required by admins.
The text was updated successfully, but these errors were encountered:
Or maybe better, only require the geolocation check (in code) if the meeting location changed. If only the time, format, etc. of a meeting changed, the geolocation currently in the root server should take precedence. Sometimes people move the map pointer to a specific entrance of a large facility to make it easier for people to find the meeting. A geolocation check would undo that by changing the the longitude and latitude to where Google things the address is.
Currently, if I open the Quick Edit screen and make a slight change and Save, or even don't change anything but click Save instead of Cancel, the plugin gives a geolocation error if I try to approve the submission. So, it looks like if any "save" function is performed in the Quick Edit, it requires a Geolocation check.
I'd like to propose that clicking Save in Quick Edit automatically perform the Geolocation check (as well as Saving) so that a two step process isn't required by admins.
The text was updated successfully, but these errors were encountered: