[Chris]

Hi,

I’m not sure I understand, but any map created with the map block is assigned to the post. If you don’t need the block, you can delete the block. But the map will still exist and it will still be linked to the post.

That should work exactly like creating a map with the old metabox, but not inserting the shortcode.

[Chris]

Hi,

It’s true, the metabox is gone. But a new ‘MapPress’ button exists over the post editor, which opens a popup editor. There’s also a new ‘map library’ under the MapPress settings, where maps can be edited. You can see some details and a screenshot here:

https://mappresspro.com/whats-new/

[Chris]

Hi Connie,

Thanks, being able to see the map was a big help, and I think it’s working now.

I found two issues:

1. For the title, it’s ‘poi.title’ not ‘post.title’
2. The plugin uses the default template when viewing a mashup in the admin. But for some reason, you site was setting the admin flag even when viewing the mashup on the frontend.

For #2, I removed the admin check in the copy of MapPress that is on your site. I’ll also include that change in the next release.

[Chris]

Hi,

To get what you want you’ll need to make the mashup setting “Post title and excerpt”. Then, enter the code you originally posted into the mashup-popup template:

<div class='mapp-title'>{{{post.title}}}</div>
<div class='mapp-body'>{{poi.props.projektadresse}}</div>

I think I see the problem: when I pasted in your code, it contained curly quotes ( ’ ) instead of straight quotes ( ‘ ). Only straight quotes are allowed for HTML attributes. If you use the version above, it should work.

If that doesn’t help, please create the template as shown above and then *leave it active* so I can see it in the mashup (or send a login to the site for that purpose).

[Chris]

Sorry, I didn’t realize the change should be only for maps.

It’s possible to do this using filter ‘mappress_post_query’ instead. That filter lets you modify the results of a mashup query before it’s displayed.

However, I think it would make more sense to just add a new filter ‘mappress_poi_excerpt’ specifically for excerpts, since this issue comes up frequently – many themes & plugins modify the standard functionality.

Could you use the contact form to send a login to your blog? I’d like to add the new ‘mappress_poi_excerpt’ filter directly to your plugin, and once it’s working for you, I’ll also include it in the next release.

[Chris]

Hi,

I see the mashup here:
https://www.vorpommersche-kueste.de/aktuelle-projekte-3-2/

Your code for the mashup popup looks OK. But at the URL above, it doesn’t look like the mashup popup template has been modified. Could you save the template so I can see the result on the mashup map?

[Chris]

Hi,

The way you have the template looks right, the plugin should pick up the projektaddresse custom field.

But did you edit the ‘map popup’ or the ‘mashup popup’? Since it’s a mashup, you need to put that code in the ‘mashup popup’ template.

[Chris]

Hi,

I don’t think it’s changed, but MapPress calls the function wp_trim_words() to limit excerpts to 55 characters.  That function also strips out any HTML tags and characters.

The wp_trim_words() function is also called in normal theme functions like the_excerpt().  It’s an involved process, this article has an explanation:

https://www.satollo.net/how-the_excerpt-function-works-in-wordpress

Anyway, if you want to force tags through, there’s a filter that allows you to determine what wp_trim_words() should return.  The filter’s last argument is the orginal text, so if you add the following to your theme’s functions.php file, it should return it unaltered.

Note that this will affect all excerpts, including elsewhere in the blog.

function mytrimwords($text, $num_words, $more, $original_text) {
return $original_text;
}
add_filter('wp_trim_words', 'mytrimwords', 10,4);

[Chris]

Hi,

Per our email exchange, I think you found this was an error in another plugin, so I’ll consider it resolved?

 

[Chris]

Hi,

Good questions.  Here’s a brief answer and the MapPress documentation may have some additional info.

1.  Only custom fields that have actually been used in a post are available in the dropdown.  You may need to create a dummy post and publish it to get the field to appear.  Also, some custom field plugins use internal IDs that don’t match the defined name (I’m not sure if Toolset does this).

2. The overwrite option is only for automatically-generated maps, i.e. if you edit a map that was generated, it’ll be overwritten if you publish the post again.

I hope that helps.

 

 

[Chris]

Hi,

Thanks for letting me know!  It looks like this was a bug in the latest version.  It should be fixed now in 2.56.3.

[Chris]

The original shortcodes will continue to work, but Gutenberg requires conversion to blocks before you can edit them with the new block editor.

[Chris]

Hi,

Are you using the Gutenberg editor?  In the new versions, the plugin uses Gutenberg blocks instead of the older metabox.

You can convert any existing shortcodes to blocks and then edit them.

[Chris]

Hi,

It’s already there, have you updated to the latest version?  You can switch it on or off from the MapPress settings page.

Both Leaflet and Google are supported.  The Leaflet version also features a ‘spiderfier’ which separates markers that overlap each other.

[Chris]

If you would like to code it, I’ll have a look at how to add it in to the main plugin.  It could be incorporated in the plugin, or added using a filter/action.

[Author]

Posts