When creating a new policy for a component, cq: styleID is not displayed in "CRXDE" even if the style system is set | Community
Skip to main content
October 19, 2020
Solved

When creating a new policy for a component, cq: styleID is not displayed in "CRXDE" even if the style system is set

  • October 19, 2020
  • 1 reply
  • 2783 views

Hello,

 

Problem
「cq: styleId」 is not applied when registering Policy for the first time.
need to re-register 「cq: styleLabel」 and 「cq: styleClasses」.

 

Component
「Text」「Image」

 

AEM

6.5.4(Service Pack 4)

Core Component 2.3.2

 

Steps to reproduce
1.Open 「Content Page Template」
http://localhost:4502/editor.html/conf/we-retail/settings/wcm/templates/content-page/structure.html
2. Click 「Text Component Policy」
3. Click「+」New Policy
4. Input the Policy Title「Test Policy」
5.Click Properties Styles tab
6. Add 「Allowed Styles」
7. Input the Group Name「Test Group」
8. Input the Style Name「Test Style」
9. Input the CSS Classes「test_classes」
10. Click done
11. Open CRXDE Lite and check the Location of the created policy
http://localhost:4502/crx/de/index.jsp#/conf/we-retail/settings/wcm/policies/weretail/components/content/text/policy_1603083082212/cq%3AstyleGroups/item0/cq%3Astyles/item0
12. Make sure there is no 「cq: style ID」
13. Open the policy setting just created again.
http://localhost:4502/editor.html/conf/we-retail/settings/wcm/templates/content-page/structure.html
14.Change the CSS Classes 「test_classes」to「test_classes2」
15. Click done
16.Open CRXDE Lite and check the Location of the created policy
http://localhost:4502/crx/de/index.jsp#/conf/we-retail/settings/wcm/policies/weretail/components/content/text/policy_1603083082212/cq%3AstyleGroups/item0/cq%3Astyles/item0
17. 「cq:styleID」is displayed

 

Thank you.

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 vanegi

Hi @石井浩之,

With above steps, I can reproduce the behavior in AEM 6.5.4 patch. Please submit a support case to investigate this further.

 

Thanks!!

1 reply

vanegi
Adobe Employee
vanegiAdobe EmployeeAccepted solution
Adobe Employee
October 19, 2020

Hi @石井浩之,

With above steps, I can reproduce the behavior in AEM 6.5.4 patch. Please submit a support case to investigate this further.

 

Thanks!!