Skip to main content
JoseBerciano
New Participant
July 5, 2016

Parsys overlapping

  • July 5, 2016
  • 5 replies
  • 3146 views

Hi,

So as the attached picture shows for some reason these parsys are overlapping in one of my pages.

[img]https://s31.postimg.org/bwi7k4pgr/Screen_Shot_2016_07_05_at_11_25_24.png[/img]

Funny thing is that when I stretch the browser window a bit, the parsys automatically arrange themselves in the right position. I tested in both Chrome and Firefox with identical result.

[img]https://s31.postimg.org/vc2obrgp7/Screen_Shot_2016_07_05_at_11_27_41.png[/img]

 

The Chrome console log only spits the following error:

granite.js:229 GET http://localhost:4502/x?_dc=1467714519983&_charset_=utf-8 404 (Not Found)

 

I am using AEM 6.1 with SP 1, Windows Server 2008 R2 SP1

 

Any help would be much appreciated.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

5 replies

kautuk_sahni
Employee
July 14, 2016

Hi

Can you please look at the answer posted and let us know if these worked for you or not.
If you have devised another way to resolve the issue, please post it in the community for communities benefit.


Thanks and Regards
Kautuk Sahni

Kautuk Sahni
Jitendra_S_Toma
New Participant
July 8, 2016

it general happens if you have applied float in CSS classes. check the css if any such instances are there.

Lokesh_Shivalingaiah
New Participant
July 7, 2016

Are these parsys belongs to same component or different component ??

As @Tuhin mentioned, check the CSS by inspecting those parsys.

JoseBerciano
New Participant
July 5, 2016

More info:

The line that fails in granite.js is this one:

return open.apply(this, arguments);

where 'arguments' is an array containing this:

["GET", "/libs/cq/security/userinfo.json?cq_ck=1467717437065", false, undefined, undefined]

I tried http://localhost:4502/libs/cq/security/userinfo.json and it returns ERR_EMPTY_RESPONSE

Hope it helps to figure out what would be causing this issue.

Tuhin_Ghosh
New Participant
July 5, 2016

Most probably this is happening because some of your application CSS might be overriding some of CQ's default CSS classes. Kindly debug in your chrome and see what is that class which is creating that problem.

Thanks

Tuhin