March 29, 2019 at 10:38 am #48969
Thank you so much, as soon as we have custom id’s we will send it you.
And regarding the matter of snapping the polyines to nearset road we are happy to wait, but we are in a bit of a hurry beacuse the project should be launched on Monday.
Once again thank you so much for hepling us, we are more than satisfied with your product 😀March 29, 2019 at 1:36 pm #48972
And if you know how approximately we would need to wait?
Thank you so much again.March 29, 2019 at 2:42 pm #48974
We won’t be able to accommodate any custom work for at least a couple of months at the moment – we’re extremely busy working on a new major release.
Please note this would also be subject to a quote.
If you have a developer you can work with, we’d be quite happy to point them in the right direction on how to do this.
Does that help?
– PerryMarch 31, 2019 at 4:24 pm #49021
We are almost done with connecting markers and polylines.
Can you set the code so that the polylines are connected to the markers?
Thank you for your helpApril 1, 2019 at 9:15 am #49030
Yes absolutely, we would ask that you firstly please correct your Google API issues on the site.
Could you please get that corrected and get back to us regarding the custom behaviour?
– PerryApril 1, 2019 at 10:00 pm #49050April 2, 2019 at 7:54 am #49057
We’re still seeing “You have exceeded your request quota for this API” at our end and a “For development purposes” overlay on the map at http://www.gspns.co.rs/mreza
Can you confirm whether or not you are seeing the same thing?
Unfortunately no polylines appear on the map whilst this message is showing, which would make it impossible to test any polyline/marker code. We’d need this out of the way before we can write that, sorry for any inconvenience caused.
– PerryApril 2, 2019 at 1:25 pm #49061April 2, 2019 at 2:37 pm #49064
Thank you for that, I can confirm your account is in Trial mode and is also in credit, so the billing isn’t a problem.
I can see that the API key in your Google Dashboard does not match the API key being used to load the Maps API on your site.
Can you please check you have entered the correct key in Maps -> Settings -> Advanced under Google Maps API key,
If you are able to share access with us so we can get this solved for you without any further back and forth, we would be happy to take care of this and any subsequent issues that could potentially occur.
– PerryApril 2, 2019 at 4:07 pm #49071April 3, 2019 at 9:40 am #49085
In that case, there must be some 3rd party software that is also enqueueing the API and causing this to happen.
Can I lastly please ask you to try the setting “Prevent other plugins and theme from loading Maps API” in Maps -> Settings -> Maps?
If that doesn’t solve the issue, can you please open a ticket at https://www.wpgmaps.com/contact-us/ , attaching this thread as a reference and asking to be put through to myself, please supply FTP details, and we’ll identify where else the API is being enqueued and remove that, allowing our plugin to load the API with the correct key.
– PerryApril 4, 2019 at 12:29 pm #49107
I did what you told me and everything seems to be OK with API now.
Can you now set the code so that the polylines are connected to the markers?
Thank you again so much for your help.April 4, 2019 at 12:53 pm #49108
I’m really sorry but we are still seeing the same thing at our end with the API error message.
Could you please share access to the site with us so we can see why this is happening. we’ll need to fix that before we can add the marker/polyline code.
– PerryApril 4, 2019 at 1:24 pm #49110April 4, 2019 at 3:16 pm #49111
I’m so sorry for the back and forth on this, I was looking in the wrong place there, I beg your pardon on that.
We’ve modified the code in the Custom JS plugin at your end and can confirm that is now working well in testing,
Unfortunately changes we’re making to your Custom JS are not being reflected. Are you running any kind of caching that might be causing this?
I’ve saved the Custom JS repeatedly now and the JS on the front end never seems to reflect this.
You must be logged in to reply to this topic.