Hi there
Sorry about that.
Please can you update to 8.1.2 (which has many bug fixes) and let me know if you are still experiencing issues?
Hi!
Unfortunately I have the same issue on my site, too. I use the plugin’s latest version 8.1.2:
wp-google-maps.min.js?ver=8.1.2:1 Uncaught SyntaxError: Identifier 'i' has already been declared
at wp-google-maps.min.js?ver=8.1.2:1
Any help would be appreciated!
Thanks in advance,
Thomas
@seiteneffekt please can you provide me with al ink to your map?
Yes of course. As I removed the map from the original page because of the JS error I added a temporary sub-page containing the map only:
https://www.ensecur.de/ueber-uns-datenschutz-besser-machen/map/
The same error occurs there, too.
I am currently at 8.1.2 and the map still is not showing.
wp-google-maps.min.js:1 Uncaught SyntaxError: Identifier ‘i’ has already been declared
at wp-google-maps.min.js:1
(index):388 Uncaught SyntaxError: Identifier ‘d’ has already been declared
at (index):388
same issue on another site. Uncaught SyntaxError: Identifier ‘i’ has already been declared
at wp-google-maps.min.js:1 website
Quick update: I just updated to 8.1.3, but the error still occurs.
Same here. Update didn’t help. Same error message
Hi All
It appears that the Instant.page plugin has released an update that stops any other plugin from using the variable i in their plugin thereby causing this error.
We have patched a workaround for this and 8.1.5 will have this patched in.
This will be available in the next 24 hours.
Not actually heard of instant page. Will the patch work for those of us who have the issue but don’t have that plugin?
@nickduncan thanks for your quick support!
@starhorsepax2 your page seems to use a plugin called “WP Performance Score Booster” which loads this file:
https://naturalresultschiropractic.com/wp-content/plugins/wp-performance-score-booster//assets/js/page-preloader.js
This is actually the instant.page script which is loaded on my site, too.
update to 8.1.5 didn’t help. Performance Score Booster still blocks the map with the same error messages. I tried refreshing the page but no luck. 🙁
On my site the problem was fixed with version 8.1.5 🙂
Thank you very much for your support!
Thomas
8.1.5 didn’t do it but 8.1.6 apparently did. Thank you!
