Replies

Highlighted

Avatar

Avatar

ronnyfm

Avatar

ronnyfm

ronnyfm

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?

Highlighted

Avatar

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Answer

2.3K

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Answer

2.3K
smacdonald2008

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.

Highlighted

Avatar

Avatar

ronnyfm

Avatar

ronnyfm

ronnyfm

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.

Highlighted

Avatar

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Answer

2.3K

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Answer

2.3K
smacdonald2008

08-11-2018

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

Highlighted

Avatar

Avatar

ronnyfm

Avatar

ronnyfm

ronnyfm

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.

Highlighted

Avatar

Avatar

jainpraveen12

Avatar

jainpraveen12

jainpraveen12

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.