Google API key – not saved

I’m having the exact same problem! Thanks for any help!

Edited to add: I have the same problem on my localhost, but not on my staging site on a real host. API key is saved just fine on the staging site. So is it a problem with saving the API key on localhost?

• This reply was modified 7 years, 9 months ago by bjtalbot.

I have a problem in the north where there is only one server name “localhost”

https://lebeda.skauting.cz/technicke-informace

On the second hosting WEDOS Servers not called “localhost” and everything works smoothly.

You can fix a bug that caused the server name “localhost”.

Thank you

I have the same issue. Does anybody know if this issue has only recently appeared in an update to the plugin, or wordpress?

When I paste the API key into the text field and press “Save Changes” the text field is cleared. Is this supposed to happen, or is the API key supposed to remain in the text field after saving?

Key stored left! It does not work with WordPress 4.7.2

The documentation for Simple Calendar, here https://docs.simplecalendar.io/system-requirements/, says that PHP extensions curl,iconv,json,mbstring are required. In my PHP installation I have curl and iconv extensions enabled in the php.ini file but json & mbstring do not appear in the php.ini file. Perhaps they are built into PHP 7.1 now? I’m no expert in PHP. Anybody know how to enable these two extension in PHP 7.1?

Are you all running PHP 7.1+ and getting this issue?

Yes from me.

Yes, I use PHP version 7.1.1

Does it work correctly on a version of PHP < 7.1 ?

Immediately I try. 30 minutes’ll let you know

So the problem is only at version 7.1.1

For version 7.0.15 it works.

So bug with saving applies to the entire section of the settings.

Thanks for confirming that. We have it on our list to get things compatible with PHP 7.1 at some point. Unfortunately PHP 7.1 introduces a pretty big backwards compatibility breaking change so we will have to go through the entire plugin to remove any instances of that. Not sure of an ETA but if you can run 7.0.x in the meantime to avoid the errors then that will be best until we can get a fix for it.

Thanks

So what? It’s been half a year and updates are nowhere! When will it support PHP 7.1.x ???