-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Lightroom 6.14 : Map not working #21
Comments
Hi Sebastien, I don't know if Lightroom writes any logs. You should see traffic in your Google Cloud account. If there is no activity on then most likely the API key is wrong. Also make sure to enable the necessary APIs on your Google Cloud account as described in section 2. Best Regards, |
Yes, that's the key. Double check that you included the API key without extra characters (for example don't add the { } brackets). APIs look ok. Make sure to exit Lightroom before updating the files. To be sure that you update the correct location, you can rename the file and see if Lightroom complains. If it doesn't you may be modifying the wrong file. |
I've regenerate my key which now does nto contains hyphen (the first one was). Still not working. |
I've checked hexa content and replacement seems to be done :-\ |
I just checked, and I get the error you see when I rename my Location.lrmodule. When you replace your module with the original (I hope you have a backup), what error do you get? |
With original or without any Location.lrmodule, I've got the same error as the one in my first comment. I' ve not find any log or debug mode/console ... |
I had heaps of trouble getting this working. My top is that modifying the
file is pretty straight forward with clear instructions. I missed some of
the things in the google end of things which made mine work straight away
after fixing,
…On Wed, 28 Aug 2019 at 04:52, sebsebseb1982 ***@***.***> wrote:
With original or without any Location.lrmodule, I've got the same error as
the one in my first comment. I' ve not find any log or debug mode/console
...
Could I sent you my modified module ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#21?email_source=notifications&email_token=AB6VIVDHYHW6GEXWG2EBPX3QGVZWLA5CNFSM4IPOPHE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5IYGII#issuecomment-525435681>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB6VIVGQ7DVUUNW7AIG4PZ3QGVZWLANCNFSM4IPOPHEQ>
.
|
My Google API seems to be OK. I'll try to find someone who can test my module |
Hello, Is there a way to turn on the location debug panel or otherwise see which calls ligthroom makes ? |
I've got exactly the same problem. If you find solution I'm interested ! |
Sorry, but I really can't reproduce those issues. Are any of you using non-english versions of LR? Unfortunately, I haven't figured out how to enable the debug console that the error message mentions. I suspect it's a standard message from the embedded browser that displays the map. |
I'm using it in French as well but doubt Adobe made language specific versions. Do you know how to trace all the http calls and responses ? I'll do some research on my side, just wondering if you alredy did it. |
Nope. I haven't time to do it now but maybe Fiddler (if it's still compatible with Windows 10) could bring answers. |
Something really weird happened that I absolutely cannot explain...
I went back to resource hacker to check location.lrmodule and it definitely is the original... I have absolutely no clue which file LR is using but the fact is that it somehow switched to my API key. |
Someone just posted this on the thread in DPreview:
Please let me know if this solves the mystery for any of you. |
Yes ! that's it ! |
Same for me ! Changing the extension did it. Thanks a lot. |
Hi !
I've modified my Location.lrmodule as explained here, but it is still not working :-(
Do you know where I can find logs that could help me ?
Thank you,
Sébastien
The text was updated successfully, but these errors were encountered: