Not working since WP Geo upgrade to 3.3

Looks like that plugin only support Google Maps API v2 at the moment.
Are you using a shortcode or a tag in your templates?

You could try using the WP Geo Shortcode [wpgeo_mashup]
You can set attributes like [wpgeo_mashup post_type=”any”] if needed.
How close does that get to what you need?

If not you can temporarily try selecting to use the v2 API in the WP Geo settings, or failing that rollback to the previous version of WP Geo for the moment.

Hi Ben!
The short code did not seem to work so I selected v2 API which works fine.

Thanks!

That’s fine for now.
I’ll post request for the Mashup Plugin author to try to add v3 API compatibility.

Hi all, just released an update that should be compatible with WP Geo 3.3 now fully migrating to the shortcode that is available in WP Geo. The ‘cat=’ parameter (if you’re using it) theoratically should be replace by ‘category=’ but I have not tested that yet…

James, let me know how the 0.6 version works for you ??

Cool, thanks RavanH

@ben I saw your mashup shortcode now accepts even more parameters. So it looks like there is no reason to continue with my version of the mashup shortode. For backward compatibility with the previous versions and with Geo Mashup, I’ll keep it in a rudimentary form basically using your shortcode function… But does the documentation on https://www.wpgeo.com/documentation/shortcodes not need an update? ??

Could I request one more parameter? If you could add 'lang' => null then suddenly, when using Polylang for multi-lingual sites, it will be possible to define a specific language or to choose to display all languages at once in one mashup map…

Thank you both for extremely quick responses!
Both plug-ins work perfectly with Google Maps API v3!

All the best,
James

@ravanh I’m planning to build out the documentation on GitHub via a wiki:
https://github.com/benhuson/WP-Geo/wiki

I’d rather add in a filters to help with compatibility with other plugins like Polylang rather than introducing other plugin code to WP Geo. Maybe you just need a filter in get_wpgeo_map() to set a default value for lang?

@ben a filter would be great too! Thanks ??

@james thanks for the report ??

@ravanh Something like this?

https://github.com/benhuson/WP-Geo/commit/bd9bffaa6d492b7efe838145008011eaa654d04b

@ben I was thinking more like a filter before wp_parse_args to allow changing defaults or adding optional shortcode parameters. Something like:

$defaults = apply_filters( 'wpgeo_map_default_args', $defaults );

Or would that be inconvenient?

More like this?
https://github.com/benhuson/WP-Geo/commit/9fd4dfc05924a4d4fbeb5dc97098be9d9545e4a2

just perfect ??

Have added that in for the next release.