Hi Folks,
Good Day!
I uploaded a asset in the AEM publish instance but it is not showing up as a preview.
I know I should not be uploading a asset directly into the publish instance, I have done it just out of a curiosity and I want to understand what are the things behind it.
Thank You.
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hi @Nitesh-Chavan ,
When you upload an asset directly to the AEM Publish instance, it bypasses the normal workflow that ensures the asset is properly processed, indexed, and replicated. In AEM, the recommended approach is to upload assets to the Author instance first, where they go through various processes like rendition generation, indexing, and approval. These assets are then replicated to the Publish instance, ensuring they are fully integrated into the content pipeline and accessible on the live site.
Since the Publish instance is typically read-only, it doesn't have the mechanisms in place to generate renditions or properly handle assets like the Author instance does. As a result, the asset you uploaded might not be processed correctly, and that's likely why it's not showing up as expected in the preview.
Key Points to Consider:
If you're doing this for testing or curiosity, I recommend uploading the asset to Author first and then replicating it to the Publish instance for the full preview experience.
Let me know if you need any further clarification!
Thanks
Ritesh Mittal
Hi,
There are some workflows (and other processing tasks) that are not active on the publisher, which may explain an odd behavior. Also, keep in mind that, although it’s possible, you should not use the publish instance as the author instance for previewing or performing other author-related tasks. You should handle images on the author instance and replicate them once they are ready for use by the final user.
Hope this helps.
Hi @Nitesh-Chavan ,
When you upload an asset directly to the AEM Publish instance, it bypasses the normal workflow that ensures the asset is properly processed, indexed, and replicated. In AEM, the recommended approach is to upload assets to the Author instance first, where they go through various processes like rendition generation, indexing, and approval. These assets are then replicated to the Publish instance, ensuring they are fully integrated into the content pipeline and accessible on the live site.
Since the Publish instance is typically read-only, it doesn't have the mechanisms in place to generate renditions or properly handle assets like the Author instance does. As a result, the asset you uploaded might not be processed correctly, and that's likely why it's not showing up as expected in the preview.
Key Points to Consider:
If you're doing this for testing or curiosity, I recommend uploading the asset to Author first and then replicating it to the Publish instance for the full preview experience.
Let me know if you need any further clarification!
Thanks
Ritesh Mittal
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies