CQ 5.6.1 On Reopening OOB Teaser component does not show values in Location, Campaign Path or Strategy. | Community
Skip to main content
October 16, 2015
Solved

CQ 5.6.1 On Reopening OOB Teaser component does not show values in Location, Campaign Path or Strategy.

  • October 16, 2015
  • 3 replies
  • 737 views

I was able to successfully create a touchpoint for my teaser using -http://dev.day.com/docs/en/cq/current/wcm/campaigns.html#Creating%20a%20Touchpoint%20for%20your%20Teaser. The problem I am having is that when i re-open this OOB teaser component on the authoring page it does not show any of the the three values that were set to make it work. My page has the campaign and the content and is displays correctly (everything still works) but it is a bad User experience for author's to not being able to see back the values that they have set on teaser component.
Am I missing something or is this a bug in cq 5.6.1?

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 dkhanna

Thanks for your reply.

I created a brand new instance for my authoring server and build and deployed the package from the old to new instance and I do not face the same issue now. It works as expected. I tried a lot to figure (looking at cq logs, js errors etc if any) out why it does not work on my previous instance but could not figure that out.

3 replies

dkhannaAuthorAccepted solution
October 16, 2015

Thanks for your reply.

I created a brand new instance for my authoring server and build and deployed the package from the old to new instance and I do not face the same issue now. It works as expected. I tried a lot to figure (looking at cq logs, js errors etc if any) out why it does not work on my previous instance but could not figure that out.

smacdonald2008
Level 10
October 16, 2015

I am glad that it is working for you. If i hear any known issues from the Eng team, i will post the issue here. 

Thank you! 

smacdonald2008
Level 10
October 16, 2015

I will contact the Engineering team an follow up on this thread.