10

Before I jump on to the problem, let me first congratulate Jon Chan and his team for the newly re-designed Stack Exchange blog. I like it very much, great job!

While searching on Google, I stumbled upon Customizing stackexchange.com blog post of Jeff Atwood and found few broken images. There are currently four images are broken on this post, Here is one of them:

Upon doing an inspect element on one of the broken image (same goes for all other broken images on the post), I found out that it is currently pointing to:

http://blog.stackoverflow.com/wp-content/uploads/stackexchange-genuine-example11.png

The newly re-designed Stack Exchange blog is now moved to a new location: http://blog.stackexchange.com and the old blog URL i.e. http://blog.stackoverflow.com has the correct mapping of URL redirection (also called URL forwarding) and works perfectly.

But, the problem lies in the latter part i.e. /wp-content/uploads/ directory structure does not exist anymore at the new blog location. I read the Jon Chan's How We Built Our Blog post (nice writeup! btw) where he talks about his custom Python script. Here is the relevant excerpt taken from that post:

I wrote a Python script to go through all the imported posts, looked for references to WordPress hosted content, download all the static assets into images/wordpress in the repo, and changed all the links to relative paths on Jekyll. Worked surprisingly well.

In other words, all of the old /wp-content/uploads/ static assets is now resides under the /images/wordpress/ directory at the new blog location. So, Jon's find and replace script should have worked (which it did for the most of the part) as intended to be but apparently it did not catch few of them. At least on this blog post and few other like Welcome Valued Associate Nick Craver, Logo Design Contest or Stack Overflow Beta Design. We could possibly have more but these are the ones I have found so far.

I believe it's a minor bug somewhere in the script and could be fixed with few lines of code tweaking. Also, the static content link mapping problem would not have occurred at all if the directory name was unchanged as the URL redirection (as stated above) would have taken care of it. But, there must a reason for this change.

Upon investigating further, I found out that the issue with broken images does not end here. They will still appear as broken even if Jon's script replaces the path to the correct one. Because the images have not been uploaded (or copied) to the blog's new /images/wordpress/ directory at all. They are missing!

For example, try clicking on the following link:

## I replaced old dir. path /wp-content/uploads/ to the new /images/wordpress/ https://blog.stackexchange.com/images/wordpress/stackexchange-genuine-example11.png

So, in a nutshell, in order to fix this broken images link problem, we need to make sure that not only they are pointing to new path i.e. /images/wordpress/ but also do exists (i.e. uploaded) at the blog's new location.

Please fix this at your earliest.

  • @ShadowWizard thanks for editing and adding a broken image snapshot to my post. – HackerKarma Jul 5 '15 at 15:23
  • 1
    My pleasure, though the FHRC is even more important... :-) – Shadow Jul 5 '15 at 17:50
  • Jon Chan, I think your newly re-designed blog also broke SE team members blog URL. The SE team members blog posts are now in the "authors"(as oppose to author) directory. @Jaydles please update your profile page to point the blog link to correct location at: blog.stackexchange.com/authors/jhanlon – HackerKarma Jul 10 '15 at 6:00
  • You know they can't see your comment, right? They don't have a special comment sniffer that monitor all comments around the network. – Shadow Jul 10 '15 at 6:03
  • @ShadowWizard I didn't know that. Thanks. I will use the other route to notify this. – HackerKarma Jul 10 '15 at 12:53
  • 1
    If you have new bug to report it should be done by starting a new question. What "other route" you have in mind? – Shadow Jul 10 '15 at 16:49
  • @ShadowWizard I thought I would be able to get the email id as some of the SE team do post their official email address in their Profile. But, I am out of luck here. I am drafting a new question for this. Thanks. – HackerKarma Jul 10 '15 at 17:03
  • Well, easy enough to get to Jon Chan Facebook profile but yeah, better start new bug report. – Shadow Jul 10 '15 at 17:06
  • 1
    @ShadowWizard Thanks. I thought of that too but decided not to got that route... Anyway, I have posted a new bug report: meta.stackexchange.com/questions/260440/… – HackerKarma Jul 10 '15 at 17:46
  • 2
    This is a known issue. Like you said, the script I wrote should have captured most of the images here, but many of them weren't captured (some of these were actually missing even in the old one). I'm working to recover as many of the images as we can now, but this is something that may take some time to recover. – Jon Chan Jul 27 '15 at 23:08
  • @JonChan Not a problem... I m glad to know that you're on top of it. – HackerKarma Jul 27 '15 at 23:37
  • @Jon any updates, almost 3 months later? In addition to what OP showed here, this blog post also contains the non exitant image blog.stackoverflow.com/wp-content/uploads/… – Shadow Oct 19 '15 at 10:58
  • @ShadowWizard as noted in the post, we're missing some of the images and need to restore them from our backup on a case-by-case basis. I'm going to see what can get done for the posts mentioned here specifically. – Jon Chan Oct 19 '15 at 15:03
  • @Jon thanks, better than nothing I guess - one by one, image by image. – Shadow Oct 19 '15 at 15:04

You must log in to answer this question.

Browse other questions tagged .