[Chris]

Hi,

I’ll need to see your blog to help you. Could you please provide a URL demonstrating the problem or better yet, a login to the blog?

If the blog isn’t public yet, another option would be to sign up for a demo site here and try to replicate the issue:

http://mappresspro.com/demo

[Chris]

Hi,

I think I see the problem – the plugin sets width on the outermost div but the height is set on the inner canvas div. This works if the height is in pixels but not if it’s in %.

To make % height work you’ll need to either modify the template file ‘map_layout.php’ or use CSS. For CSS, if you give your container div the id ‘xyz’ something like this might work:

#xyz .mapp-layout { height: 100% }

Or maybe you could just include the height and width in the shortcode directly:

[mappress id="1" width="100%" width="480" height="480"]

[Chris]

Hi,

Possibly – I don’t know enough about KML files to say. MapPress uses the infoWindowHtml property of the KmlFeatureData object.

From what I’ve read, that should include the extendeddata, but you need to use ‘entity replacement’ to make it available to the infoWindowHtml property:

https://developers.google.com/maps/tutorials/kml/#extendeddata_elements

[Chris]

Hi,

I took another look at this today and I’m not sure I fully understood (or answered) your question. I just went through the relevant MapPress code to recall the details so I’ll try again.

The plugin does suppress the default infoWindows as I said in my earlier message. But when a feature is clicked, MapPress should show the infoWindow content from the original KML file – it just wraps it in MapPress CSS. The idea was to provide a consistent CSS style without interfering with the KML.

If the clicked feature has no infoWindow in the KML file, then it should show the MapPress title and body. This is also true if a KML is clicked from the POI list, or in the editor.

I wasn’t clear from your post if current version of the plugin isn’t working this way, or if that’s undesirable – or if there’s something specific to your KML file. Could you elaborate about what you’re expecting to see and provide an example URL or KML?

[Chris]

Hi,

Sorry, the documentation is not up to date. I’ll update it right away.

The current versions of the plugin is more flexible, but it doesn’t default the ‘to’ address. The following parameters are used:
initialopendirections – true of false

from – address or POI number (starting at 0) to use as the default whenever the directions form is opened

to – address or POI number to use as a default

For example, this will open the directions from with directions from San Francisco to the first POI:

[mappress initialopendirections="true" from="San Francisco" to="0"]

[Chris]

Hi, this should do it:

[mashup query="all"]

That essentially just runs the query for all post types with no limit, i.e.:

[mashup query="post_type=any&posts_per_page=-1"]

[Chris]

Hi,

If the infoWindow was defined in the KML itself, then this is because the plugin suppresses the KML infowindows. Instead it shows its own info (such as the POI title & body defined in the map editor, or the post title & body for mashups).

I’m not sure if it’ll work in your case, but one options is to just add the content in the MapPress editor or post body.

[Chris]

Hi,

Sorry, I’m not familiar with WPS. Perhaps you can ask them if you can integrate shortcodes or PHP code in the activity stream; if so you can probably display maps.

[Chris]

Hi,

There’s no POI limit in the plugin, but your blog can run out of memory. It doesn’t seem likely that’s the problem – 67 isn’t many posts and if you ran out of memory you would probably just see a spinner instead of the map, not an error. Memory issues are covered here:
http://mappresspro.com/mapress-faq

Try deactivating all of your other plugins and switching to a standard theme for a moment, to see if it’s something else.

[Chris]

Those warnings are related to the border style in the MapPress settings screen.

Here’s a few ways to fix the problem:
– download version 2.42.1 – I’ve fixed the warning messages in that version
– save the MapPress settings again – this should make the messages go away.
– turn off warnings in wp-config.php by setting wp_debug to false

Please let me know how it works out.

[Chris]

Correct, step-by-step instructions are here:
http://mappresspro.com/install

[Chris]

Ok, I checked it! It seems to be a bug in Chrome version 34 and higher:
http://code.google.com/p/gmaps-api-issues/issues/detail?id=6594

I don’t think it’s related to MapPress.

[Chris]

Hi, this is the tabs issue described in the FAQ. Please take a look here for some solutions:
http://mappresspro.com/mappress-faq

[Chris]

I think mobile devices look for a Google URL to open the App. Try setting the directions to ‘google’ instead of ‘inline’ in the MapPress settings.

[Chris]

Hi Joerg,

Check your setting for “overwrite maps when updating” in the “geocoding” section of the MapPress settings screen.

If that checkbox is checked, the plugin will always try to re-create the map using the current custom field values. It will overwrite your changes.

If it’s unchecked, you should be able to make manual changes directly to the map.

[Author]

Posts