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
BedrockMission!

Learn More

View all

Sign in to view all badges

AEM 6.2 to 6.4 upgrade : Issue with iparsys

Avatar

Avatar
Validate 50
Level 6
cquser1
Level 6

Likes

75 likes

Total Posts

313 posts

Correct Reply

15 solutions
Top badges earned
Validate 50
Validate 25
Validate 10
Validate 1
Give Back 50
View profile

Avatar
Validate 50
Level 6
cquser1
Level 6

Likes

75 likes

Total Posts

313 posts

Correct Reply

15 solutions
Top badges earned
Validate 50
Validate 25
Validate 10
Validate 1
Give Back 50
View profile
cquser1
Level 6

25-10-2018

Hi All,

We have a template[not editable templates], wherein iparsys is included in the page component of the template in body.html.

<sly data-sly-resource="${'xyz' @ resourceType='wcm/foundation/components/iparsys'}"></sly>

In 6.4 environment, on creating a page out of this template it appears as seen in screenshots below. When an extra parsys comes up, in author mode it overlaps some other component, thereby hiding that component and creating issues.

In 6.2 environment, on creating a page out of this template the extra parsys doesnt come up.

Did some investigation from the UI perspective,as we were suspecting our component css conflicts with the 6.4 OOTB css. Tried multiple things, but no luck.

Whereever, iparsys is included [i.e, in header, footer] this issue is to be seen in 6.4.

Tried multiple things for quite some time, but no luck.

Any thoughts/pointers on this will be really helpful.

AEM64 screenshot1.png

AEM64 screenshot2.png

Replies

Avatar

Avatar
Validate 10
Level 3
ronnyfm
Level 3

Likes

22 likes

Total Posts

70 posts

Correct Reply

4 solutions
Top badges earned
Validate 10
Validate 1
Ignite 3
Ignite 1
Give Back 5
View profile

Avatar
Validate 10
Level 3
ronnyfm
Level 3

Likes

22 likes

Total Posts

70 posts

Correct Reply

4 solutions
Top badges earned
Validate 10
Validate 1
Ignite 3
Ignite 1
Give Back 5
View profile
ronnyfm
Level 3

08-11-2018

Hi, we are facing something similar, did this happen to you using either 6.4.0, 6.4.1 and 6.4.2? Does this happen also using Classic UI?

Avatar

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,408 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,408 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile
smacdonald2008
Level 10

08-11-2018

Ronny - why not make use of the features 6.4 exposes as opposed to doing things the "old way". Use of editable templates to give an AEM site similar look and feel (headers/footers, etc) is best practice.

Avatar

Avatar
Validate 10
Level 3
ronnyfm
Level 3

Likes

22 likes

Total Posts

70 posts

Correct Reply

4 solutions
Top badges earned
Validate 10
Validate 1
Ignite 3
Ignite 1
Give Back 5
View profile

Avatar
Validate 10
Level 3
ronnyfm
Level 3

Likes

22 likes

Total Posts

70 posts

Correct Reply

4 solutions
Top badges earned
Validate 10
Validate 1
Ignite 3
Ignite 1
Give Back 5
View profile
ronnyfm
Level 3

08-11-2018

Sure Scott, but the first phase is the upgrade step, before then moving to the latest features.

I am aware that Classic UI is deprecated, but we need to ensure that we can perform the upgrade without affecting current site, or at least to know that by fixing a couple of configurations or lines of code will suffice to get the iparsys working fine.

Avatar

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,408 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,408 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile
smacdonald2008
Level 10

08-11-2018

If you deploy your 6.2 site to 6.4 - what is happening?

Avatar

Avatar
Validate 10
Level 3
ronnyfm
Level 3

Likes

22 likes

Total Posts

70 posts

Correct Reply

4 solutions
Top badges earned
Validate 10
Validate 1
Ignite 3
Ignite 1
Give Back 5
View profile

Avatar
Validate 10
Level 3
ronnyfm
Level 3

Likes

22 likes

Total Posts

70 posts

Correct Reply

4 solutions
Top badges earned
Validate 10
Validate 1
Ignite 3
Ignite 1
Give Back 5
View profile
ronnyfm
Level 3

12-11-2018

Reviewing, we are having CSS issues with some components, the dialog is in the DOM but with CSS rules that prevent it to be displayed:

element {      position: absolute;     z-index: 11000;     visibility: visible;     left: -10000px;     top: 20px;     width: 800px;  }

I am still researching why some of them have such rules applied.

Avatar

Avatar
Give Back 5
Level 4
praveenjain
Level 4

Likes

37 likes

Total Posts

36 posts

Correct Reply

10 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Ignite 1
Boost 5
View profile

Avatar
Give Back 5
Level 4
praveenjain
Level 4

Likes

37 likes

Total Posts

36 posts

Correct Reply

10 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Ignite 1
Boost 5
View profile
praveenjain
Level 4

02-10-2019

Can you check that in your custom code you have not overlayed any OOTB libs files ?

Similar issue was faced where below 2 files were overlayed, post merging both (latest libs file + custom code), parsys issue got resolved.

/libs/wcm/core/components/init/init.jsp

/libs/foundation/global.jsp

It should not be replicable in fresh AEM 6.4 instance, when we dont have any overlayed code.