I am glad to hear you got the value of authorizableId to work. Unfortunately, I have not been able to get their code to work right out of the box. I was able to get currentId, and CQ_Analytics.CustomStoreMgr.initialized to work by using this code in the customstore.js file:// Create the session stor...

AEM newbie wrote...   The value of authorizableId is anonymous ...  Did you try loading a profile into the client context? Once you load a profile into the client context, and refresh the page, you should get the value of the profile you loaded instead of anonymous.

I replied to your other post. I hope that it helps you.

You have included the client context correctly. Once you include that line of code, you can use the client context to view data. Are you following along with the tutorial, or did you install the full code at the very end? I tried doing this tutorial, and if you install the completed code, and try do...

Jason Tarry wrote... Is the reason for working with templateSlightly.jsp (extending foundation/components/page) to be able to use Sidekick in Classic UI? In other words does the side kick only appear if the page component is JSP?Hi Jason,The reason you use the super type is so it will inherit the ma...

I would expect that there are questions on sightly since it is important in AEM 6 and since it takes the place of JSP. I would review the documentation on sightly if you are not familiar with it, and go through articles links that are located on the experience delivers page. Here are some links: htt...

They can be used to achieve the same result, however it would really depend on what you are trying to do.  For example, the <sling:include> can do the same thing as the <cq:include>, but it has more parameters that you can use if you need them. You can read more about the attributes in the Sling doc...

Have you tried installing SP 2 to see if it resolves your issue? I know that the service pack added a lot of hot fixes. You can read more here: http://docs.adobe.com/docs/en/aem/6-0/release-notes-sp2.html.

I am not sure if there is a function to get the directory. However, you can access the logs by just using the "crx-quickstart" when using the file path. For example: InputStream in = new FileInputStream(new File("crx-quickstart/logs/stdout.log"));Here is an example component you could use to display...

In order to check how long the the AEM author/publish instance has been up and running, you could use the stdout.txt log file that is located in your crx-quickstart folder under logs.This log file records what time your instance of AEM started and what time it shuts down, and is refreshed every time...