Changing destination of user generated content image uploads from AEM journal/blog | Community
Skip to main content
davidevg09
davidevg09
Level 2
March 28, 2018
Solved

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

  • March 28, 2018
  • 3 replies
  • 1344 views

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

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by kumarashok

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.

3 replies

kautuk_sahni
Community Manager
kautuk_sahniCommunity Manager
Community Manager
April 6, 2018

Checking with Internal team!

-Kautuk

Kautuk Sahni
K
Adobe Employee
kumarashokAdobe EmployeeAccepted solution
Adobe Employee
April 6, 2018

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.

T
titli
Level 2
September 24, 2018

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

Terms & ConditionsAccessibility statement

Loading footer...