Godfrey, The following things abruptly happened in LR6 and just about the time of the API change:
- I have a “Photos” folder containing one folder for each year on an external drive that I use as my “photo drive.” The number of photos reported overall, and the number of photos in each annual folder, went to 0. Oddly, most of the monthly sub-folders still display accurate counts, though some (like all of them from 2015) report 0. - My keywords vanished, almost every one of them. Some groups of photos still have their keywords, but the search function can’t find them. I tried quitting and restarting LR, and quitting and restarting my computer and hard drives. No use. Rick > On Dec 20, 2018, at 5:57 PM, Godfrey DiGiorgi <[email protected]> wrote: > > > >> On Dec 20, 2018, at 2:42 PM, Rick Womer <[email protected]> wrote: >>> On Dec 20, 2018, at 5:35 PM, Matthew Hunt <[email protected]> wrote: >>> On Thu, Dec 20, 2018 at 4:48 PM Rick Womer <[email protected]> wrote: >>> >>>> 1. I have LR 6.14 installed on my computer. Why should it be updating >>>> anything from Google? >>> >>> You don't have maps and images of the whole world on your computer. >>> When you use the mapping module in Lightroom, it accesses Google's >>> servers for the maps and images. >> >> I’ve never used the mapping module in LR. I =did= use my keywords, a lot! >> I really have no idea what to do here. > > Hi Rick, > > Nothing about the Google API change should affect your keywords, and the only > thing that is broken in LR 6.14 is the Maps module … which I've never used. > What problem are you running into with keywords? > > I have LR 6.14 running on my macOS system (macOS X Mojave) right now. > Nothing's wrong with either my keywords or anything but the Maps module, > which I have never really used at all. So I just edited the top bar and > removed it's module key so I don't click on it accidentally. > > >>>> 3. Why are the people who run large tech companies such jerks? >>> >>> Maintaining and old API in addition to the new API would incur costs >>> to Google, which they do not wish to incur. Adobe incurs costs >>> updating Lightroom to the new API, and they recover these costs >>> through the subscription pricing model, which you have elected not to >>> pay. This is, to be frank, an example of why even "software that's >>> finished and works" requires maintenance, and why software companies >>> are moving to subscription models to the degree that the market allows >>> them to do so. >> >> Adobe’s terrible customer service has always indicated to me that they don’t >> give a damn about their users once they have their money. So I guess I >> shouldn’t be surprised when they disable a vital feature in order to >> maintain a couple of bells-and-whistles. > > Hmm. While I have my beefs with Adobe and their attitudes, and certainly with > their "subscription is everything" policy of the present, I have to say that > I've never had any issues (other than that they're slow and it often takes a > good bit of effort to find/get what I need out of them) with their customer > service when I've used it. I dislike the subscription model because, as they > have it configured, it's not a good match to my needs and there's no longer > any way around it if I want to keep up to date on their tools. > > My solution is to switch to other tools, eventually, when Adobe tools I have > stop working. The Google Maps API is one part dead, but it's a part I never > really use so it's not of much importance to me. Same for the Publish > Services, and Book and Web modules … never used them other than to test > things, so I just ignore them. > > G > -- > PDML Pentax-Discuss Mail List > [email protected] > http://pdml.net/mailman/listinfo/pdml_pdml.net > to UNSUBSCRIBE from the PDML, please visit the link directly above and follow > the directions. -- PDML Pentax-Discuss Mail List [email protected] http://pdml.net/mailman/listinfo/pdml_pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
