Resolved - Bug Squashed Inline images referencing an old version of attachment URLs are not working

This bug has been squashed
Jump to Latest
#2
Exhibit A above references missing images. I'm on the hunt for "broken links" now - any examples where a link to the old site no longer links to this site (at all or incorrectly)? Please tag me ASAP you find one of those.

I have found an earlier report of google search revealing links that the user reported as broken. I have subsequently verified that that same search works for me - so possibly google has updated its cache but that doesn't mean every incoming link site will have done so.

A couple of solid and verifiable examples will really help here.
 
#7
Pano said:
Interesting, thanks for the example. Looks like the image links got rewritten or truncated.
@xrk971 Where these gallery images? Links to attached images? Do you remember?
Click to expand...

Typically, these images are in found later on in the same thread. Sometimes posted in anothe thread.

For example, the first broken link is:

802945d1576612905-10f-rs225-fast-speaker-xo-pcb-gb-10f-rs225-speaker-system-photo-jpg

I believe the image referenced came from here::
:
https://www.diyaudio.com/community/threads/10f-8424-rs225-8-fast-waw-ref-monitor.273524/post-5789339
Edit: I just tried to look for this thread on the wayback machine to see if I could find stuff. The wayback machine said it could not find the present URL for this thread:
"https://www.diyaudio.com/[/URL]community/threads/10f-8424-rs225-8-fast-waw-ref-monitor.273524/"

But, I searched a link to this thread in my shop, and it shows this:
"http://www.diyaudio.com/forums/full-range/273524-10f-8424-rs225-8-fast-ref-monitor.html"

And indeed, on the wayback machine, this thread shows up when using theold URL, and has been around since 2015 and uploaded to wayback 42 times.

It appears that the migration was used as an opportunity to change the site's architecture or directory structure en-masse, renaming "/forums/full-range/" into "/community/threads/" and appending .273524 to the end of the URL.

I believe a temporary solution to this might be to restore and place online, a legacy static website using the identical root tree structure as the old website, and this will allow those links to find their content.
 
Last edited:
#13
Other than that the new site is very pleasant.
Click to expand...
Umm... nothing pleasant without functionality. As XRK mentioned elsewhere, saving images on a forum's server is considered safer & better for longevity than saving them elsewhere, but it appears that a majority of the images that work here now are hosted elsewhere.
 
#14
Hey guys. I have split the discussions about this very specific case of mangled image URLs into its own ticket.

We are currently investigating this issue.

EDIT UPDATE: We're narrowing down on this, hope to have a fix up within 24 hours.
 
Last edited:
#19
Sure thing. That particular attachment link structure could have been from any of the following incarnations of link structure that we've had over the last 20+ years:

  1. Around 2001 we started using vBulletin version 2
  2. Around 2010 we moved to vBulletin version 3
  3. Around 2014 we started using vB SEO which preferred search engine friendly links
  4. Around 2018 we migrated to dB SEO because vB SEO was now unsupported and had lots of security risks
Those links could have come from copying the actual attachment link, or perhaps what appeared in the URL bar, or any other mechanism, and could have been borne from any of the 4 different iterations of link structures.

Whatever link structure it was, our development partners (who are XenForo experts) had never seen it before, so it wasn't planned for or easily recognizable. After some detective work, we resolved it with an NginX regular expression rewrite rule to strip out the attachment id and rewrite the URLs to the new attachment URL structure.
 
You must log in or register to reply here.
Top Bottom