Hi @nirajd,I've actually also noticed this problem. Any overlay of
anything under wcm/foundation/components/basicpage/v1/basicpage or
override of the basicpage component causes the editor to break. I
suspect it's not just us, because if you look at the way the AEM Core
Component Page is built, they've used granite:include nodes in the
cq:dialog to get around this issue while customizing the page
properties:
https://github.com/adobe/aem-core-wcm-components/blob/master/content/src/content/jcr_root...
Hello @airnavin30,You can re-use parts of your edit dialogs by using a
Granite include node:
https://helpx.adobe.com/experience-manager/6-5/sites/developing/using/reference-materials/granite-ui/api/jcr_root/libs/granite/ui/components/coral/foundation/include/index.html
For example, by using adding the following node to a cq:dialog, you can
re-use the configuration form the Core Components Text
cq:dialog:
This is the result :
Hi @rk39193348,A while back I wrote a 4 part tutorial on how to set this
up using Docker images:
https://medium.com/@theopendle/github-jenkins-sonarqube-integration-for-java-maven-1-4-installation-ab4bdb53fcdd
The tutorial will teach you step-by-step but I also uploaded the source
code to GitHub: https://github.com/theopendle/docker-ci The end result
is the following architecture (you will obviously need to adapt it to
fit your environnement/network. This is what I used for my home
developments)...
Hi @Heena06,The issue is that the URL you are trying to visit does not
have the an extension (eg: .html or .json).What do you mean by "the
navigation option provided"?
Hi @srinivas_chann1,This forum is aimed at answering AEM-specific
questions. This is generic CSS question which would probably be better
asked on Stack Overflow.Here is a thread that answers your question and
uses the CSS skew() function to give you the exact 45° corner you're
looking for:
https://stackoverflow.com/questions/7324722/cut-corners-using-css/33122202#33122202
Hi @ashishkhadpe,Is your problem the following?If this is the case then
here is the answer 🙂The reason for your problem is that providing a
custom valueFormat, you are violating the JCR's definition of a date,
which you can see here in the spec:
https://docs.adobe.com/docs/en/spec/jcr/1.0/6.2.5.1_Date.html As you can
see, a JCR date must follow a certain format, which is not the case for
your property. Instead, you should save your date as a String by adding
typeHint="String"The type hint (docu...
Hi @JonMaguire,In your previous question the answer was to use
${item.properties.subtitle} because in that case, the item in question
was a Page object.In the case of the Navigation component, the item is
not a Page object but a NavigationItem object (you can see this by
checking out the getItems() method of the Navigation interface) which
does not have a getProperties() method, so ${item.properties.subtitle}
will not work 😕 In HTL, the dot accessor is actually shorthand for
using a Java getter...
Hi @Aryan12345,Could the issue be caused by the way you fetch your
artifacts? What version of core components were you using before? Since
v2.7.0, the core components artifacts are no longer available on the
Adobe Public repo, as you can see here:
https://repo.adobe.com/nexus/content/groups/public/com/adobe/cq/core.wcm.components.core/However,
based on your error message, it seems like you are still trying to use
the public Adobe repo. Instead, you should be fetching them from Maven
Central. You...
Hi @arvind,This is normal for a typical AEM Author instance
installation. The reason is that the WCMMODE is EDIT by default on
Author instances, which is mentioned in the documentation here:
https://helpx.adobe.com/experience-manager/6-3/sites/developing/using/reference-materials/javadoc/com/day/cq/wcm/api/WCMMode.html#EDITIn
order to simulate a Publisher instance, you must add ?wcmmode=disabled
to the URL, regardless of whether /editor.html is present in the URL or
not (this is what the View as...
Hi @psrpjayaem,As @Arun_Patidar mentioned, there is no easy way to do
this in HTL and it will always be more verbose and less performance (due
to lots of iterating) to perform this kind of complex logic than if you
used a Sling model.In my opinion, you really should be using a model for
this kind of requirement, for a number or reasons:You can unit test this
logic if it's in a model, but not if it's in HTLIf you wish to re-use
the logic elsewhere, then ou can do so using Java but not using HTLYo...
Hi @arvindk091986,Migrating from AEM 6.2 in Classic UI to AEM 6.5 in
Touch UI is going to be a BIG project. I'm speaking from experience as a
project I'm working on from AEM 6.3 in Touch UI to AEM 6.5 in Touch UI
is going to take roughly 300 man days.You would have to share the whole
stacktrace with us so we could help you identify the source of the error
but if you've already narrowed it down to annotation then you probably
have an incompatibility between WCM Use API and Apache Felix annotation...
Hi @johns56194565,If you're looking for a way to add/change the Type
drop-down, have a look at my tutorial on the subject:
https://levelup.gitconnected.com/aem-populate-a-drop-down-with-a-data-source-edafada90cc4
Hi @zeevd,As @Shashi_Mulugu suggested, this clientlib is meant for
authoring purposes and if authors are accessing AEM via Dispatcher then
your Dispatcher should allow all paths (or you will have many other
problems too).However, if you wish to expose a clientlib under /libs in
a Publisher witha Dispatcher that prevents access to /libs, then the
clientlib must have allowProxy="{Boolean}true" set on it. This will
cause AEM to fetch it under /etc.clientlibs rather than /libs 🙂
Hi all,I recently began writing Groovy scripts and decided to make this
quick-tip tutorial on how to speed up your Groovy developments using
IntelliJ!Have a read:
https://levelup.gitconnected.com/aem-quick-tip-write-your-groovy-scripts-in-intellij-716f4aa3c6ba
🙂
Hi,I'm still a bit confused by some of the explanations but not, you
cannot use the Style system to add attributes 😕To make the author
experience as friendly as possible though I would suggest using an
Autocomplete Tags widget in the edit dialog to select the attributes:
https://helpx.adobe.com/experience-manager/6-4/sites/developing/using/reference-materials/granite-ui/api/jcr_root/libs/granite/ui/components/coral/foundation/form/autocomplete/tags/index.html.
You can then use a cq:template nod...
Hello @Unnikrishnankv, I don't believe there is, but even if there were,
I don't think it would be the best way to proceed.If you want to do
advanced pre-processing then I think your best bet is to do so during a
build process, by creating a front-end project as is commonly done when
using the later version of the AEM Maven Archetype. Here are some
advantages:This is the direction that the AEM community is going, so
you're more likely to be in line with best practicesThe documentation
around npm...
Hi @diegoeflz4887,Here are a couple of pointers:What does your browser
console say? It sounds like you may have a JS error that is preventing
certain UI elements from loading correctly. Have you overlayed anything
under /libs/wcm/foundation/components/basicpage?
Hi @nitin_harikant1,IE 11 isn't actually supported by AEM 6.5.You can
see the the browser compatibility matrix here:
https://docs.adobe.com/content/help/en/experience-manager-65/deploying/introduction/technical-requirements.htmlHere
is the line in question:
Hi @marcjuberoWhat version of AEM are you on?I wasn't able to test your
validator because on my 6.5.5 instance, your desired behavior is
actually implemented OOTB: Perhaps it's time to think about an upgrade?
😉
Hi @marjorielazaro,I'm not sure I've understood exactly what you're
looking for... but if you mean "How can I easily pass a number of
attributes to a web-component element in HTL" then the asnwer is to use
a Map and the data-sly-attribute expression.Here is an
example:Interface:public interface DemoModel { Map
getAttributes(); }Model:@Model( adaptables = Resource.class, adapters =
DemoModel.class, resourceType = "demo/components/content/demo" ) public
class DemoModelImpl implements DemoModel { @...
Hi @aaykay22,The ACS Commons installation page you linked to contains
the two steps you you need:Fetch the acs-aem-commons-content artifact
via a maven dependencyEmbed that artifact into a package which you will
then deployThe documentation mentions "your content project’s pom.xml"
but this is just a recommendation, there is no technical reason why this
won't work in ui.apps, so you can just follow the documentation as-is
and simply apply it to your ui.apps project 🙂Disclaimer: if you have
mult...
Hi @gvaem,It's important that each time you install an AEM upgrade (CFP
or SP), to check that your customizations are still valid.If you have
changed /libs/sling/xss/config.xml to /apps/sling/xss/config.xml a few
versions ago, then in the meantime the original file under /libs may
have changed while your customized version under /apps did not. It may
be completely out of date! Here's what you should do: Identify the
changes that were made in the /apps/sling/xss/config.xml fileRemove
/apps/sling/...
Hi @ajinkayk6258253,There are 2 likely reasons why this might be:The
responsivegrid is locked.You can unlock it using the lock/unlock button
like so:There are no allowed component. Make sure that the
responsivegrid has a policy which allows a set of components to be
placed inside. The responsivegrid should look like this in Structure
mode: Not like this:
Sorry I don't have a 6.4.8.1 instance ready-to-go. In order to help, I
will need the entire HTL file for your component, not just this one line
(unless this one line IS the whole HTL?)
Hi @samikshaa223429,@Arun_Patidar beat me to the punch 😉 But his answer
is correct! One thing to know is that the value is cq:template are set
when a component is created. That means if you placed your component on
the page, then modified the cq:template values, you would have to remove
and add the component again to see the changes, maybe that is your
problem? 🙂Other things to look out for:The cq:template child must have
the same name as the name of the resource in your data-sly-resource
attr...
Hi @bsr78033597,I'm not sure what your refereing to. What HTTP request
are you using which features binary-to-text encoding?As a general rule,
the payload of a response for a GET on an asset is Gzipped.
HI @cnur24357457,There is no OOTB method of publishing only certain
parts of a page. However, your use case seems to fit well with Fragments
(either Content Fragments or Experience Fragments).A fragment is a piece
of content which can be re-used in any number of pages. It can also be
edited and publish independently from a page so it could be used to
satisfy your use-case.There are excellent documentations for Content
Fragments here:
https://docs.adobe.com/content/help/en/experience-manager-64/a...
