Reposting this comment, which I originally made on Bug 1520328:
In fixing this, it should be noted that you also need to test for whether the embedded image is visible to other users:
1. Share the page with another user (or with "Public" or "Registered users")
2. View the page as another user and see if the image displays properly.
A user's permission to view a page is currently tracked via several different tables, at least one of which must have an appropriate record:
- artefact_attachment: For classic "attachments", like those on notes, blog entries, and comments
- view_artefact: For artefacts displayed directly by selection in a block (e.g. the image block)
- artefact_file_embedded: For images embedded in another artefact's rich text fields
The import process must populate any of these that are appropriate, in order for it to work correctly.
Reposting this comment, which I originally made on Bug 1520328:
In fixing this, it should be noted that you also need to test for whether the embedded image is visible to other users:
1. Share the page with another user (or with "Public" or "Registered users")
2. View the page as another user and see if the image displays properly.
A user's permission to view a page is currently tracked via several different tables, at least one of which must have an appropriate record:
- artefact_ attachment: For classic "attachments", like those on notes, blog entries, and comments file_embedded: For images embedded in another artefact's rich text fields
- view_artefact: For artefacts displayed directly by selection in a block (e.g. the image block)
- artefact_
The import process must populate any of these that are appropriate, in order for it to work correctly.