Question Out of curiosity!! A asset upload in the AEM publish instance. | Community
Skip to main content
Nitesh-Chavan
Nitesh-Chavan
Level 3
November 19, 2024
Solved

Question Out of curiosity!! A asset upload in the AEM publish instance.

  • November 19, 2024
  • 2 replies
  • 521 views

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.

Best answer by Ritesh_Mittal

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:

  1. Rendition Generation: Renditions (e.g., different image sizes or formats) are only created in the Author instance, not on Publish. The asset in Publish won't have these renditions, which can affect its display.
  2. Replication: Normally, assets uploaded to Author are replicated to Publish, ensuring they are available for the live site and correctly linked with any content.
  3. Previewing Assets: The Preview functionality works best when assets are uploaded to Author and then replicated to Publish. Without this workflow, the asset might not be processed correctly for preview or display.

 

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

2 replies

EstebanBustamante
Community Advisor and Adobe Champion
EstebanBustamanteCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
November 19, 2024

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.

Esteban Bustamante
    Ritesh_Mittal
    Community Advisor and Adobe Champion
    Ritesh_MittalCommunity Advisor and Adobe ChampionAccepted solution
    Community Advisor and Adobe Champion
    November 19, 2024

    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:

    1. Rendition Generation: Renditions (e.g., different image sizes or formats) are only created in the Author instance, not on Publish. The asset in Publish won't have these renditions, which can affect its display.
    2. Replication: Normally, assets uploaded to Author are replicated to Publish, ensuring they are available for the live site and correctly linked with any content.
    3. Previewing Assets: The Preview functionality works best when assets are uploaded to Author and then replicated to Publish. Without this workflow, the asset might not be processed correctly for preview or display.

     

    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

      Terms & ConditionsAccessibility statement

      Loading footer...