Wappler Version :BETA 5
Operating System : mac
Server Model: node
Database Type:
Hosting Type:
An existing google maps script tag should be left alone.
Custom settings for the script tag are removed after the page is saved.
Would love to use beta builds more, but this bug is a blocker for me on an active project.
Yes same here, it removes the key from the script. Which renders the maps component in development mode.
Still happening in Beta 9.
@George This is a complete blocker to using Wappler 5 for me. Perhaps some bug fixing could be done within the RC process?
Same here. Was really hoping for a fix in yesterday’s release.
Yap, same here I had to re-edit and save the file with visual studio.
Ran into the same issue and used Google’s script as a workaround. I was hoping this would be fixed in Beta 9 as I have been tracking this post.
Will this be fixed after the V5 launch? Seems like such a trivial thing, but is super irritating having to manually rework all pages every time I edit a page with google map on iit.
Same here.
Wappler 5 beta 10, Windows 11, NodeJS.
Just installed v5.0.0 Release and this is still removing the maps API key.
Unfortunately I will have to stay with v4.9.1 until this is resolved. Every time I save a page I lose the key and initially I didn’t know it had happened.
Great. Well, looks like 4.9.1 is going to my platform for awhile.
Hmm, this is slightly more serious than I first thought. v5 has replaced v4.9.1 and left the beta alone. I was expecting it to replace the beta so v4 could still be run.
@George, can we get bug fixes ASAP so we can use v5?
Yes now that the major update is out we can focus on all those smaller bugs
Good stuff. Will I have to wait a week? I’m keen to be using v5.
Same happened to me when i updated to 5.0.0
Decided it was probably a sensible time for a full uninstall and to start fresh so removed both 4 and beta 5 and installed 5.0.0 as new
Does it still lose the Google Maps API key from the code when you save?
In Scotland at moment. Will check when I get back home.
Hopfully we can expect a fix in today’s update? 
