Thanks for the explanation, it is helpful. I did notice that the default
max size of 3840 can be increased in the Web Console, so I increased it
to 7000 just to test. I'm not sure almost doubling this value is the
best way to go about this, but it did resolve the issue.
When our authors use the cropping option in the Image Component, the
image "disappears" like this.This seems to happen with larger images.
For example, the original image size I'm testing is 6582x4388.We are
using AEM 6.5 and components version 2.13.0.I haven't found any useful
info in the logs, but I'm not sure what I'm looking for.I'm wondering if
this has happened to others and how you may have resolved it?
This question relates to an earlier post I made
here:https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/get-subtitle-page-property-with-htl/qaq-p/378345I’m
trying to extend the Navigation Core Component and add the subtitle and
description page properties at the group level. This is my test code so
far in the group.html of the component:
${item.properties.subtitle} ${item.description}
While the solution in my previous post worked in my local HTL
REPL page, and I can curr...
I don't know why this was marked as accepted. @ChitraMadan's answer
below should be the accepted solution. ${item.subtitle} does not work.
${item.properties.subtitle} does work.
I'm wanting to retrieve the page subtitle and description using HTL.
Using the AEM HTL Read–Eval–Print Loop environment to test, I'm able to
get the description using ${item.description} but cannot get subtitle
using the same format, ${item.subtitle}. Is there a different way to get
the subtitle property?
Thanks, but my app is not React. I understand being able to add
clientlibs as dependencies to templates. My team wants to be able to see
the generated css in a human-readable format. For instance site.css
within clientlib-site.
Thanks, that sort of makes sense on how it works, it being generated in
the build, I'm just not sure of the reasoning behind it. For a follow-up
question, do you happen to know if there is a way to turn off the
minification of the css and js files generated through the ui.frontend
process? This makes debugging through CRX easier in integration and QA
author environments. I assume we would have to modify the
webpack.prod.js or maybe another file to accomplish this?
When using the ui.frontend project, why are clientlib-dependencies and
clientlib-sites ignored in Git. Don't these folders and the code within
them need to be part of version control?
That is where the tutorial project installed node for the ui.frontend
part. It is my understanding it installs a separate node version for
this? My machine is running node v12.9.1.
I've been trying to set up the AEM WKND Tutorial. When I run mvn
-PautoInstallSinglePackage clean install I get the following
error:[ERROR] Failed to execute goal
com.github.eirslett:frontend-maven-plugin:1.7.6:npm (npm install) on
project aem-guides-wknd.ui.frontend: Failed to run task: 'npm install'
failed. java.io.IOException: Cannot run program
"C:\Users\conta\git-repos\aem-guides-wknd\ui.frontend\node\node.exe" (in
directory "C:\Users\conta\git-repos\aem-guides-wknd\ui.frontend"):
CreatePro...
I'm creating an experience for new visitors to a page,. Does Target
consider someone a new visitor per page or does Target only consider
someone a new visitor per site/domain? For example, I created an
audience with these two rules: Site Pages Current Page URL contains
https://www.somedomain.com/page AND Visitor Profile equals New Visitor.
If I have a Target experience elsewhere on the site that a visitor has
seen previously and then comes to this page later, should they still see
the New Visito...
Thanks for the response. That was my assumption.We are on AEM
6.2.Looking at the documentation for the Core Image component, it still
seems to use a URL with just the width attribute and therefore would not
take height into account. It would just scale at the different
breakpoints? Or am I misunderstanding?If we want cropping instead of
resizing at each breakpoint, should that be done with rendtions? If so,
is there an out of the box way to crop renditions as part of the upload
workflow instead ...
We have an image heavy site we are wanting to optimize. I've read
through this
page:https://docs.adobe.com/docs/en/aem/6-2/develop/mobile-web/responsive.html.
My designers like the Image Reference Modification Servlet because it
crops the images instead of resizing. The Geometrixx example targets the
page property image, but can this be used for all images? Or would that
be too much and cause the site to be slower?
Is there an OOTB way in AEM 6.2 to crop image renditions on upload
similar to how Wordpress handles renditions? Currently the workflow is
just resizing the image.
The path is isolated. We have a check in our workflow to run different
rendition sizes if uploaded to this path. I tried adding the activate
step to the workflow instead of the script before, but ended up running
into the same issue.
We have a batch script that is used by one of our business partners to
copy newly created or updated photos from a legacy directory to our AEM
6.0 DAM and activate them. The script uses cURL, (e.g, curl -X POST -F
path="/path/to/our/ photos/color-jpg/%3.jpg" -F cmd="activate"
http://%logon%@%server%/bin/replicate.json). An issue we are running
into is the activate is taking place before all renditions are created,
so the data on the publish server is incomplete. Is there another way to
prevent s...
