Google Drive image posts have broken?
Jan 27, 2024 23:54:47 GMT
Philatarium, khj, and 4 more like this
Post by Ryan on Jan 27, 2024 23:54:47 GMT
Earlier today, ameis33 (Roberto) posted a line in the Shoutbox advising of problems with his older Google Drive image links being broken. By looking at his recent posts, he has been using the TSF Image Host for his latest image links but for posts from around May 2023 and older, Google Drive was used. All of these image links are now showing as broken and from what I can figure out, it's a matter of the link being malformed by the ProBoards software TSF uses - it's not that Google Drive is not permitting the use of the links or something like that.
Have a look at this post from the Italian parcel post thread. 6 image links, all of them broken. I have moderator powers so I can use them to edit his post in order to look at the BBCode for the images. I can't post that text because the ProBoards software fiddles with the URL links and that's what seems to be the problem, so what follows is a screen capture, not something typed in by me as text.
Every image source tag includes "view & amp; id=" - I have added spaces into that because if I don't the TSF board software tries to convert it as BBCode (and in fact, it messed with my attempt to explain my edit on Roberto's post, correctly converting that as BBCode and leaving behind something that doesn't make much sense). If you were to cut & paste those image source tags directly into a browser as a URL, the link breaks and you get this.
But if the "amp;" portion of the image source tag is stripped out so that we now have "view & id=", then those direct links work.
drive.google.com/uc?export=view&id=152IK4_6puoFEznamD0vscak11qX46L1S
drive.google.com/uc?export=view&id=1T_Fi9rCIeNnXN-UBuv9v2vqW5d94sjCv
etc.
If the post is edited in BBCode mode in order to strip out the "amp;" portion of the image tag, the board software puts it right back in and the link stays broken. And oddly, if the URL is put into the Shoutbox, if it includes that "amp;" portion the Shoutbox strips it out and the link works ...
Admin, you may or may not have the ability to figure out what is going on with this automatic conversion of the "&" in a URL into the HTML equivalent which seems to be breaking the Google Drive image link. khj, any ideas? Anybody else with some technical chops on ProBoards software?
Ryan
Have a look at this post from the Italian parcel post thread. 6 image links, all of them broken. I have moderator powers so I can use them to edit his post in order to look at the BBCode for the images. I can't post that text because the ProBoards software fiddles with the URL links and that's what seems to be the problem, so what follows is a screen capture, not something typed in by me as text.
Every image source tag includes "view & amp; id=" - I have added spaces into that because if I don't the TSF board software tries to convert it as BBCode (and in fact, it messed with my attempt to explain my edit on Roberto's post, correctly converting that as BBCode and leaving behind something that doesn't make much sense). If you were to cut & paste those image source tags directly into a browser as a URL, the link breaks and you get this.
But if the "amp;" portion of the image source tag is stripped out so that we now have "view & id=", then those direct links work.
drive.google.com/uc?export=view&id=152IK4_6puoFEznamD0vscak11qX46L1S
drive.google.com/uc?export=view&id=1T_Fi9rCIeNnXN-UBuv9v2vqW5d94sjCv
etc.
If the post is edited in BBCode mode in order to strip out the "amp;" portion of the image tag, the board software puts it right back in and the link stays broken. And oddly, if the URL is put into the Shoutbox, if it includes that "amp;" portion the Shoutbox strips it out and the link works ...
Admin, you may or may not have the ability to figure out what is going on with this automatic conversion of the "&" in a URL into the HTML equivalent which seems to be breaking the Google Drive image link. khj, any ideas? Anybody else with some technical chops on ProBoards software?
Ryan
