この会話は、活動がないためロックされています。新しい投稿を作成してください。
この会話は、活動がないためロックされています。新しい投稿を作成してください。
Along the top of Touch UI dialogs are a series of buttons. I need to configure the help button (leftmost) so it points to the documentation for the component. I see that helpPath is the property name I should use according to this example from Adobe. But it's not working, and instead always points to https://www.adobe.com/go/aem6_1_docs which is not what we need.
I've tried both helpPath (works in Classic UI) and helppath, but it is not working in the Touch UI. Any advice would be appreciated. Thanks!
{ jcr:primaryType: "nt:unstructured", helpPath: "/content/blah/en/aem-support/events.html", helppath: "/content/blah/en/aem-support/events.html", sling:resourceType: "cq/gui/components/authoring/dialog", content: { jcr:primaryType: "nt:unstructured", sling:resourceType: "granite/ui/components/foundation/container", layout: { jcr:primaryType: "nt:unstructured", type: "nav", sling:resourceType: "granite/ui/components/foundation/layouts/tabs" }, items: { jcr:primaryType: "nt:unstructured" } } }
looking at the code it seems pretty well hard-coded...
private AttrBuilder getHelpAttrs(SlingHttpServletRequest req, Config cfg, XSSAPI xssAPI, I18n i18n) {
String url = i18n.getVar("https://www.adobe.com/go/aem6_1_docs");
AttrBuilder attrs = new AttrBuilder(req, xssAPI);
attrs.add("type", "button");
attrs.addClass("coral-MinimalButton cq-dialog-header-action cq-dialog-help");
attrs.addHref("data-href", url);
attrs.add("title", i18n.get("Help"));
return attrs;
}
解決済! 解決策の投稿を見る。
表示
返信
いいね!の合計
This looks like a bug to me. Please raise a daycare ticket here to fix it at the platform level
https://helpx.adobe.com/marketing-cloud/contact-support.html
表示
返信
いいね!の合計
This looks like a bug to me. Please raise a daycare ticket here to fix it at the platform level
https://helpx.adobe.com/marketing-cloud/contact-support.html
表示
返信
いいね!の合計
Hi,
Not sure if this is the correct solution, but I see the key is available in the i18 translator.
Let me know if this works. Contact support as well.
Thanks
表示
返信
いいね!の合計
That may not be the right solution as it will be generic to all the component and not specific to one component.
表示
返信
いいね!の合計
does this issue got resolved?
表示
返信
いいね!の合計