Tomasz Babczyński

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?

David, please check whether the file from the following link solves the issue. It is the newest available version of prototype.js file. It is actually file from 2015 but anyway newer than the file in PGV. https://ajax.googleapis.com/ajax/libs/prototype/1.7.3.0/prototype.js @canajun2eh - maybe this proposed bump to 1.7.3 version of prototype helps to solve or or at least workaround the issue until we change google map api to leaflet

@GaryT You have my hands. And my phpstorm. And my modest leaflet knowledge. But I refuse to migrate this part of code to anything before deep refactoring and moving all "mapping" code to one-and-the-only place. In my site now, the edit place page and places diagram page display grayed out maps while the personal 'map' card doesn't display map "oops, something went wrong...".

Ha, I've caught it. It is not google api issue but the CSS parser. Namely the class includes/classes/class_cssparser.php and the ParseCode(...) function in it. But I don't understand why does it trigger the error. At the end of the function $css var is not empty while it should be... T.

Garry, yes, I confirm too. In all themes. But in chrome debugger I have the following warning: "Indicate whether to send a cookie in a cross-site request by specifying its SameSite attribute" Because a cookie’s SameSite attribute was not set or is invalid, it defaults to SameSite=Lax, which prevents the cookie from being sent in a cross-site request. This behavior protects user data from accidentally leaking to third parties and cross-site request forgery. Resolve this issue by updating the attributes...

Gerry, it is a surprise to me, because I'm sure it worked some time ago. I don't remember which version of php I had back then. It is possible that 6.x or even 5.x. T.B.