An OP full of broken pictures…

Bob Blaylock

Bob Blaylock

Senior Member
See http://nikonites.com/learning-photography/24694-drip…drip…drip…drip…drip….html

A baker's dozen of pictures in the OP, were visible while I was previewing before I saved the post. After I saved it, the pictures wouldn't display. The forum produces links to them which get caught in redirection loops.

I went back in and edited the post. Failing less drastic things, I ended up deleting all the pictures, then reinserting them from the “Manage Attachments” window. I saved this change, and the first time the thread was loaded, all the pictures displayed.

I then tried to post a reply to someone else, who had wondered why he couldn't see the pictures. The browser got caught in some sort of loop, trying to save that reply (which never got saved), and then once again, the pictures are broken as before.

I've been jumping back and forth between two different computers, running two different browsers—A Power Macintosh G4 running TenFourFox under MacOS X 10.4.11, and a PC running Google Chrome under Windows XP.

Clearly, the problem is on Nikonites' side. The pictures are there, on your server, but the message is being displayed using defective HTML code that produced redirect loops when it tries to display the pictures. Same thing happens on two completely different browsers, running under two completely different operating systems, on two completely different computers.
 
Horoscope Fish

Horoscope Fish

Senior Member
If the issue was with the Nikonites server or 'page I think we'd be hearing from more users about the issue...

Have you *thoroughly* flushed the browsers cache and cookies lately?

....
 
E

Eyelight

Senior Member
Bob Blaylock said:
See http://nikonites.com/learning-photography/24694-drip…drip…drip…drip…drip….html

A baker's dozen of pictures in the OP, were visible while I was previewing before I saved the post. After I saved it, the pictures wouldn't display. The forum produces links to them which get caught in redirection loops.

I went back in and edited the post. Failing less drastic things, I ended up deleting all the pictures, then reinserting them from the “Manage Attachments” window. I saved this change, and the first time the thread was loaded, all the pictures displayed.

I then tried to post a reply to someone else, who had wondered why he couldn't see the pictures. The browser got caught in some sort of loop, trying to save that reply (which never got saved), and then once again, the pictures are broken as before.

I've been jumping back and forth between two different computers, running two different browsers—A Power Macintosh G4 running TenFourFox under MacOS X 10.4.11, and a PC running Google Chrome under Windows XP.

Clearly, the problem is on Nikonites' side. The pictures are there, on your server, but the message is being displayed using defective HTML code that produced redirect loops when it tries to display the pictures. Same thing happens on two completely different browsers, running under two completely different operating systems, on two completely different computers.
Click to expand...

According to the FAQ that is what happens when there is a hiccup during the upload. The image may not be on the server yet. Did you try uploading fewer images?
 
J

jdeg

^ broke something
Staff member
This is a special case. The name of the thread is throwing things off. I'll have to report this issue to the makers of the software we are using.
 
Bob Blaylock

Bob Blaylock

Senior Member
jdeg said:
This is a special case. The name of the thread is throwing things off. I'll have to report this issue to the makers of the software we are using.
Click to expand...

That appears to be the problem, though it's odd I've never tripped over it before.

I created a new thread avoiding the use of non-ASCII characters in the title, and inserted the same images (I did not re-upload them; I used the “paperclip” icon to insert the instances I had already uploaded.) and that thread appears to have no problem.

But yes, this would be a bug in the software. If the software is going to allow non-ASCII characters in the title of a thread, and if it is going to incorporate the title into the addresses to display pictures in that thread, then it needs to make whatever workaround it must to insure that these characters don't mess up the image addresses.

I must say I am at a loss to understand the whole scope of the problem. What ends up happening in the thread with the problem is that the addresses to the images end up getting caught in a redirect loop.
 
J

jdeg

^ broke something
Staff member
Yep, that's exactly what needs to happen :) You'll see that the dots are encoded in the URL of the thread, but not in the location of the images. It didn't happen before because I changed the software that is used to do the rewriting of the URL's last week. The old one was no longer supported and the new one still has some bugs. I'm pretty sure they are filtering most ASCII characters, but dots in a row is currently not being accounted for.
 
Top