Je ne recommande pas

Hi @alankabout,

Thank you for getting in touch and letting us know of your experience, we do appreciate the feedback.

I suspect this is an issue with the translations specifically, which are community driven, however there are two versions of the translation files. The version we ship within the plugin which are based on submissions directly to us, and the global community version which is maintained by the larger WordPress community.

Unfortunately, we do not control these directly, which is why we ship our own version of the translations included within the plugin. If you’re open to reaching out to us on our website, I’d be happy to work with you to get to the bottom of this and get the interface layout sorted out, you can do so here.

For users interested in helping us improve our translations, we do have a community project where we offer a premium license to anyone who submits an updated/improved translation for a specific language.

With regards to our documentation, we recently updated large portions of our documentation, and we are always working towards further improvements, if you had trouble with a specific document please let us know and I’ll make sure this gets an update as soon as possible.

It’s also worth mentioning, we do not have the ability remove any reviews, which is to say we did not remove your earlier review. If it was removed, this would have been done by the ww.wp.xz.cn team, and to my knowledge would only be as a result of breaching their community guidelines.

If you are open to contacting us directly, I’d love the opportunity to discuss these issues with you a bit further.

Hi @alankabout,

Of course, happy to help clear things up in anyway I can.

I suspect something is wrong with your customization scripts or perhaps a conflict as play here, as we did not remove any events with V10, we still provide full access to all API’s including the underlying Google Maps library (or any of our other map engines/presets).

If you have scripts which use those events/controls and they are not working, I’d really like to take a closer look, if you reach out here: https://wpgmaps.com/contact-us – Ask for me by name and my team will assign the ticket to me, I’m sure we can get things back on track.

To confirm, we still fully support full control via the JS library, we have more events in V10 than we had in V9 and we have additional map engines, each with their own API layers and access. What our system does (and has done since V8) is abstract logic between engines.

That is to say, if you want to control zoom via JavaScript, you can use our internal API instead of Googles library directly, and the script will work even if you change map engines at a later stage. With that said, we do not remove any of the native (Google/OpenLayers/Leaflet) API’s and they can also be easily accessed instead.

The only note here is that you should access these API via our internal layer (WPGMZA.maps[0].googleMap as an example). As this will lead to more cohesive code in the long term.

Is it possible your scripts are very old? Possibly from before V8? In those versions the events were not standardized yet, and we moved towards this in V8/V9. We only continued to expand this in V10 as shown by our new customization documentation.

For the sake of full transparency please find a details list addressing each of your points below as well:

• Smooth Pan : This is available via internal methods, and direct on engine methods. The engine may decide not to smooth pan if the distance is very great, this depends on the engine
• Smooth Zoom : See above, this behaves the same way and we have many different methods available for this
• Click behaviour customization : Still fully possible with either an event listener, or a full onClick override, as preferred.
• Full JS API Access : Yes, full unrestricted access to both our internal WPGMZA core API and whichever underlying API you decide to use for mapping services, Google, OpenLayers, or Leaflet
• Marker Events : Yes, still fully accessible, and we have more than we’ve ever had (This is very important to us for developers). Your event structure seems incorrect for the latest versions. We now use standard event structures like “markerselect.wpgmza”, “filteringcomplete.wpgmza”. Legacy events are still available, but not recommend (since V8)
• Fully Customizable : Yes, again as we fully expose the underlying API’s you can achieve most things via some code layer. This might require PHP, JavaScript, or CSS, but every part of our core is fully extendable.

As part of our focus on making the system easier for developers to access and scale, we’ve just started up a new customization documentation hub here: https://www.wpgmaps.com/help/docs/customization-guides/ (Released with V10) which shows more real world examples of extension, it’s still early days but we intend on documented this further.

If you do have older scripts, which are no longer working, I’d be happy to help you work through these, in most cases moving to the newer structures will only benefit your project in the long term.