Hi, when I'm looking at a contact's data in Kaddressbook and click on the blue link on the right of the address to see it on a map, it goes to the mapquest page but gives an error saying: 'The AppKey submitted with this request is invalid.' I've given an example of this in the url above though changed it to remove personal data. I'm not sure if there's a way to add other map services or to fix this one. Thanks. Reproducible: Always Steps to Reproduce: 1.go to contact 2. click on blue link to go a map in browser 3. Actual Results: Web page gives error message. Expected Results: Map of Location. KDE version 4.14.2, Kaddressbook 4.14.1. On Debian Jessie.
it(s a very old kdepim we are kf 5.0 and kde4.14.10 But we have several engine I will investigate why you have this error. Is it possible to save this specific contact as vcf and send me in private ? I need to know if it's a problem in your address or engine
Hi Laurent - I've tried it with several different addresses and the bug occurs with each? On 30/10/15 11:37, Laurent Montel via KDE Bugzilla wrote: > https://bugs.kde.org/show_bug.cgi?id=354594 > > Laurent Montel <montel@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |montel@kde.org > > --- Comment #1 from Laurent Montel <montel@kde.org> --- > it(s a very old kdepim > we are kf 5.0 > and kde4.14.10 > But we have several engine > I will investigate why you have this error. > Is it possible to save this specific contact as vcf and send me in private ? > I need to know if it's a problem in your address or engine >
it works here. it's for that that I need an example => a vcard please :)
Created attachment 95227 [details] Contact vcard
No problem - attached! Sounds like it's just the old version of the program and I'll just have to wait till the update works its way here.
Thanks So I confirm it works. So it was fixed during 4.14.x you need to increase kdepim version.
Running kaddressbook5-15.08.3 on openSUSE Leap 42.1, I have the same problem exactly.
The issue is still open with kAddressbook 5.0.3 (KDE Framework 5.18.0) :(