Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FIX] base_geolocalize: raise a helpful error to configure the Google… #32162

Closed
wants to merge 1 commit into from

Conversation

len-foss
Copy link
Contributor

… account

Google maps used to be free, but became a paid API.
The hold dealer's tactic of getting'em hooked on the stuff for free,
and then you make them pay once dependant. Great business model.
Technically, the usage could be part of the free offer,
but to benefit from it the account needs to have billing enabled.
Since it's a paid feature security had to be ramped up,
so now API have to be explicitly enabled (here geolocating/geocoding).
All this makes it so that the Google account has to be properly configured
before the calls to the Maps API can work.
As a result we add an explicit UserError if the request fails,
to help the user configure the Google account
(before the error was entirely hidden as to give the user no chance at all).

opw 1946485
opw 1947292
opw 1947337

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:

--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

@robodoo robodoo added seen 🙂 CI 🤖 Robodoo has seen passing statuses labels Mar 27, 2019
@C3POdoo C3POdoo added the OE the report is linked to a support ticket (opw-...) label Mar 27, 2019
@robodoo robodoo added CI 🤖 Robodoo has seen passing statuses and removed CI 🤖 Robodoo has seen passing statuses labels Mar 27, 2019
@len-foss len-foss requested a review from nim-odoo March 29, 2019 09:31
Copy link
Contributor

@nim-odoo nim-odoo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Export translations
  • You point of view on the business model is not necessary

Otherwise ok.

… account

Google maps used to be free, but became a paid API.
Technically, the usage could be part of the free offer,
but to benefit from it the account needs to have billing enabled.
Since it's a paid feature security had to be ramped up,
so now APIs have to be explicitly enabled (here geolocating/geocoding).
All this makes it so that the Google account has to be properly configured
before the calls to the Maps API can work.
As a result we add an explicit UserError if the request fails,
to help the user configure the Google account
(before the error was entirely hidden as to give the user no chance at all).

Also exports transaltions, including for commit e6ca846
which raised a similar error message if no API key was found.

opw 1946485
opw 1947292
opw 1947337
@robodoo robodoo removed the CI 🤖 Robodoo has seen passing statuses label Mar 29, 2019
@len-foss
Copy link
Contributor Author

robodoo r+

robodoo pushed a commit that referenced this pull request Mar 29, 2019
… account

Google maps used to be free, but became a paid API.
Technically, the usage could be part of the free offer,
but to benefit from it the account needs to have billing enabled.
Since it's a paid feature security had to be ramped up,
so now APIs have to be explicitly enabled (here geolocating/geocoding).
All this makes it so that the Google account has to be properly configured
before the calls to the Maps API can work.
As a result we add an explicit UserError if the request fails,
to help the user configure the Google account
(before the error was entirely hidden as to give the user no chance at all).

Also exports transaltions, including for commit e6ca846
which raised a similar error message if no API key was found.

opw 1946485
opw 1947292
opw 1947337

closes #32162

Signed-off-by: Nans Lefebvre (len) <len@odoo.com>
@robodoo robodoo added CI 🤖 Robodoo has seen passing statuses merging 👷 and removed merging 👷 labels Mar 29, 2019
@robodoo
Copy link
Contributor

robodoo commented Mar 29, 2019

Merged, thanks!

@robodoo robodoo closed this Mar 29, 2019
@len-foss len-foss deleted the 10.0-opw1946485-gog-len branch March 29, 2019 12:36
ecino pushed a commit to CompassionCH/odoo that referenced this pull request Nov 22, 2019
… account

Google maps used to be free, but became a paid API.
Technically, the usage could be part of the free offer,
but to benefit from it the account needs to have billing enabled.
Since it's a paid feature security had to be ramped up,
so now APIs have to be explicitly enabled (here geolocating/geocoding).
All this makes it so that the Google account has to be properly configured
before the calls to the Maps API can work.
As a result we add an explicit UserError if the request fails,
to help the user configure the Google account
(before the error was entirely hidden as to give the user no chance at all).

Also exports transaltions, including for commit e6ca846
which raised a similar error message if no API key was found.

opw 1946485
opw 1947292
opw 1947337

closes odoo#32162

Signed-off-by: Nans Lefebvre (len) <len@odoo.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI 🤖 Robodoo has seen passing statuses OE the report is linked to a support ticket (opw-...)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants