Portal Administrators can enable staging for Blogs. This means that bloggers can publish blog entries using staging. If those blog entries contains adaptive media images, we need to ensure that the content is properly published and that it points at the appropriate image.
When staging is enabled and the user creates a blog entry, all the images included in that blog entry will point at the image stored in the staging group (not the image in the live group). Then, if the URL is hardcoded in the blog entry content, we need to update the blog entry content so when it gets published it will point at the image stored in live (and not in staging) because otherwise, when we disable staging, all those links will be broken.
If we are not hardcoding url and we are just using a placeholder to ensure that we always use the latest available resolutions (
LPS-70229) we need to ensure that when staging is enabled and the blog entry contains adaptive media images, the dynamically generated urls are pointing at the images in the staging site but when they are published the dynamically generated urls are pointing at the live site. If the placeholder also contains a static url (as fallback url) that static url will also need to point at the appropriate version (staging or live)
- When viewing a blog entry in staging, all the urls need to point at the images stored in the staging site.
- When viewing a blog entry that was published, all the urls need to point at the images stored in the live site.
- Urls pointing at a adaptive media image in a staging site should only be accessible by users have permission to view the content in the staging site.
- The behaviour should be the same as document library urls in a web content article.