Separate names with a comma.
Discussion in 'Ask Baldy, Blame Cannonshot' started by snowjob, Oct 12, 2015.
Seems my latest shared photos have failed again. My frustration at this one component of Google Photos is HUGE! To recap, the only method that consistently worked was creating a shared link. The link google provides does not work, but once you create it the URL accessed by right-clicking the photo will not only work, but no longer change. I even tried to use a shared album to see if that would help.....nope. I would hope by now there are enough Google Photos users that somebody has got this all sorted.
BTW, here is the picture that keeps failing (using the share-->create link-->right-click, copy address approach):
It seems to work for several hours before failing.
i feel your pain. it also seems to vary on if the people looking at the pics have a google account and are logged in. if you log out of your account @ google, then come back and look at the pic you posted, you will know immediatly if it is going to stay. if you can view it, you're golden, if not there are going to be problems.
Nope. That makes no difference. The pix will still disappear after a few hours.
just testing this out... Say hello, Pup! Is that picture visible to everyone?
See this post for detailed instructions on how to embed images hosted on Google Photos
How to embed from google
Thank you @motokeith. We are on day 2 and the pic is still working. I find it amusing that I created this thread within a day of someone else doing the same as I was pretty sure I searched for it first
Anyhow, to confirm what is now working:
Place photo in an album that has been shared (link)
Open photo within album and right-click, copy link
You can adjust photo size with the end of the link
This is only slightly different than what had been working for me, but will be my new approach until Google breaks it too.
Another with the same problem:
I created the RR with several links. A day or two later, as reported in this thread, several links seem to work, while others do not.
Test picture from Google photos...
That whole "adding jpg to the end of the link" business is completely unnecessary here on a Xenforo board. If you are going to do it anyways, you need to add "?.jpg". The question mark indicates the beginning of query parameters and is what allows ".jpg" to be tacked onto the url to satisfy the dumber board software out there without invalidating your google link url.
The single biggest failure point in embedding photos from Google is not making them shared to the public. This usually shows as the "i can see it but no one else can see it" problem or the "it was visible for a little while and now it's gone" problem. If you are not 100% sure that your photos are publicly viewable then it's a safe bet that they are in fact not.
In another thread I wrote up step by step instructions on what is required to post photos from Google into messages on this board....
Have a look here
ok. mine is acting up again. i have followed the direction in the above link for the last few months and things seemed to be working. i would add the photo to my shared album, then go to that album and click on the pic, i would then "get a link" using the share function, paste that just incase, then right-click and copy image address, then alter the size to 1200p.
now all the sudden all my pics just showing broken link. if i am signed into google i can see them, but as soon as i sign out they are gone and we get the "img" again.
i have shared the album link, i have shared everyone of the photo links, and i have my settings so anyone with a link can view.
what am i doing wrong?
this is just ridiculous!
ok, so i just confirmed all the pics and albums show up in my "shared" portion of google photos. i also went and re-did the last two post in this thread and both pics showed with a size of 1200p. as soon as i log-out of google, the images disappear again.
Here is one of your photos that doesn't show.
Another... Let's see how long this sticks around
Your image links in the airplane thread are returning a "403 Forbidden" error, which makes me suspect there is something wrong with the way they are shared.