Hi everyone, below is new official Jira/Atlassian thread on this paste image topic from Daniel Gutierrez (who works in the Atlassian founders office and set this up).  Let's all try to rally around this new official thread and vote to get this issue fixed once and for all:

Thanks for your interest in this use-case! I've opened a feature request on jira.atlassian.com for you watch and vote on: JRACLOUD-71695

I'm also locking this particular thread for comments as it is dated and we want to make sure your comments and feedback get the attention they deserve. Please create a new question on Community if you need help with a particular aspect of Jira's current behavior. And if JRACLOUD-71695 completely captures what you're looking for, please watch it to keep up with any changes planned in Jira.

Thanks!

Daniel | Atlassian Support

patrijst There wasn't so i created this ticket for you to vote on https://jira.atlassian.com/browse/CONF-43522.
Feel free to explain your use case for having confluence upload the image instead of referencing the source. Thanks!

Thanks, is there an issue I can vote for that would upload copied web images?

patrijst This issue was addressed for copying images within the same confluence instance. When you paste across instances, that will be the same behaviour as if it was a web image link because thats what it is.

This doesn't seem fixed.. pasting Confluence content from one instance (different) to another (5.10 to 5.9) will add the images as a referal to the other instance instead of upoading it as new images.

Today i run into this problem. Hope this will fixed in the near future.

Hi guys!

I am not an IT expert, hence I do have some queries regarding the busted stuff report:
I have now downloaded python 2.7.3 - but I have no clue how to run the busted stuff report. is there a documentation somewhere around where I can read what needs to be done step-by-step?

thanks a lot!

christian

Hi Sarah,

Thanks for the tip, especially about using the Source Editor plugin. I have been annoyed by the problems that can occur when you copy a page containing images, when those images are actually attached to, well, who knows where?

Now that Confluence is moving/has moved to the Rich Text editor and XML I think I'll be using the Source Editor plugin more often. In other words, the more confluence makes things easier for some users, it's nice to have a way to easily look under the hood when we want to.

Robie

Hallo Christian

In answer to your question about identifying affected pages: You can use the "Busted Stuff Report" created by Ed Dawson:

• http://blogs.atlassian.com/2011/12/scanning-confluence-for-content-errors/
• https://bitbucket.org/edawson/busted-stuff-report

To prevent the problem from recurring, you can use the Source Editor plugin. It pops up a source window in the editor that shows the XML source (storage format) of the page. If you copy the storage format rather than the rich text, all your images will remain relative. So will your links – this may be important to you too.
https://marketplace.atlassian.com/plugins/com.atlassian.confluence.plugins.editor.confluence-source-editor

If you and all editors have admin rights on your Confluence site, you can do that without the Source Editor plugin. Admins can see a "View Storage Format" option in the "Tools" menu.

You'll still need to re-attach all your images to the new page. But at least they won't be misleadingly there and referring back to the original page.

Cheers
Sarah