tempranova

In the premium version, you can upload custom pins and use many in different colours. https://mapster.me/wp-mapbox-gl-js/wp-mapbox-gl-js-advanced

Hello guys, thanks for the feedback. We haven’t been able to crack this bug as we have a hard time re-creating it. We have noted the problem with apostrophes before, although we haven’t noticed it with any other characters.

We will make sure to work on this some more in the next day or so and see if we can push a solid fix.

I don’t think the geolocation would be messing this up, but there may be some problem with the IDs, and once the parsing has a problem then things start to go haywire.

Please let us know any other issues you’re facing aside from the “undefined” issue and the encoding problem.

Hey there, I think we found the error. It’s on line 60 of public/js/wp-mapbox-gl-js.js. change “mapData” to “mapdata”.

In the latest update, I’ve pushed this, so you should be able to update. Take a look and let me know if that fixes it.

Hey there again, we can’t seem to recreate the error. We didn’t make any recent changes to the front-end marker code. Can you send us a link to the problem at [email protected]? We’ll get on it right away.

Hi there, we will take a look at this right away and get back to you!

Hmm! That’s bad! Can you email me at [email protected] and maybe I can go in to take a look to make sure that’s the thing breaking everything? Otherwise, I will let you know when I push out the next version later this week.

Hey there! Is this just a warning appearing, or is it causing anything to break? It’s a warning from the React application underlying it that I need to change a flag when I run the development build of the app. I will fix this in the next release, but it shouldn’t actually be causing anything to break. Let me know if there is something not working and I will try to get on it ASAP!

Thanks,
Victor

Hi falkgeist,

Can you give me a screenshot of what you’re seeing, or let me know what other metaboxes are appearing above the editor? I just did a test on my end and I’m seeing the normal post and page editor area staying above custom fields, other things, discussion, comments, etc. The code also does specify this only to change for the “gl_js_maps” custom post type in the part where I move up the metabox.

I just want to check to make sure I don’t make the wrong fix and that I replicate your problem as closely as possible.

Thanks again!

– Victor

• This reply was modified 6 years, 5 months ago by tempranova.

Hi Pfeilal, this is definitely an issue. Sorry about the late response.

Are you also able to edit the markers so they don’t say undefined? By default, they should say “Description”. Can you let me know what kind of content you added to the markers? It’s possible that there was some kind of broken HTML that was added, and the parser didn’t allow it to be saved properly.

Happy to help and follow up, just send me a note. My apologies again about the late response here.

Hello Tezet! Sorry about my late reply.

You can see for the shortcode settings at our documentation: https://www.mapster.me/wp-mapbox-gl-js/docs/shortcode/map-options/ . You are able to set the height using “height=600px” in the shortcode when you add that to a post or a page.

Let me know if that helps!

Hello Falkgeist, sorry about the late reply, I’ve just realized that WordPress doesn’t email me when these issues get created.

When you mention the “Edit Box”, are you talking about the content editor on each GL JS Maps page? In the current free version of the plugin, this content editor doesn’t actually affect anything, so there’s no reason for you to be editing there anyway :/.

In the premium version (coming next month), each set of posts will also be visible automatically from the front-end and that editor will be more useful, but currently in the free version, you need to manually embed each map into a post using the shortcode.

I will consider, for the premium version, allowing the content editor to be above the map creator. However, that decision to place the map editor on top is deliberate right now, because I assume most people are using the plugin primarily for the map creator and editor. Happy to hear more feedback, and again, apologies over the late response.

Yikes, I’m so sorry for responding late about this, mgeist! Maybe you emailed me about it separately? In any case, my apologies.

I am wondering about what process Elementor might have for the plugin when it’s rendered. Have you explicitly set the shortcode width to 100%? That might help. https://www.mapster.me/wp-mapbox-gl-js/docs/shortcode/map-options/

When you press Advanced Settings, do you see any error happen in the Web Console of your browser? (in Chrome, you can open this inside View > Developer). This would help to identify the error, since that’s a relatively simple bit of code.

Right now, you can increase the size of Marker text using the standard WordPress editor — you can go into the Text (HTML) side and increase the text size there, or use a particular heading size that you want to use.

We are nearly at the end of the development cycle for the premium version of the plugin, so I will think about including an easier way to increase text size in that version.

Again, my apologies for being late, please let me know if I can help out further with the particular maps you were struggling with.

• This reply was modified 6 years, 5 months ago by tempranova.

Hello mgeist! Thanks for the rating and the comment.

The plugin should be able to make the map fit. If you see https://www.mapster.me/wp-mapbox-gl-js/docs/shortcode/map-options/, you’ll see that you can set the width of the map to 100% in the shortcode (with something like [wp_mapbox_gl_js height=”500px” width=”100%” id=”your_map_id”]. This should allow it to wrap to the correct width.

Please let me know if this works, or we’ll make sure to update things accordingly.

I’m sorry about the slow reply — have been on vacation.

• This reply was modified 6 years, 7 months ago by tempranova.