I have a folder in my DAM that has multiple content fragments.Folder: /content/dam/brand/cfs/blogContent Fragment 1: /content/dam/brand/cfs/blog/blog-post-1Content Fragment 2: /content/dam/brand/cfs/blog/blog-post-2Content Fragment 3: /content/dam/brand/cfs/blog/blog-post-3The overall goal is to hav...

The answer wasn't specific enough which is why I still asked my question. Exactly where under /etc/designs/ must we define the path to update the resourceType or the entryresourcetype property so that the entry_topic.hbs being referenced is not the one under /libs/

Then what file do we need to update so that we can update the resource type or entry resource type so that our extended entry_topic component is the one being referred to instead of the OOTB component?Because apparently the below code doesn't work for entry_topicSCF.registerComponent('/apps/custom-b...

I agree with this 100%.I'm actually stuck on that issue of the Entry Resource Type. For clarification, where do you apply this property so that I can point it to my custom entry_topic component so that it doesn't point to the OOTB component?

Did you managed to find a solution to this?I'm currently facing this issue where my extended entry_topic component isn't being reflected on my live site. Instead, its the default entry_topic.hbs file that's being referred to under /libs/social/journal/components/hbs/Even when I update my custom entr...

After using the out of the box AEM journal/blog component to create several posts on a page, when I click on a post to view the entry_topic page of the post, is there any functionality available to be able to modify the entry_topic.hbs file to include next/previous links to link to the next or previ...

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...

Thank you very much for the reply!

Nevermind I figured it out.In the dialog of the journal component, under Tag Field tab, set the Suggestion Limit field equal to -1. For me, by default, it was set to 0. Meaning that it would show the pop up of suggested tags when you start typing. I feel like by default it should be set to -1 and no...

I'm trying to add tags to my blog posts whenever I use the Journal component. I have created a list of tags under /etc/tags and it shows up on my journal component's edit dialogue when i enable the option to "Allow Tagging" and then i check off namespaces I allow under the "Allow Namespaces" section...