The release candidate for BGMP 1.10 is now available. The biggest changes are:

Fixes a few persistent bugs in the 1.9 releases

Adds new shortcode options for only displaying a single placemark on the map, and adding links to map markers in the text list.

Add more hooks for developers.

Adds a German translation.

If you'd like to try it out, just download and install it. If you notice any problems, give detailed feedback here and then downgrade to 1.8 until they're fixed.

If you don't notice any problems, please leave a quick note here so that I know it's working for others.

I've also setup an email list to notify everyone when new RCs are available in the future. That way you'll have time to test it out on your staging server, and we can work out any bugs before the official release.

The features listed above aren't available in the current version (1.8); they're available in the upcoming 1.10 version. The release candidate for 1.10 is available for people to test out so that any bugs can be discovered and fixed before it's officially released.

What do you mean by "Providing a filter for the support of no post is also helpful"?

Thank you very much for the implementing of the ClusterMarkers!
Great plugin, the new funcction works on my single page also very well.

But I am working also on a multi blog system and in this case the plugin calculate with the placemarkers list, but only the default pin images appear on the map, the other, with the featured images unfortunately disappeared. I added new test places to the prewious and the result was the same, the map shows only the default markers and the cluster markers.

Additionally, I found some idea for the modifying of the standard cluster images, insread of the replace of the defaults with a new pictures (this is my current solution).
Is it possible to insert this or similar code into the plugin?
If yes, please be so kind and publish, where/which file is the correct place of this?
Thanks a lot,
Andrea

Hello,
Fortunately everything is ok, it seems, that there was a conflivt between the theme and the pugin, but the use of the categories to set up the icons solved it.
Only the midifying of the cluster image would be interesting.
Than you,
KR,
Andrea

@H_Andrea, you can use the bgmp_map-options filter to modify the cluster styles. If you're having trouble with that, please start a new thread. This thread is for any bug reports in the 1.10 release; I'd like to keep new feature requests separate.

I have just had time to install 1.10 tc1 but on inserting the [bgmp-list] shortcode (without even any optional parameters) in a map page on two of my websites the following error messages appear and the page doesn't load (even the non-BGMP text on the page doesn't load). Any ideas what I'm doing wrong?

Warning: BasicGoogleMapsPlacemarks::require(__DIR__/views/shortcode-bgmp-list-marker.php) [basicgooglemapsplacemarks.require]: failed to open stream: No such file or directory in /MYWEBSITEPATH/wp-content/plugins/basic-google-maps-placemarks/core.php on line 1058

Warning: BasicGoogleMapsPlacemarks::require(__DIR__/views/shortcode-bgmp-list-marker.php) [basicgooglemapsplacemarks.require]: failed to open stream: No such file or directory in /MYWEBSITEPATH/wp-content/plugins/basic-google-maps-placemarks/core.php on line 1058

I upgraded to from 1.9.3 rc2 to 1.10 rc1. I haven't previously used the bgmp-list shortcode on either of the websites so I don't know how long the issue (or conflict with something else on my sites) might have been present.

Yes, there is a file named "shortcode-bgmp-list-marker.php" in the "views" directory of the plugin in both sites I installed the new version in (there are 9 files in total in the views directory as per your link).

The plug-in only crashes if I use the [bgmp-list] shortcode, it still works fine using the [bgmp-map] shortcode.

Ah, I see now. The __DIR__ constant wasn't added until PHP 5.3, so if you're using 5.2 then it won't be able to resolve the filename. I'll push a new RC shortly that uses an older method to resolve the path.

This CSS is no longer working and instead I am getting the same font and font-size as set in my theme (Weaver II Pro) for post titles. Is the placemark title no longer h3, or do I need to modify my CSS rule to get back to the look that I had before?

2) This issue relates to the use of [bgmp-list] which I haven't previously been using so it might have been there for a while. In some of my info windows I have an address (or simply a suburb or town). Instead of just displaying the address in the list as text (which is what I want) the address is being "translated" into a linked Google map reference and displayed as an extra line in the list (which I don't want - after all, the placemark for that address is already on a BGMP map!). How can I stop this happening?

I have put a [bgmp-list] shortcode in this page temporarily so you can see what I mean with respect to issue 2. The issue is there whether or not I include the new "viewonmap" parameter.

I have some more questions about formatting the output of bgmp-list but as they are off-topic for this thread I will start a new thread for them when I get a chance.

After installing 1.10rc1 this morning it seems in placemark title the - character gets replaced by & #8211; without the space between the & and # characters. I have been tinkering with a filter/function so probably that's the cause, but restoring everything to default (disabling all the filters in functions.php) doesn't seem to fix it though.

Yes these slider don't work on ver1.10.
Now is v1.8 activated, I delete v1.10

But v1.8 have too some error on homepage (Basic Google Maps Placemarks error: JavaScript and/or CSS files aren't loaded. If you're using do_shortcode() you need to add a filter to your theme first. See the FAQ for details. )

jeroenm77, I wasn't able to reproduce that on my test install. Can you post a link to your map? Did you just type the dash into WordPress using your keyboard, or did you copy/paste from another application?

fegi, Google Maps places a limit on how many geocoding requests it will serve per day. If you're using shared hosting, there are probably other sites that are also making requests, and you've hit the limit for the day.

You can either use coordinates to bypass the geocoding process, or wait until tomorrow and try again. If you'd like to use coordinates, see the FAQ for details.