As some of you may know, article attachments are affected by the article's "visible to".

Even if someone knows the permalink of an attachment or image attached to an article, they cannot view or download the attachment with that link alone. If he doesn't have permission to view the article.

However, these security rules sometimes put us and many article publishers in great trouble.

Let's assume the following situation.

You are the article publisher and you have published an article named "A" that contains an image named "A1".

And after a few days you decide to create a new article "B" rather than edit article "A".

You create article "B" by Ctrl+c & Ctrl+V of everything in article "A".

Then you publish article B, and archive article A.

So, what will happen?

Tada! All images in article B appear as broken images to the end user.

Why is this happening?

"Article attachments are affected by the article's "visible to"."

Going back in time, the image A1 contained in article A remains A1 when copied to article B, rather than becoming B1.

Image A1 is within article B, but is affected by the "visible to" of article A.

So if you change the "visible to" of article A to admins, or archive article A, the image A1 contained in article B will be invisible to the end user.

Moreover, it is difficult for you to notice this problem. Because you have permission to all articles, the image in article B will look fine.

You may not notice this problem. Until the end user calls you and tells you, "I can't see any images from article B!!"

I would like to suggest

When I Ctrl+c & Ctrl+V article A to create article "B", I want the images to be dependent on B and not on A. So if the A1 image becomes B1, everyone will be happy.

What do you think? Have you ever been reported to have a broken image, but ever said, "It looks normal to me, isn't there something wrong with you?"

I think this issue is urgently needed for improvement.