The same piece of code has been deployed to another instance (6.3), where parsys works fine. 2 newly created instances within the same packages are having parsys issues (6.3 and 6.5 instances). So is it some configuration issue or some api/file import issue?
I added the line: <cq:include path="par" resourceType="foundation/components/parsys"/> to my jsp page, but the parsys is still not seen in the page. I am not sure what might be the issue.
I have added a checkbox to my dialog. First time clicking on the button to open the dialog, i can see the checkbox, but on next click on the button to open the dialog, i cant see the checkbox. though i can see the field description and field label 3/4 times, one after the other.When I remove the ID ...
I need to write servlet code which can run in AEM 6.1 as well as in 6.3. But, as we use Felix in 6.1 and SCR in 6.3 how to write a common piece of code that works for both?
i made a connection to repository using JCRUtils and got session. Next, I need the resource but, when I am trying to fetch resource using resourceResolver, I am getting null. Whereas, if I use session.getNode, i am getting the node (not null). I also tried to use AdaptManager to convert the node to ...
I have checked, it's not there.Infact, the problem is really peculiar. At times when I download a package, I get zipped file, which I can upload. But, at other times when I download, I get unzipped file, which on compressing doesn't gets uploaded!
I use Mac.When I get the downloaded folder I created a zip using the jcr_root and meta_inf folders, only that zip get uploaded successfully. But if I try to zip the folder itself, which contains the jcr_root and meta_inf, that doesn't get uploaded.