Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

Changing destination of user generated content image uploads from AEM journal/blog

Avatar

Level 2

When using the rich text editor through the journal/blog component, uploading an image sends it to the following destination: /content/usergenerated/tmp/social/images/...

Is there any way I can update a certain file to have any uploaded images from any of my journal/blog components send the images to a folder of my choice? Ideally I want all usergenerated image uploads to be sent to a folder of my choice under the  /content/dam directory.

I'm using AEM 6.3

1 Accepted Solution

Avatar

Correct answer by
Employee

There is no extension made available to  achieve this.

Reason:-

/content/usergenerated/tmp/social/images/* is a temporary location to upload and file finally gets stored along with actual UGC in mongo ( for MSRP) , mySQL ( for DSRP) . Since SRP resides out side JCR , your images are accessible from all the publish instances without relying on replication. putting these files in dam would make them instance locked or rely on replication to distributed across all publish instances.

The main advantage of putting images in dam is to extract metadata and renditions via dam workflows. Whereas UGC is always get created on a publish instance and dam workflows are not recommended to configure there.

View solution in original post

3 Replies

Avatar

Administrator

Checking with Internal team!

-Kautuk



Kautuk Sahni

Avatar

Correct answer by
Employee

There is no extension made available to  achieve this.

Reason:-

/content/usergenerated/tmp/social/images/* is a temporary location to upload and file finally gets stored along with actual UGC in mongo ( for MSRP) , mySQL ( for DSRP) . Since SRP resides out side JCR , your images are accessible from all the publish instances without relying on replication. putting these files in dam would make them instance locked or rely on replication to distributed across all publish instances.

The main advantage of putting images in dam is to extract metadata and renditions via dam workflows. Whereas UGC is always get created on a publish instance and dam workflows are not recommended to configure there.

Avatar

Level 2

So if we use JCR as the SRP then the images will keep getting deleted. What is the solution for that? ashokkumar