Skip to main content
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
smacdonald2008
smacdonald2008Accepted solution
Level 10
Mar 20, 2018 3:24 PM UTC

Using a personal AEM DEV instance is the best way to code with AEM. Make sure you solution is sound before pushing to a staging server.

Anyhow - i recommend setup a fresh instance and repeat your steps. Lets see if you can reproduce in order to pinpoint where the issue is. I still think its related to that bundle.

14 replies

Ratna_Kumar
Level 10
Mar 20, 2018 2:47 PM UTC

Hi,

I just tested in 6.2. It works fine for me and not able to reproduce this issue. In past also, I tested this many times.

Below is the screenshot.

I suggest you to test the package once in fresh AEM 6.2 instance.

Thanks,

Ratna Kumar.

Translate
smacdonald2008
Level 10
Mar 20, 2018 3:05 PM UTC

You tested on a personal DEV AEM instance right?

Translate
jamesm77050123
Level 2
Mar 20, 2018 3:15 PM UTC

Yes I did

Translate
smacdonald2008
smacdonald2008Accepted solution
Level 10
Mar 20, 2018 3:24 PM UTC

Using a personal AEM DEV instance is the best way to code with AEM. Make sure you solution is sound before pushing to a staging server.

Anyhow - i recommend setup a fresh instance and repeat your steps. Lets see if you can reproduce in order to pinpoint where the issue is. I still think its related to that bundle.

Translate