mschwar

Sadly I don’t think that an export will take these along for the ride.

Do you have access to the database? You can dump the two DB tables that contain all the map info and move them over to your new database. Those tables don’t contain info that is specific to any particular WP installation.

For example:

mysqldump -u old_db_user_name -p old_database_name wp_wpgmappity_maps < maps_export.sql

mysqldump -u old_db_user_name -p old_database_name wp_wpgmappity_markers < markers_export.sql

Then:


mysql -u new_db_user_name -p new_database_name wp_wpgmappity_maps < maps_export.sql

mysql -u new_db_user_name -p new_database_name wp_wpgmappity_markers < markers_export.sql

Hey danno – I’m the author.

I’ve been hunting and hunting for the source of this problem and have been able to reproduce this error that some people are having with 0.5.5

The solution you just posted makes perfect sense – by turning off the “save data” option the tables in your database were wiped when you deactivated and then built fresh when the new version was installed.

This localizes the problem to the database update functions.

If you see this could you fill in a couple blanks for me? It will really help me track down why some people are experiencing this problem.

What version of the plugin were you previously on? If you don’t remember a specific version number, do you remember about when the last time you installed it / upgraded it was?

What web hosting company are you using? Would you happen to know what PHP version and MySQL version you run?

For anyone else reading – if you are having this same problem the answers to those questions would really help me stomp this bug.

Hi DG,

Glad the plugin is useful!

So the short answer is not without hacks at the moment.

You could absolutely just hop into the database and change your stored values for that map if you like. Or resize the div with a piece of javascript. Or I (possibly?) a CSS !important rule in your stylesheet.

Again – those are all hacky though.

The reason this is set this way is legacy from when the plugin was using version 2 of the Google Maps API. Maps broke down below those dimensions as the Google copyright took up most of the space leaving the map pretty unusable.

I’ll take a look to see if that is still the case with version 3 of the API since we have made the jump to it.

Heya archert – thanks ??

That’s a really interesting idea. As it is now it only produces one line of HTML – just an empty <div>. It then produces a handful of JS to build each map. TinyMCE is really cranky about letting anything insert JavaScript in a post – thus the shortcode.

What do you think would be the most useful way to offer the functionality? Maybe add an option to the “insert link” button in TinyMce that builds a map?

I’ve never used Tippy or Hover before, I’ll take a look at them to see their UI’s.

Thanks barkerbaggies! Glad its useful.

@protop – I’ll leave it to others to rate it, but its purpose is to allow maps to be added in a similar manner to adding an image to your post. Click the button and a window similar to the “Add an image” window pops up and allows you to build a Google Map.

There’s a “living” example of the window towards the bottom of the plugin’s home:

https://www.wordpresspluginfu.com/wpgmappity/