Hey Peter,
I’ve given things a bit of a closer look but unfortunately have yet to come up with a solution. We can only spend a limited amount of time on issues like this, and I’m sorry for the frustration, but I’d urge you to ask your theme developer if there’s a way they can limit their JS from affecting the entire Array prototype and offering a solution that only affects their theme code.
I’m sorry Peter. Anything I could think of doing from our end would mean some extensive core plugin code modification, which is a horrible idea as it means that if you update the code, you’ll lose your changes – unless you go piecemeal and backup each change, then re-add them once you update one by one…
Our Maps-related JavaScript doesn’t use anything fancy about the Array prototype or anything customized about it to run correctly, so if the theme’s JavaScript is then modifying it and leading to conflicts elsewhere, the ball is mostly in their court to limit the scope of their changes.
Thanks for your patience Peter.