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!
I just ran into the same exact issue from this posting:
data-sly-resource Not EditableAll the same except the solution from that
post doesn't work in AEM 6.3.My template's page is a single line:It "almost
works" except the referenced component is not editable.Adding
data-sly-unwrap makes no difference.How can I make the component
It was created automatically behind the scenes by AEM, probably the OOTB
workflow that runs after an image is uploaded through the DAM UI. It's
possible the node became corrupted as a result of this other issue: Re:
Eclipse "Import from Server..." function corrupts the JCR Is there a
quick way to re-run the image upload workflows or somehow
reset/overwrite these bad nodes?
jainpraveen12 the useFixedInlineToolbar=true was already in use, so
that's not the cause of this issue.Here's the dialog
smacdonald2008 It's for a description field which we need to reference
in other pages. Think of a page containing a really long article, and
then having a requirement to create a "top articles of the month" page
where you want to pull in just the titles and summaries of those
jainpraveen12, it is not possible to type anything into the single
line, it does not accept input focus. So #3 cannot be reproduced.Why
can't I make it behave the same in Page Properties as it does in a
One nuisance problem I've found while working with AEM in a
general-purpose IDE like Eclipse, is that the average project contains
hundreds of files all named ".content.xml".So the editor tab bar quickly
ends up looking something like this:It becomes very hard to quickly
switch between different components. Shortcuts like Ctrl-R become
useless since every file of interest is named the same.Are there any
Eclipse settings that can alleviate this problem?
Julio Tobar I see that I have filevault-3.1.38. I quick Google search
did not reveal where other versions can be downloaded. I did find an
alternate version "VaultClipse" at
which I will try next.smacdonald2008 the step to reproduce is to use
the Import from server... option below:
I have tried
got the same unexpected behaviour:it works fine when used in a component
dialogdoes not work when used in a Page Properties dialogWhen it works,
it looks like this:but when the same input is carried into a Page
Properties dialog, it looks like this:What could cause this, and what's
I have created a static template for some product pages. Simplified for
debugging it looks like this at page creation time:However when the
Product Description field is replaced by a richtext, the input collapses
to this:What could cause this?
kautuksahni I reproduced the problem using the package from this
article: Configuring Experience Manager Rich Text Editor Plugins in a
Touch UI Component Dialog My additional testing indicates this problem
only occurs in touchscreen laptops using a touchscreen API enabled
browser. My laptop has a touchscreen, and the RTE works fine if I use
IE11, which is the only browser I have that lacks the touchscreen API.
I get this error in Eclipse:The OakConstraint would seem perhaps to
indicate a violation of DAM Metadata Schema.So while investigating I
noticed PNG is not listed in
/etc/dam/metadataeditor/mimetypemappings.Does something need to be added
in order to remove the Oak constraint violation?
Executing the "Import from Server" function corrupts the JCR, by leaving
out attributes of jcr:content.Example showing /content/dam/myproject
before (right) and after import (left):What could cause this and what's
the solution?Eclipse version: Neon.3Sling IDE Plug-in: 1.2.0AEM: 6.3
with SP1, CFP2
hi dgordon86, we were experiencing this issue in our own project and
updating the dependencies fixed it. The project was created by a
colleague using the Maven aem-project-archetype version 12.Here's the
top-level pom.xml, the version which works fine: [XML]