Bug when naming anything some from of the word "advertisement"? | Community
Skip to main content
Level 3
October 16, 2015
Solved

Bug when naming anything some from of the word "advertisement"?

  • October 16, 2015
  • 5 replies
  • 1480 views

Ran into a strange issue last night and wanted to check if anyone else has seen this. If i name anything (component, node, jsp file, package) in the CQ environement with any form of the word "advertisement" (advert, advertise, advertisement, advertisements) it'll cause issues. If you try to expand the node in crxde lite it'll freeze, trying to build a package with that name will throw an unspecified error, and the jsp file just won't render. I thought it might just be our environment so i installed a clean CQ5.6 (build 20130129) but sure enough it still happens there.

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 brucelef

Any chance you're using Adblock Plus in your browser?

5 replies

brucelefAdobe EmployeeAccepted solution
Adobe Employee
October 16, 2015

Any chance you're using Adblock Plus in your browser?

smacdonald2008
Level 10
October 16, 2015

I will see if i can duplicate this issue. I will name a node under apps using that term and see what happens. 

smacdonald2008
Level 10
October 16, 2015

I have successfully built a CQ 5.6 app using this term:

[img]ad1.png[/img]

Here is the JSP displayed in a browser:

[img]ad2.png[/img]

So CQ supports this term. Your issue may be due to something else. See the troubleshooting docs as you may have old files somewhere conflicting:

https://dev.day.com/docs/en/cq/current/deploying/upgrading/tips-and-troubleshooting.html


 

jocampAuthor
Level 3
October 16, 2015

Yep, that was it. After smacdonald said it worked fine for him i was trying to think what would be different about our environments. We all have adblock installed in firefox, just tested IE and it works fine. Sorry, should have thought of that last night!

Adobe Employee
October 16, 2015

No worries, I ran into this issue myself.