For the ssl switch we executed these MySQL commands:
UPDATE wp_options SET option_value = replace(option_value, ‘http://www.ihreseite.de’, ‘https://www.ihreseite.de’) WHERE option_name = ‘home’ OR option_name = ‘siteurl’;
UPDATE wp_posts SET guid = replace(guid, ‘http://www.ihreseite.de’,’https://www.ihreseite.de’);
UPDATE wp_posts SET post_content = replace(post_content, ‘http://www.ihreseite.de’, ‘https://www.ihreseite.de’);
UPDATE wp_postmeta SET meta_value = replace(meta_value,’http://www.ihreseite.de’,’https://www.ihreseite.de’);
Yes, the marker URLs are saved in the database, just like any of your post images. So when switching from HTTP to HTTPS a database update is always required.
For future reference, we have a detailed write-up on making that transition on our Give website here:
http://docs.givewp.com/ssl
Thanks!
Thanks for your reply, Matt.
With the “Better Search Replace” plugin I replaced all the entries in the database tables wp_options, wp_postmeta and wp_posts from the http://-url to the https://-url. Additionally I replaced in all the tables the tag “http://maps.google.com/maps” with “https://maps-api-ssl.google.com/maps”.
But the markers on the map have not appeared yet. Do I need to update any other table? Is there any other reason why the markers don’t appear any more?
It’s not problem to add a new map with new markers. They appear.
Thank you.
CAn you provide a link to your map so I can see the problem live?
The direct link to the map is:
https://www.dontox.de/google-maps/visa-auszahlungsprobleme/
There should be about 150 markers. Since we switched to SSL they disappeared; but they are still in the database but not connected to the map.
I don’t see anything obviously wrong with the map itself, so I’m curious about the migration process you did, or that original query you did. If the markers were loading as HTTP then there would be errors in the browser that we could see, but instead the markers just simply aren’t there, so it seems like they got associated with the wrong Map ID.
I’d recommend duplicating your site locally, installing your backup database from before your HTTPS conversion, and try to start again. I do not see this as a Maps Builder issue specifically so far, but something that must have gone wrong in the conversion process.
