Tomasz Babczyński

Googlemaps have more to do with JavaScript than PHP. Anyway, in the current version, if the user has valid google api key, the maps should work properly. I mean, the version after jQuery update from the last year. I wish, I have more time to migrate maps to leaflet engine ... T.B.

The user can set, in gedcom options, the format of calendar but the only additional calendars are French revolutionary, Jewish and Hebrew, there is no option to set Julian and Gregorian calendars to display simultaneously. Ah, wait, I've checked just now that if the calendar format is set to "julian", it displays dates as "23 lipca 2018 (10 lipca 2018)". So, go to administration/manage gedcoms/click 'edit' near the "configuration file", then check the "calendar format" (the 6th option) setting it...

It looks like Julian/Gregorian calendar. Don't you have dual calendars turned on?

Terry, I don't like the code of RA so if you changed it to something more readable, you are welcome. But try to remove as much as possible strange/abandoned/deprecated libraries turning them into up to date jQuery with jQuery UI. Yes, I know, jQuery is also not the rocket science but it is relatively small and handy in use. T.B.

I will look at these issues. But, sorry, not now. First I will finish the upgrade of js libraries (this should address the issue 4). The "developement only" issue is google api problem; actually their current policy. If you buy access to google map api and provide proper key - maps will be displayed correctly. It is the reason why I'd like to migrate from google maps to OSM in the future. T.B.

Me either. Now I'm working on removing dependency from legacy libraries like prototype, behavior, scriptaculous and very old jQuery. About 80% of the work is done. Next, the google maps migration to leaflet is in my mind. Google analytics... Maybe some day. But not in the near future.

Huh, the problem is more serious than it appeared. And I suppose, the leaflet will be affected as well. The problem is in prototype.js library. It is no longer developed and as one gay said "its successors successor is obsoleted now". If I commented out the script calling the library (in js/prototype.js.htm), the maps works again but probably the other things doesn't. To solve the problem, and maybe the others in the future, we should make the audit of the code, find the calls to prototype.js lib...

Yes, after sending the message I've noticed the same. In both Firefox and Chrome. The better idea than removing the line is to change it to: Array.from = Array.from || $A for a case of legacy browser without Array.from implementation. Are there such browsers in wild?