- Joined
- May 25, 2013
- Messages
- 5,071
And this is why I don't like IPS many times.
Configure Google Maps project with the following API's:

Then you submit the token in the ACP and you get this

Uhhhh... exsqueeze me, but it sure as hell looks like I do have those API's required enabled. Even after waiting an hour "for it to take effect" I still get the same response when I try to submit the API that Google provides.
And the token is definitely valid:

Granted, this is an older version of IPS, but it was working fine but had an issue with the maps not pulling up locations by the IP address in the user profile (think it was actually an IPS issue) so started a new Google project and get the above. Then when I try to go back to the token that WAS working, guess what I get. The same thing.
This was a PITA to configure the first time as it took several creation attempts before it worked if I remember correctly (that was back in 2018). I'm honestly about ready to pull that site totally off line as there have been to many little headaches like this and I'm not going to simply put out a couple of hundred more dollars to see if something is "fixed" that should be still working since the old API token worked prior to developing a new Google Project.
Of course, since it's not a "current" version, going over to the IPS website for input from fellow IPS admins is totally useless (have found that to be the norm also even when it was the current version).
Configure Google Maps project with the following API's:

Then you submit the token in the ACP and you get this

Uhhhh... exsqueeze me, but it sure as hell looks like I do have those API's required enabled. Even after waiting an hour "for it to take effect" I still get the same response when I try to submit the API that Google provides.
And the token is definitely valid:

Granted, this is an older version of IPS, but it was working fine but had an issue with the maps not pulling up locations by the IP address in the user profile (think it was actually an IPS issue) so started a new Google project and get the above. Then when I try to go back to the token that WAS working, guess what I get. The same thing.
This was a PITA to configure the first time as it took several creation attempts before it worked if I remember correctly (that was back in 2018). I'm honestly about ready to pull that site totally off line as there have been to many little headaches like this and I'm not going to simply put out a couple of hundred more dollars to see if something is "fixed" that should be still working since the old API token worked prior to developing a new Google Project.
Of course, since it's not a "current" version, going over to the IPS website for input from fellow IPS admins is totally useless (have found that to be the norm also even when it was the current version).
Last edited: