SUMMARY Since yesterday, on any of the map views in digiKam, I don't see the location of geotagged photos. Neither thumbnails nor markers show up. If I change the map to Marble Virtual Globe, the photos markers / thumbnails show on the map. STEPS TO REPRODUCE 1. Click on Map or Browse -> Map 2. Select Google Maps as the map type OBSERVED RESULT No photos appear on the map EXPECTED RESULT Thumbnails or markers should appear on the map, depending on which is selected SOFTWARE/OS VERSIONS Windows: Windows 10 Pro 22H2 19045.2846 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION I was running digiKam version 6.8 when this problem started yesterday. I've updated it to 8.0 but the problem persists. I have set up my own Google Maps API to remove the "map for development purposes only" watermark. My API key is saved in C:\Program Files\digiKam\data\digikam\geoiface\backend-googlemaps.html. I've been using this for over six months, so shouldn't be related.
Please can you details how you have set the API in the backend-googlemaps.html. We can certainly create a simple settings to control this directly in digiKam GUI. Note : as you run under Windows, QtWebkit is used to render web contents, including googlemaps, as digiKam is fully cross-compiled under Linux. There is certainly a uncompatibility with this old Qt component with Google web service. Qt provide the QtWebEngine (Chromium) instead when we compile digiKam with Native Visual C++ compiler. There is a windows installer available in the KDE infrastructure compiled with Visual C++, but this version lack few important features, as the Mysql support. https://binary-factory.kde.org/view/Windows%2064-bit/job/Digikam_Nightly_win64/ Take a care to well uninstall the cross-compiled version before to install the native Windows version instead. Best Gilles Caulier Gilles Caulier
Hi Gilles, Thank you for the quick response. I have installed the version compiled with C++ that you provided and can confirm this has resolved the map marker problem. With regards to setting the Google Maps API within the digiKam GUI, I think that's a great idea, and would probably help other users. These are the steps I followed: 1. Activated the free trial and confirmed my credit card at https://console.cloud.google.com/google/maps-apis (my credit card has never been charged as you get 1,000 free map initialisations per month) 2. Opened C:\Program Files\digiKam\bin\data\digikam\geoiface\backend-googlemaps.html in Notepad++ 3. Replaced the 39 character API key that follows "https://maps.google.com/maps/api/js?key=" with my own API key provided in step 1 4. Saved the file, reopened digiKam, and the "development purposes only" watermark is removed Thanks, Jeremai
*** Bug 469781 has been marked as a duplicate of this bug. ***
Google made changes to JavaScript that are no longer processed by QWebKit. Maik
@Gilles, the digiKam MSVC nightly build is currently broken. Apparently missing permission on a "LICENSE" file. I'm not sure if it's a craft issue or if we need to fix something. Maik
a permission to a LICENSE file ? I love craft (:=)))... Gilles
It come from OpenCV: 11:16:52 *** Craft all succeeded: libs/opencv/opencv after 2 seconds *** 11:16:52 [Errno 13] Permission denied: 'C:\\Craft\\BinaryFactory\\windows-msvc2019_64-cl\\LICENSE' 11:16:52 Traceback (most recent call last): 11:16:52 File "C:\Craft\BinaryFactory\windows- NOTE: OpenCV is not the last one, and must be updated. As i know OpenCV is only used by digiKam and KDenlive in the KDE world. Gilles
@Jez, This problem still reproducible with the new digiKam 8.2.0 pre-release Windows installer available at usual place: https://files.kde.org/digikam/ This new bundle is based on last Qt framework 5.15.11 and KDE framework 5.110. Thanks in advance Gilles Caulier
I think this file is fully relevant of bug 433732
No, this is not relevant to bug 433732. This was a problem with QWebKit, due to changes in Google Maps this was the first that stopped working with QWebKit, since we no longer use it we can close here. Maik
Since 8.2.0, Windows installer is compiled with MSVC instead MXE. We use QtWebEngine instead QtWebKit. This problem is no longer present. Gilles Caulier