@mike_in_md
Thanks for the link – the page is throwing 2 JavaScript errors both about Invalid Google maps API keys
Timestamp: 10:33.29
Google Maps API warning: NoApiKeys https://developers.google.com/maps/documentation/javascript/error-messages#no-api-keys
fC.
Google Maps API warning: InvalidKey https://developers.google.com/maps/documentation/javascript/error-messages#invalid-key
So it would appear that your Google maps API key has either been removed or is no longer valid.
Go to the plugins setting page and open the Options box
+ Plugin Framework Global Settings
Follow the link in the text in the Google Maps section and generate a new Google key and then add it and save changes.
That will fix the white space in the page (where the map should be showing and i believe it will fix the out of alignment on the cards as the broken JS will be affecting that.
Regards
Steve
Steve,
Thanks for your reply. I did what you said, but any changes that I try to save do not take. It doesn’t matter what changes I try to make…nothing saves. The strange part is that when I click on save changes, it says “contact page settings successfully changed”, but nothing changed…the google map API shows no data even after I entered and saved it…again same with everything else.
I guess the real question now is how to get changes to REALLY save.
Note: I never deleted any google map API to begin with so I am unsure why this happened after I upgraded to the 3.1.3 version.
-
This reply was modified 3 years, 7 months ago by
mike_in_md.
-
This reply was modified 3 years, 7 months ago by mike_in_md.
I have a similar problem as @mike_in_md, after updating to 3.1.3 the page looks messed up. The photos on profiles are bigger than they should be and the map isn’t shown. After I reinstalled version 3.1.2 it looks as it should. I also cannot save any settings, i receive same message as Mike.
Is there a solution to this problem? Could it be the file writing permissions? I doubt it since there would be an error message displayed.
Thanks in advance
hcpuros, You’re my hero. I reverted back to version 3.1.2. I’m back to normal now.
You’re welcome, I guess… It’s just a temporary solution. Hope there will be a 3.1.4 version with a fix to this soon.
I already had to remove the plugin from one of my other websites, since it “broke” the whole site. I had no idea I could have just reverted to previous version…
@mike_in_md, @hcpuros
Version 3.1.4 was released 2 weeks ago – are you able to confirm that the upgrade fixed the issue for you?
Regards
Steve
Yes, sorry I forgot to write it here. I had no problem with the current update. It looks as it did in 3.1.2.
Cheers and thanks for asking!
3.1.4 fixed the problem. Thanks Steve!
