Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

NitroHazeDev
NitroHazeDev
Online

Badges

Badges
39

Accepted Solutions

Accepted Solutions
11

Likes Received

Likes Received
159

Posts

Posts
343

Discussions

Discussions
52

Questions

Questions
291

Ideas

Ideas
0

Blog Posts

Blog Posts
1
Top badges earned by NitroHazeDev
Customize the badges you want to showcase on your profile
Re: Questions - Move api for bulk moves, Jcrutils and resource resolver api - Adobe Experience Manager 24-07-2022
My observation on the api is that it creates the entire non existent folder path. The jcr content nodes , that should exist associated to the folder does not get created . jcrutils is not recommended per the last ref doc sent over, @sachinarora so skipping for these reasons Using resourceresolver.create is recommended per the doc and acs folder creator so using it . But looks like it needs saves after every create , which means one for folder and one for jcr content. But this is not super clear ...

Views

37

Like

1

Replies

0
Re: Bulk replication assets and folders- activate/deactivate - Adobe Experience Manager 23-07-2022
@SantoshSai Do you know of unpublish, based on my observations it is the same as replication where it is targeted to the specific path to activate or deactivate via api vs all it’s children. The problem is since not all resources may or may not be published , I can’t replicate the tree . By tree replication, first glance , it is iteration and activating one resource at a time ? It invalidates but does not unpublish IMO ?

Views

51

Like

1

Replies

0
Re: Bulk replication assets and folders- activate/deactivate - Adobe Experience Manager 22-07-2022
I think i might have the answer, let me know your thoughts, not sure of any limitation wrt api replicator.getActivatedPaths(session, path);- get the string path array and then deactivate. String[] pathArray = pathList.toArray(new String[0]);replicator.replicate(session, ReplicationActionType.DEACTIVATE, path);

Views

68

Like

1

Replies

0
Bulk replication assets and folders- activate/deactivate - Adobe Experience Manager 22-07-2022
Hi, Tried checking replicator.replicate option for activate, but it only activates the node and not sub nodes, and node can be a sling folder or dam:asset. The same with deactivate. Is this the expected behavior via api? I would also like to avoid replication of a subfolder A, if there are children in that sub folder , that have not been replicated . Same with deactivation. What is the best approach other than traversal or query builder query? can/should sling query be used?

Views

70

Likes

0

Replies

4
Re: Questions - Move api for bulk moves, Jcrutils and resource resolver api - Adobe Experience Manager 22-07-2022
Thanks @sachinarora .My question would be does .create method auto save? I would have expected jcrutils.createPath to create nodes and jcrcontent if it does not exist , but does not seem to be the case We don't care of references at the moment so i believe assetmanager.move should do , can you please elaborate on sling jobs approach for this.

Views

39

Likes

0

Replies

2
Questions - Move api for bulk moves, Jcrutils and resource resolver api - Adobe Experience Manager 21-07-2022
All, I am trying to create folders and move assets- performing bulk moveAnyone knows 1. if jcrutil.createPath can help me best create nodes that are sling:folders WITH jcr content? I tried using.createPath which created missing nodes but no jcr:content. Want to confirm and know i am not missing something that could help me create a folder with jcr content using createPath command.trying to save on commits 2. Also i ended up using resourceresolver.create , creating folder along with it's properti...

Views

64

Likes

0

Replies

4
Re: Unable to flush dispatcher cache on publish - Adobe Experience Manager 21-07-2022
Thanks both of you @Shiv_Prakash_Patel @SantoshSai I happened to notice that acs dispatcher ttl was set on pub config run mode and was being picked up so that explained the duration that the origin was picking up but it ended up being cloudfront that was not invalidating due to config. Much appreciated guys!

Views

39

Like

1

Replies

0
Re: Unable to flush dispatcher cache on publish - Adobe Experience Manager 20-07-2022
Anyone please? Do we think setting statfileslevel from 1 to 17 would help? or should i set it to doc root 0?

Views

68

Like

1

Replies

0
Unable to flush dispatcher cache on publish - Adobe Experience Manager 20-07-2022
Hi, Anyone knows how this issue can be resolved? We have a dispatcher flush configured on pub prod but the cache invalidation does not appear to be done Reason i say it is dispatcher and not cloudfront , is , ?a=b invalidates it. Unless I am missing something? Anyone knows how i could get past this?

Views

72

Likes

0

Replies

4
Re: ACS-AEM-Generic list- 500 Error thrown - Adobe Experience Manager 08-07-2022
Hi @akashdeepAEM , 4.3.2 may be the best, but compatibility wise there were issues with 6.5 , so we had to bump it up. We do not have any config/rewriter node to rename or temporarily delete. I hope this issue with varying fixes per acs version, where a solution works for one does not work for the other gets resolved at the root itself- i.e. ACS... I haven't had the time to debug it myself.

Views

142

Likes

0

Replies

0