CQ 5.6.1 Calendar Component: Looks great in author, looks great in publish, completely broken in dispatch | Community
Skip to main content
S
StevenRTaylor
October 16, 2015
Solved

CQ 5.6.1 Calendar Component: Looks great in author, looks great in publish, completely broken in dispatch

  • October 16, 2015
  • 7 replies
  • 1112 views

I know that it is deprecated in 5.6.1 (we are soon moving to 6.0 and all of this will be for nothing) but I have an urgent need to get the out of the box calendar component working on our website.

As I said in the title of this post, it looks great in author and publish but in dispatch all that I can see is the gray title bar for the calendar without any title or month. I've been working on the assumption that it has to do with the client side libraries because when I look at the page in Chrome with the Developer's Tools open I can see about 38 GETs trying to get .css and .js files. 

Does anybody have any idea what I'm doing wrong? This is an urgent request and I've been beating my head against this for at least a day now.

Thanks.

Steven Taylor

Systems Integration and Web Services, Radford University

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Sham_HC
  • For calendar need to expose querybuilder..  to work through dispatcher. AEM in general relies on web application/server firewall to protect. In order to protect use referrer header-based solution which can either be achieved using mod_rewrite [1] or something more elaborate like mod_security [2] on the webserver tier.
  • Also you need to open up /home/users/.*.permission.json
  • With above two it should resolve your issue.  I would still recommend to file an case with daycare so that specialist can discuss with you the config from security perspective. And make sure from security point of view you are covered with additional protection it is required.
  • Also I would recommend while posting in public forums don't give your public site address and try to mask it. This is for your own benefit.

[1] http://www.webmasterworld.com/forum92/3229.htm
[2] http://modsecurity.org/

7 replies

Lokesh_Shivalingaiah
Lokesh_Shivalingaiah
Level 10
October 16, 2015

Just check if you have any rule set in your dispatcher to deny files from certain path where these css/js files resides

smacdonald2008
smacdonald2008
Level 10
October 16, 2015

When you say -- "but in dispatch" -- are you referring to the component in a dispatcher cached AEM page? 

S
StevenRTaylorAuthor
October 16, 2015

Yes, that is exactly what I mean. The errors that I get in the developer's tools console when I look at the component in our dispatcher (effectively what the rest of the world would see) are:

GET http://cq5-dispatch1-pprd.radford.edu/libs/cq/tagging/widgets/themes/default.css GraniteClientLibraryManager.includeScript @ clientlibrarymanager.js:252GraniteClientLibraryManager.write @ clientlibrarymanager.js:116(anonymous function) @ test.html:11 clientlibrarymanager.js:252

GET http://cq5-dispatch1-pprd.radford.edu/libs/cq/cloudserviceconfigs/widgets/themes/default.css GraniteClientLibraryManager.includeScript @ clientlibrarymanager.js:252GraniteClientLibraryManager.write @ clientlibrarymanager.js:116(anonymous function) @ test.html:11
clientlibrarymanager.js:252

GET http://cq5-dispatch1-pprd.radford.edu/libs/dam/components/scene7/widgets/themes/default.css GraniteClientLibraryManager.includeScript @ clientlibrarymanager.js:252GraniteClientLibraryManager.write @ clientlibrarymanager.js:116(anonymous function) @ test.html:11
clientlibrarymanager.js:252

GET http://cq5-dispatch1-pprd.radford.edu/libs/commerce/widgets/themes/default.css GraniteClientLibraryManager.includeScript @ clientlibrarymanager.js:252GraniteClientLibraryManager.write @ clientlibrarymanager.js:116(anonymous function) @ test.html:11
clientlibrarymanager.js:237

GET http://cq5-dispatch1-pprd.radford.edu/libs/cq/security/widgets.js GraniteClientLibraryManager.includeScript @ clientlibrarymanager.js:237GraniteClientLibraryManager.write @ clientlibrarymanager.js:116(anonymous function) @ test.html:11
clientlibrarymanager.js:237 

etc, etc.

As I understand it the libs directory is not normally cached on the dispatcher instance.

S
StevenRTaylorAuthor
October 16, 2015

I will look for the dispatcher's rules on this but the component seems to be looking in the wrong place for the .css and .js files. Am I barking up the wrong tree by thinking this is a clientlib issue? It seems to me that other components on other pages are probably finding the same library files (.css and .js files) but the component on this page needs to be configured to use the clientlib properly, something I've never had to worry about before. 

S
StevenRTaylorAuthor
October 16, 2015

So I've checked for any rules that would filter out any .css or .js files and there are none as far as I can tell. Does anybody have any advice on what I should investigate next? I would really appreciate the assistance.

Thanks.

Sham_HC
Sham_HCAccepted solution
Level 10
October 16, 2015
  • For calendar need to expose querybuilder..  to work through dispatcher. AEM in general relies on web application/server firewall to protect. In order to protect use referrer header-based solution which can either be achieved using mod_rewrite [1] or something more elaborate like mod_security [2] on the webserver tier.
  • Also you need to open up /home/users/.*.permission.json
  • With above two it should resolve your issue.  I would still recommend to file an case with daycare so that specialist can discuss with you the config from security perspective. And make sure from security point of view you are covered with additional protection it is required.
  • Also I would recommend while posting in public forums don't give your public site address and try to mask it. This is for your own benefit.

[1] http://www.webmasterworld.com/forum92/3229.htm
[2] http://modsecurity.org/

shannas78474797
shannas78474797
October 16, 2015

any updates on this issue?  i am facing the same thing. 

thanks

Terms & ConditionsAccessibility statement

Loading footer...