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

aneeta45259594
aneeta45259594
Offline

Badges

Badges
17

Accepted Solutions

Accepted Solutions
27

Likes Received

Likes Received
48

Posts

Posts
67

Discussions

Discussions
24

Questions

Questions
43

Ideas

Ideas
1

Blog Posts

Blog Posts
0
Top badges earned by aneeta45259594
Customize the badges you want to showcase on your profile
Re: Publish Referenced Pages - Adobe Experience Manager 15-10-2018
dmitryp96795211​I think the functionality you're looking for is mentioned in [1]. In Touch UI, the page references are calculated only when a particular configuration, called the "WCM Authoring Content Reference Configuration" is configured to list the reference component in the OSGi configuration [1]. These references then start appearing under "Borrowed Content" in the reference rail.Best Regards,Aneet Arora[1] Developing AEM Components

Views

5.2K

Likes

0

Replies

0
Re: can experience fragments be exported in json format? - Adobe Experience Manager 15-10-2018
littlegreywolf​Export from AEM to Adobe Target currently only exports the HTML and there isn't any way to export it as a JSON. However, this appears to be in the roadmap for a future release of AEM. It will be included in the release notes of the AEM version in which it's released under reference number CQ-4238696Best Regards,Aneet Arora

Views

2.1K

Likes

0

Replies

0
Re: Dispatcher not retrieving content with Vhost but will display already cached content - Adobe Experience Manager 11-10-2018
Hello kentt20248023​This isn't a dispatcher or a caching issue. The publisher specifically denied the request and it's likely due to the fact that at first you're hitting the website with http protocol, Firsltly, http://staging.OURSITE.com/viewall/nutrition/just-eat-half​ fails the first time because the Publisher isn't configured to accept http traffic. I am assuming that staging.oursite.com is the Load Balancer and it should be a https site rather than http. Please test this with https:// prot...

Views

2.5K

Like

1

Replies

0
Re: Dispatcher not retrieving content with Vhost but will display already cached content - Adobe Experience Manager 11-10-2018
Hello kentt20248023​DispatcherUseProcessedURL basically means that the dispatcher will processed/rewritten URL rather than the originally supplied URL to the webserver and the setting being set to "1" is accurate. However, you must confirm that the web server that's hosting the dispatcher has been restarted ever since you've made this update.If the above has been followed, could you please set the DispatcherLogLevel to trace i.e. DispatcherLogLevel trace instead of DispatcherLogLevel 3, restart ...

Views

2.5K

Likes

0

Replies

0
Re: installation progress from log - Adobe Experience Manager 09-10-2018
Hello,AEM operates on the basis of bundles and the progress of AEM install can be measured based on the STARTLEVEL reached for those bundles.The STARTLEVEL ranges from 1 to 30 and messages such as the following can help give you an understanding of how far AEM is along the installation process. And then you'd see a message stating Startup finished in certain number of seconds confirming the 100% install.08.10.2018 13:26:38.763 *INFO* [FelixDispatchQueue] org.apache.felix.framework FrameworkEvent...

Views

1.6K

Likes

2

Replies

0
Re: AEM 6.1 Page showing in CRX content Manager but not Site Admin - Adobe Experience Manager 09-10-2018
ryang81409263​The reason this might have happened is because of the permissions of the user who deleted the page. This page might have been replicated at some point but the user who deleted the page didn't have replicate permissions. You can check this by observing if there is a deleted and deletedBy flag in jcr:content node of this site. When the deleted flag is applied, the page is hidden from the siteadmin so no other author can work on a page which is marked for deletion. I hope this helps.B...

Views

1.2K

Likes

0

Replies

0
Re: exclude page paths from search querybuilder - Adobe Experience Manager 08-10-2018
Hello rajeevy89244319​Try something like below where the first operand indicated the path for your NOT criteria, second operand is for the path you wish to query, and third operand is basically a property to query. select * from [cq:PageContent] where (NOT isdescendantnode([/content/we-retail/ca/en]) AND isdescendantnode([/content/we-retail/])) AND [jcr:title] is not nullBest Regards,Aneet Arora

Views

7.9K

Like

1

Replies

1
Re: [Dispatcher] .stat file not generated - Adobe Experience Manager 02-10-2018
rajas66269496​That's my understanding as well. And my response addresses that with some more details.To answer your question, it is not the right expectation that .stat file will be generated in all the directories in the cache. So I answered the question stating "why is it not appearing" because the "statfileslevel" is set to "1", which means .stat files will only be generated at docroot and one level below docroot, that's it. Please test this out on your end as well for confirmation.

Views

3.3K

Like

1

Replies

0
Re: Sling mapping issue - Adobe Experience Manager 02-10-2018
Hello qglez​When considering etc mappings, you always have to remember one major consideration i.e. the dispatcher cache. The reason I am mentioning this is because it's a fairly critical implication that goes unnoticed. Before I get to the html stripping part, I'd like to focus on the path shortening and also the fact that you don't need to write any sling mapping rules for /bin, /etc, or otherwise. When you create sling:mappings, you define a sling:InternalRedirect and in that internal redirec...

Views

4.9K

Likes

0

Replies

0
Re: [Dispatcher] .stat file not generated - Adobe Experience Manager 02-10-2018
Hello Manh,The behavior you're seeing is expected. It's because you've added the statefileslevel with a value of "1". The value of "1" means that there will be two .stat files, one at the docroot itself, and another one at docroot and one at the /content directory. So you should see a .stat file in the /mnt/cache and at /mnt/cache/content directories. If you wish to see a .stat file generated for every single one of your content levels, you'll have to change the statfileslevel to "6", or "7" or ...

Views

3.3K

Like

1

Replies

0