Leaderboard

Good day, everybody! Sorry for not answering in this thread. Going through some not so easy times here. And working on this module is out of my reach for now. More to that the leaflet site is not even accessible from Russia (this is where I am at) as the lib author is in Ukraine. You can guess why. But maybe I have got a way around. Just maybe you noticed that the module repo is under the FriendsOfProcessWire organization. I was hoping to gather a team of PW loving devs under this org and support some important but abandoned modules there. This plan didn't work out (yet?) but we can try to make it work. If someone here in this topic feels willing and capable to take care of FieldtypeLeafletMapMarker (at least for a while), please write to me a PM and we will decide how to go on. I was always wishing a more productive community cooperation around PW and just maybe it is time))) P.S. I am now out of town so might not answer quickly. But I will)

Experienced the same error ("Invalid LatLng object: (NaN, NaN)") with a freshly installed module just now. In my case it was caused by a legacy (?) Nominatim URL: The module uses https://nominatim.openstreetmap.org/search/?q=Berlin&limit=5&format=json&addressdetails=1&json_callback=_l_geocoder_2, but Nominatim responded with a 404 error. I had to remove the trailing slash from 'search/' in modules/FieldtypeLeafletMapMarker/Control.Geocoder.js, line 343. Change this line from: L.Control.Geocoder.jsonp(this.options.serviceUrl + 'search/', L.extend({ To: L.Control.Geocoder.jsonp(this.options.serviceUrl + 'search', L.extend({ Now the modules uses the correct Nominatim URL, in this example: https://nominatim.openstreetmap.org/search?q=Berlin&limit=5&format=json&addressdetails=1&json_callback=_l_geocoder_2 The map loads fine, with the initial marker.

@ryan now that NativePHP reached v1 we could build native mobile and desktop apps with ProcessWire if it supported SQLite 🤯🚀 How cool would that be???

I'm using a regular UIkit modal... Original theme: With the default theme the modal is vertically centered, which causes a weird glitch when closing it: As the UIkit docs mention there is a standardised way to center the modal: https://getuikit.com/docs/modal#center-modal. And as you can see there it will work properly if used properly. I don't know why the default modal is vertically centered with the new theme, but I know that adding these kind of visual "optimisations" causes problems. Could you please stick to default UIkit markup and concepts as much as possible with your overrides to avoid these kind of issues? Thank you.

From the start, I asked myself why I was somehow not completely satisfied with the display of the checkboxes as switches: We actually use switches quite heavily in some of our webapps, so I looked at the examples and therefore suggest making the “inactive” status brighter. This makes it easier to recognize the status of the checkbox. Below is an example of iOS switches. I also find it problematic when the theme color is red: To me, this makes the checkbox appear “false” even though it is “true”. Making the “unchecked” state lighter in color, also would help in this case. Below is an example of one of our web apps. There we chose to give both states a color: That makes it easy to understand the state of the toggle (checkbox).

We just discovered something funny: The design of the column width slider handle is from a galaxy far, far away, isn´t it? 😉