Hello Team,We are in the process of integrating Adobe Experience
Manager(AEM) and Adobe Target. I understand we have different ways of
achieving it (with Launch or without Launch). But I got some basic
questions on how to go about purchasing the License for Adobe Target. We
are one big global team operating in different regions with different
organization names and we have our adobe products’ licenses purchased
across different regions (EMEA and Americas).This is how our current
adobe products a...
we are also looking for something very similar here. In our use case,
the rules for web properties are usually created, updated by the
agencies we work with. We are looking for a notification feature, which
triggers an email to the admin or admin group that lets us review and
validate the changes. Isn't this a reasonable/common use case to
consider as an OOTB feature within Launch? If this is not an OOTB
feature, is there a suggested best practices around how to go about
customization of this fe...
Hello Team, I am new to AA's world. Trying to figure out some of the
basic reasons for traffic spikes for one of our Single page
applications. When debugged using adobe experience cloud debugger, we
noticed on our home page, that there were two image requests that are
being fired (two hits). Here are the details of those two image
requests. Image request 1: Yes, obviously, the page load rule that sends
a beacon (s.t() call) ---> we are setting few variables like page name,
referrer, load time.. ...
We are on 6.4 (service pack 2.0) and yes we are still facing this issue.
We are not facing this issue on our local instances. It is happening on
our QA and staging environments. Please let us know if anyone figured
out anything particular about this issue.
Hello All,We have been working on a requirement (AEM 6.4 - Touch UI)
where when an asset is uploaded, we will have to determine the aspect
ratio of it and if it's invalid then throw an alert which could prevent
the author from uploading the image OR Display a Coral-UI alert message
which shows up when the image is viewed(something like "Invalid aspect
ratio"). So, basically asset validation and error message display. We
could accomplish this particular requirement through overlays in our AEM
6.2...
the path you mentioned is correct. under Forms&Documents, you create
folders(based on your project details) and put all your forms over
there. Also, were you able to resolve the actual issue you were talking
about?
Did you take a chance looking into this one? Best Approach to upload
large Assets in AEM Also, What is the version of AEM you are using? If
it is 6.3, please take a moment to go through this helpx articles. There
are loads of performance improvements went into the 6.3 release. There
may not be a single shot suggested solution, but we could certainly
accomplish bulk upload using a combination of multiple approaches.Assets
Sizing Guide and AEM Assets
If possible, Please package component and content page and attach to
this post. I will try deploying it locally on my local AEM 6.2 instance
and determine what is going on.
I tried doing it on classic UI and it worked all fine. In Touch UI, the
approach must be different. I am not sure how it is done. Let us see if
other folks will be able to provide their insights.
Which version of AEM you are using? In general, both in Classic and
Touch UI whether or not targeting is enabled is basically defined at the
component level (In the context menu of a component). However, In Touch
UI, you could also manage targeting using Targeting Mode. But, In your
current implementation, if you are able to target a given component in
Parsys A but not in Parsys B, one possibility could be Parsys B is
customized and it could be have been disabled globally for Parsys B. For
insta...
I too validated on AEM 6.2 and it works perfectly fine. Not sure why it
is not working for you. Did you take a look the previous's reply by
mjb54261515 which talks about an OOTB page (trainage page in
geometrixx)? also please compare your custom component's dialog nodes
and properties with with the OOTB one which is present in
/libs/foundation/components/page/tab_basic/items/basic/items/tagslet us
know if you are still running into issues. Also, package your component
and upload it here. I will ...
For classic UI, check this out for complete details. How to set default
value for tag picker But are you specifically looking for a solution in
Touch UI?
I think we can achieve this using a mechanism called "Service Ranking".
By default, which ever implementation got a highest rank that
implementation class will be selected. Developer can control which
implementation needs to be selected by using OSGI property called
SERVICE_RANKING. refer to this article... i followed this one when i had
this question in my previous project.... cq5 - Multiple Interface
Implementations - AEM/CQ - OSGi - Stack Overflow For detailed
explanation you can refer to the...
please check this out Query for fetching assets with the same ordering
as used in DAM If you want to maintain the order, the suggested practice
is to use JCR API as opposed to query. It also betters the performance.
I am sure this is what you are looking it? Please refer to this
beautiful article which talks about the
same.http://www.aemcq5tutorials.com/tutorials/custom-osgi-configuration-aem/
Denny,I found something and I validated on my local instance(AEM 6.2).
Basically, when we enable a renderer for GET servlet, we see this
behavior. Surprisingly, I see a whole lot of live sites having this
issue and worst thing is these pages are getting indexed by google and
showing up in search results.Anyway, there is a OSGI configuration in
felix console which needs to be tweaked to fix this issue. Please follow
these steps1) Please go to felix console's configuration manager
http:///system/c...
Can you please confirm where the authoring of your component(footer
links) is happening?. The the component(with design_dialog) to show up
in all pages of a given template, the authoring should happen in Design
mode(not in page level). So, in your case, I hope you have accessed the
page 1, switched to design mode, configured all the footer links while
you are in design mode. This will create the relevant node structure in
/etc/designs// and now when you have
created page 2, the footer component ...
I guess it is the default behavior of sling. Meaning, when we do not
have a script or sling:resourceTtype associated with a node, this page
is displayed also this happens when we have an invalid
sling:resourceType. They are like the bad nodes or pages which can be
cleaned up. But in this case you are noticing the behavior on a
sling:folder type(not on a cq:Page or a component). Is this an upgraded
environment? and is this behavior seen only for given set of folders or
are you seeing it for other...
I would advice not to debug issues of this nature in PROD environment as
it may pose severe performance issues or may be an outage. So, please
validate if you could reproduce the issue on a lower environment (QA,
Dev servers) before you try in PROD.Regarding the solution for the
issues you have asked... For the #1 Here are the options thoughModify
the .js, .css files that is included in the library by adding a space -
A change here sometimes rebuild this particular client libraryOpen
js.txt or c...
Are you seeing this behavior when you are injecting the request object?
was it all working otherwise? one of the prerequisites is to make these
changes(add dependencies) to your pom.xml and also add the plugin
element.org.apache.felix.scrorg.apache.felix.scr.annotationsorg.apache.sling.models.apiplease
refer to this working example just to make sure you are not missing out
on any basic steps.Adobe Experience Manager Help | Creating Adobe
Experience Manager 6.3 Sling Model Components
Caused by: java.lang.NullPointerException: nullat
org.apache.jsp.apps.amica.components.content.left_002dnav.left_002dnav_jsp._jspService(le
ft_002dnav_jsp.java:191)Snippet of the stack trace clearly indicates
that it is a null pointer that is originating from the component script
because of which you may be seeing an error when you include this
component on to the page. You may have to take a look at the JSP and
figure out what is going on.
You will always be able to get the handle of SlingHttpServletRequest
object in your model(sling models) by injecting it. Here is the code
below.@InjectSlingHttpServletRequest request;And once you have the
request object, it should be straight forward to get the WCMMode.
WCMMode mode = WCMMode.fromRequest(request);Let me know if this helps.
Can you be more specific or elaborative please. Without much details, it
may not be easy to point out where the issue is. If possible provide
some screen shots which may allow us to comment/suggest on the solution.
ResourceResolverFactory is like any other service that is available in
OSGI framework. It's most frequent use is accessing resource resolver.
You can see its detailed use in your felix console,
/system/console/configMgr. Search for "Apache Sling Resource Resolver
Factory".Now, coming to your second part of the question...It depends on
where you need to get the handle of resourceResolver. In Servlet OR In
Java code(non servlet), In OSGI service or In WorkflowProcess class., In
JSP .. etc. The mos...
I think i figured out something (probably there could be more to it).
Basically, it is a new way to keep the permissions within the context of
the page which i feel is nicer way to handle instead of the traditional
classic UI user admin console where it often leads to confusion.A simple
use case to see it working1) Logged in as admin, create a custom user
and assign it to a custom group or the existing group(authors,
contributors)2) Pick up a page in geometrixx(hiking) and edit the
permissions b...
I agree. But there is a catch, jcr:created property gets updated for
every publish(regardless of the modifications to the page) where as
cq:lastModified property will be updated only when the page is modified.
A mere publish without modifying the page will not update
cq:lastModified but it does update jcr:created property. So, either of
those can be used for sorting the articles.
The publish environment does not have cq:lastReplicated property. The
equivalent property on a page that you would get to see on publish
instance is, jcr:created. This property gets updated every time a page
is published. So, technically jcr:created property's value in publish
instance and cq:lastReplicated value in author instance will almost
always identical. See if you can use either of these properties based on
your WCM mode(author/publish) to sort the values.
From my experience in my project, either admin OR user with admin rights
will be able to unlock the page. A mere impersonation of the person who
locked the page does not give you all the access to unlock the
page.Also, did you get a chance looking into some of the options that
were discussed in this thread. Unlocking Pages - Alternative to "admin"
Account?
