This requires tightly coupling the Sightly code to the keys available in
the json object. Is there any way to do this generically? I just need to
dump out the entire json object within a script tag in the mark-up,
without hard-coding the keys in the Sightly code.
I looked into @ValueMapValue and @Via but did not see anything that
would automatically "walk" the JCR back to the template. As a
work-around I hard-coded a JCR path as in smacdonald2008's suggestion,
but would like to refactor this for better maintainability/re-use.
I have a simple sling model, the important part looks like this:This
works fine if I use HTL's in a component to access
resources under the page where the component is used.However, if my
component is used in the structure of an editable template, this breaks
since the resources I want are in the template node, not the page
node.Is there a way to access the template resource node instead?
Per Adobe Daycare "RTE on Page Creation is not and OOTB AEM feature and
not supported OOTB" and so jainpraveen12's answer is the correct one,
although it is only a partial fix (the toolbar still won't display).
ThanksJulio Tobar for pin-pointing the root cause of the issue. I
relayed your explanation to the Sling IDE Tools project and they
immediately pushed a fix (upgrade File Vault to 3.1.42) to the
1.2.1-SNAPSHOT version of the plugin as of this morning.
My clientlibs are getting corrupted, replaced by
"./bad_files/clientlib-base.css"I am seeing this strange warning in my
error.log:This happens in a component that uses data-sly-resource to
re-use content from another page.What could be causing this? I searched
everywhere and I have no "position" style attribute anywhere!