[Chris]

Hi, there’s a setting ‘mashup thumbnails’ on the settings screen.  Is that checked?  It needs to be set to automatically display featured images.

[Chris]

Hi,

The map id is “mapp0” if there is one map on the page.  Then second map is “mapp1” by default, and so on.  The div containing the map also has the id “mapp0”, and the various layout parts are prefixed with that name, e.g. “mapp0_layout”, “mapp0_directions”, etc.

You can also specify a name in the shortcode using the name parameter, e.g. name=”mymap”.

[Chris]

Hi, I see the problem and I can reproduce it.  I traced it and the plugin is setting the same bounds for both maps.  I think it’s timing-related – Google sets the bounds asynchronously and it seems the problem happens if the map ’tiles’ are loading at the same time.

I’ll see if it can be fixed in the plugin…

[Chris]

Hi, the plugin doesn’t support anything like that.  You could hook into the save action and extract the data from the map as it is being saved.  The plugin call this action when a map is saved, with the mapid that was saved.

do_action('mappress_map_save', $mapid);

You can use this to retrieve the map:

Mappress_Map::get($mapid)

[Chris]

Hi, this was a bug that was introduced in version 2.39.3.  It should be fixed in 2.39.4, which you can download from your account now.

[Chris]

Hi, 2.39.2 – actually 2.39.3 as of today – is the latest stable version of MapPress.

The beta versions are less tested and contain new functionality.  The stable versions just receive bug fixes and minor updates – like WordPress 3.4.1, 3.4.2, etc.

[Chris]

Jim, you can always re-install an old version.  But first you might want to check if your theme is calling wp_footer().  Some older themes don’t, and the plugin need it in order to load its scripts.

[Chris]

No, I haven’t heard of any conflict.

[Chris]

Hi,

I also updated MapPress so it will work with some older jQuery versions.  You can give 2.39.2 a try if you don’t want to switch or change your template.

 

[Chris]

Hi,

Did you get some kind of error message?  It sounds like you noticed this already, but you do need to deactivate the plugin before deleting it.

If it’s not working for some reason you can use your FTP client to just delete its directory from your plugins directory (/wp-content/plugins/).

If that doesn’t help, you can send a login if you like and I’ll try to install it for you.

[Chris]

Hi, the maps are stored in the database so you won’t lose them.  You can do a database backup first to be sure – it never hurts.

Please be sure you’re installing the Pro version from your account, not the free version:

http://mappresspro.com/install

 

[Chris]

Hi,

You can’t use mapid for the mashup but you can specify a specific post using the ‘p=’ parameter.  There should be an example of a mashup like that in the documentation.

There’s no overall list of maps yet, but it will be coming in the next version.

If you look at the front of this forum, there’s a ‘sticky’ FAQ posts that describes how to add missing translatins.

 

 

[Chris]

Hi,

There was a change for the default functionality for the [mashup] shortcode.  Rather than showing all maps, it only shows the ones on the current page by default, to prevent accidentally running long queries.

Does it work if you use this shortcode instead?

[mashup query="all"]

[Chris]

Hi Brad, it’s an array, try:

“mapLinks” => array(“bigger”, “center” , “reset”)

[Chris]

Hi Brad,

You’re absolutely right on both issues.

Thanks for letting me know.  Look for 2.39.1 later today with a patch.

On the draft posts: the mashups now use AJAX to query the database.   WordPress treats front-end AJAX calls as though they came from admin screens.  Apparently in the WP query code there is a hard-coded check that adds all statuses if the query is coming from the admin – and since WP can’t tell the query is really from the front-end, it returns all posts.

There is a 3-year-old ticket about this that seems to have been resurrected again recently:
http://core.trac.wordpress.org/ticket/12400

Maybe they’ll fix it this time.  Meanwhile, I’ll update the query code to default to ‘publish’.  I don’t see the is_admin() check doing anything else so that should fix the problem.

As for the posts_per_page – I switched it to support paging the results, but since that function didn’t make it into this release, I’ll set it back to -1 by default.

Thanks again, please let me know if you notice any other issues.

[Author]

Posts