Are you going to fix them?
Can you show me an example? If people are posting links to broken images, we can't control that.
What's interesting is that if you click on the link in the previous post, you won't see the images but if you then click on the Quote button, you will see the images correctly in the reply window.
I think there is a bug involving the image proxy system and the redirect. You are linking to an attachment using the old URL. This is being redirected to the new URL but the image proxy might be messing it up. I'll have to talk to the devs.
In addition to old links that used to work before the new software, I cannot get a new image to work. It appears correctly in the edit window but in the preview window I see a button that says "View attachment 12345". When I click on the button, I get an error message saying, "You do not have permission to view this page or perform this action." I suspect your developers have the permission and so they don't see the problems I am describing.
Here, let me upload and image:
Right now, while I'm editing this post, I can see the image. But if I click the PREVIEW... button I see a button that says, "View attachment 73532" in place of the image. Now I'm going to POST REPLY and see what happens.
Well, it does display the image correctly, but it shouldn't give me all this confusion during editing of a post. And the original problem persists. Your developers should not be having a challenge to fix this problem. As I said, in a post where the images are broken, I can click on Quote and the images appear correctly.
I see now that the function of the Quote button has changed and so my above instructions are no longer correct. Let me start again.
Go to this link:
You will see two graphic X's in the post.
Scroll to the bottom of the post and click on the Reply button.
Now you see the images correctly.
How hard can this be to fix?
I fixed it for you. If you edit the post and switch to bbcode editor you'll see your linking the images to the old attachment URL. You need to reinsert them and the system will use the new attachment URL.
This problem persists for all posts. I have uploaded hundreds of diagrams. I cannot edit the posts. Here's one of my first:
Can you explain to me why the system can't display the images on the above link but if you click on Reply, it can? If the new system is able to link to the old attachment URL in the Reply window, why can't it link to the old attachment URL in the post?
Looks that the differences between the old system and new system somehow break the way old attachments are displayed, and it is not only a problem with your posts. That means it may require a forum-wide changes - please wait a few days as Greag is working through the 2do list. Be sure we want all these images to display correctly :)
Thanks, that's what I wanted to hear.
It's been 10 days now, how far up on the 2do list has this problem gotten?
Click on this link to see the problem:
Let me re-iterate, if you click on the above link, you can see the images displayed correctly in the thumbnails at the bottom of the page and if you click on "Reply", the full-size images will be displayed correctly in the edit window. I don't see why this problem is taking so long to get fixed.
The problem is that we are using SSL, because we are using SSL we have to use a image proxy. At the moment the image proxy will only cache publicly viewable images. Because the images in your posts were added via an image tag using the private attachment url, they are not publicly accessible. I am still trying to work on a reasonable solution.
I used PF's upload and image display features. The images are not on some other URL. Did you click on the Replay button after going to the example page I linked to? If the images display correctly in the edit window, why can't they be displayed correctly in the post? It doesn't make any sense to me.
I am assuming the edit window doesn't engage the image proxy. What doesn't make any sense to you?
It doesn't make sense to me that you have two windows that are taking exactly the same source from your database, one of them does not display the image (it puts a big X in place of the image) and the other one does display the image correctly. Why can't your developers look at how the edit window correctly displays the images and do the same thing in the post?
The purpose of the image proxy is that because we are using SSL, everything loaded on a page within our domain must come from a secure location as well. Most image hosts are not secure. If you load insecure elements to a supposedly secure website you'll receive browser warnings. The image proxy caches the image on our server from which it will now load from. It must come from a publicly accessible location. The attachment system is not public.
The edit window is ajax loaded and not public so there isn't a need to load the image proxy into it. I agree it's confusing, but that is the way it is.
As I said, I am searching for a solution for your case.
I can understand your explanation if my images were uploaded to an insecure image host, but they are uploaded to PF's image host. Are you saying that your own image host is insecure?
It's secure, but it's not public
Separate names with a comma.