The latest update of the "Google+ Exporter" seems to handle the references to images in a much better way.
Originally shared by Kent Crispin
The latest update of the "Google+ Exporter" seems to handle the references to images in a much better way. To be precise, previously, I generated a G+ -> blogger backup file, then used the blogger export function to generate another blogger backup, then imported that second backup into a wordpress.com site. This gave me image references like: ...img src="https://lh3.googleusercontent.com/-L38O0UeVzAM/W8xsW9CagsI/AAAAAAABIEU/z08SSCuXFf0DPObMh-kT_RBnOd4UgGN3gCJoC/s400/20181021_185552.jpg"...
That is, the image references were still into google's infrastructure. This may be because of the two step process I used (going directly from Google+ Exporter's export to wordpress failed for obscure reasons).
However, the latest Google+ Exporter supports direct WordPress export files. I ran it again, and imported the result into a new wordpress blog I'm running locally, and the image references now seem to be "correct":
...img src="https://raven.songbird.com/blog/wp-content/uploads/2018/10/20181021_185552.jpg"...
The latest update of the "Google+ Exporter" seems to handle the references to images in a much better way. To be precise, previously, I generated a G+ -> blogger backup file, then used the blogger export function to generate another blogger backup, then imported that second backup into a wordpress.com site. This gave me image references like: ...img src="https://lh3.googleusercontent.com/-L38O0UeVzAM/W8xsW9CagsI/AAAAAAABIEU/z08SSCuXFf0DPObMh-kT_RBnOd4UgGN3gCJoC/s400/20181021_185552.jpg"...
That is, the image references were still into google's infrastructure. This may be because of the two step process I used (going directly from Google+ Exporter's export to wordpress failed for obscure reasons).
However, the latest Google+ Exporter supports direct WordPress export files. I ran it again, and imported the result into a new wordpress blog I'm running locally, and the image references now seem to be "correct":
...img src="https://raven.songbird.com/blog/wp-content/uploads/2018/10/20181021_185552.jpg"...
Which album is that image in? Is it G+Photos from posts, or a Google Photos album, or something else?
ReplyDeleteJulian Bond It's actually a reshare of a photo by Sawanya Prittipongpunt. Not a google photos album -- I will be pleasantly surprised if albums download as individual photos, though I really don't expect it. I'm not sure about multiple photos in a single post. I'll check and get back...
ReplyDeleteJulian Bond I found both kinds of albums. Individual photos from google+ albums are downloaded individually, and in the WP (it's a sign of age -- I think "WordPerfect" when I write the acronym) blog entry they just show as a bunch individual photos vertically down the page. Unfortunately my WP blog isn't yet on a public server, so I can't show it. Might depend on the theme.
ReplyDeleteGoogle Photos albums, on the other hand, just show as a google photos url: eg photos.google.com - Angkor
Ok. The reason I ask is that there's no reason for photos hosted by Google Photos to disappear. The URLs should continue to work. But for "G+Photos from posts" that's not clear. They may survive, they may not.
ReplyDeleteAlways assuming that Google Photos keeps going. It won't shut with G+, but that doesn't mean Google won't decide to shut it at some stage in the future.
Yes, it looks as if Google Photos is "safe" - for the time being. That said, I've downloaded all of mine, largely because a recent computer crash cost me a LOT of my photo files, and this is one way to at least restore the jpeg versions I've uploaded to Photos.
ReplyDeleteJulian Bond Indeed. I have ~60000 photos in google photos -- it basically serves as my offsite backup. I also pay for extra storage space. I don't know how many people are in my position, but I do think it would be harder for google to shut down a paid service. That said, I just converted my flickr account to "pro" ($50/year), with unlimited storage, and I am busily copying all my photos over there as well.
ReplyDeleteVery valuable experience, in a way.
Pat Kight Raw files are a special problem, aren't they -- they just take too much bandwidth to upload anywhere.
ReplyDeleteI'm doing an export of a community with a bunch of g+ album links in it that render as images in g+ but are just broken links in the export. I hoped that 1.7.2 would fix that up based on this post, but no such luck.
ReplyDeleteI sent a help request for this but haven't heard back yet. 🤞
Kent Crispin Early this year, I bought storage on CrashPlan and backed up all my photos onto it. It's not cheap, but it's already paid for itself when, not long afterward, I had a massive computer crash and was able to recover almost all of my RAW files, along with almost everything else. (Recovery was VERY time-consuming, but I lost very little of value).
ReplyDeleteMichael K Johnson I wonder what is different in your case. I also did the export of images and the image list (two separate, additional steps). And I did the export on a linux system. I just did the export of my own profile, not a community.
ReplyDeleteI'm sure the difference is how people did the posts. There are probably eleventy-one possible variations.
ReplyDeleteExample post is https://plus.google.com/114764801971637832887/posts/Fd9Nrt98nRc where the images in comments show up in g+ but the exporter just shows a link to the album. There's something special that g+ is doing to reach through to the album that the exporter doesn't seem to know about (yet?).