Hi @rahulb31017943 I have just noticed that you want to read a property
located at /etc/abx/xyz/* and the corresponding dispatcher rule is /0151
{ /type "allow" /url "/etc/xyz/*" } which doesn't seem to be right to
allow /etc/abx/xyz/*. Could you please try updating your rule like
below:/0151 { /type "allow" /url "/etc/abx/xyz/*" } Regards,Arpit
Hi @Kam-nyc Please download it from here
https://github.com/adobe/aem-core-wcm-components/releases/tag/core.wcm.components.reactor-2.5.0
and install it in your AEM instance. Regards,Arpit varshney
Hi @saurabh_intel Why don't you create a common client-lib which include
common files and create two clientlibs embedding the common clientlibs?
Regards,Arpit Varshney
Hi @Kam-nyc The link you are referring is using core component release
2.5.0 as a reference. Could you please verify if it is the same version
in your instance as well? Regards,Arpit Varshney
Hi @danilo-delfio There might be many reasons for this behavior. Some of
them might be:AEM instance is not up and running.AEM instance might be
running on different port than the one configured in your pom.xml file.
In that case, you can change your pom port parameter or run aem on the
same port mentioned in your file or use a different profile where you
can pass the port.check the credentials configured in your pom file is
the valid credentials of your running aem instance. Regards,Arpit
Varshn...
Hi @ajin0093 This is an upgrade project which needs proper planning and
approach to make a decision. It is not recommended to replicate content
from a lower AEM version to a higher AEM version. Start from here to get
an understanding of the AEM upgrade. You will understand the few
additional steps which you might need to do as per Adobe recommendation
like repo
restructuring.https://docs.adobe.com/content/help/en/experience-manager-65/deploying/upgrading/upgrade.html
Coming back to your question...
Hi @v1101 It seems you are mixing JSP and HTL syntaxes. If your script
file contains extension as .html then follow HTL documentation else
follow JSP. It looks like your script file is JSP as most of your shared
code follows JSP syntaxes and JSP doesn't support sly and data-sly-test.
It is HTL syntax of testing an expression. Please go through the link to
get the corresponding syntax
https://stackoverflow.com/questions/28409916/how-to-check-null-from-jcr-value-in-adobe-cq5
Regards.Arpit Varshney
I will still recommend you to wait for next time and see the CPU usage.
Apart from that try checking if you can find any error in browser
console when you click upload button. Also try to test this
functionality on different browsers during that time.
I understood it now, What is fieldDescription property? Is it a dialog
property where you want to give hyperlink in the text?If yes, are you
using classic or touch dialog?
Hi @airnavin30You can implement the rich text editor (rte) inside a
dialog for this requirement. Go through below
blogshttp://experience-aem.blogspot.com/2019/05/aem-65-touchui-composite-multifield-with-coral3-rte-rich-text.htmlhttps://www.albinsblog.com/2019/01/create-touch-ui-multifield-dialogs-with-rte-granite-coral3-aem.html#.XxZ57HUzZxg
Also, You might think of giving the HTML itself in the text field and
read in HTL using @context='html' but this is not recommended at all.
I've seen many p...
Hi @Magicr It is not a version-specific issue. It is specific to your
publish environment. Could you please check if you are replicating the
package then is it not blocked in the replication queue? Also, verify
whether this publish is stable before you install the package Verify
http://localhost:4502system/console/bundles if all bundles are active or
not and revert your recent changes(any content package or code changes)
if any which are not present in another environment to confirm your
issue. ...
Hi @fionas76543059 What do you mean by the file picker menu doesn't
allow me to select a local file to upload - Is the system hanged during
that time? If yes, could you please verify the CPU usage during the
issue. It might be due to high CPU usage on your system. Regards,Arpit
Varshney
Hi @Magicr I'm not clear with the issue. Can you please confirm: You
mentioned the issue in one test system. Is it working with the other 5.6
systems?Is it happening only in publish instance or both author and
publish?Please share the relevant logs during that timeframe after
changing the level as trace. Regards,Arpit Varshney
Hi @Mayankg1 @Nupur_Jain has covered everything but you can have a look
to this blog :http://www.aemcq5tutorials.com/tutorials/aem-cq5-tutorial/
to get a better understanding. This is an old blogpost but the order of
learning is still valid. Regards,Arpit Varshney
Hi @nayeemnshaikh In order to customize or extend the AEM OOB
functionality, one needs to overlay in AEM.In AEM 6.4 version, I have
found that the black background header is generated from the location
/libs/granite/ui/content/shell/header/actions and noticed that it's
marked as granite:internalArea as mixin type. Following Adobe
documentation it says that "Internal (granite:InternalArea) - Defines a
node as internal. Nodes classified as internal cannot be overlaid,
inherited, or used directly. ...
Hi @v1101 If other AEM 6.4 instance with same service pack is working
fine, then something is wrong in your current instance. It can't be AEM
version specific issue.There might be additional code/content or package
in your instance which is creating issue. You need to debug this by
checking error logs, removing additional packages or reverting
additional code which is not present in other instance. Regards,Arpit
Varshney
Hi @aem-explorer Please go through the blog
https://helpx.adobe.com/in/experience-manager/6-3/sites/developing/using/extending-msm.html
to get better understanding of creating custom rollout config, You can
try creating custom rollout config as suggested by @Arun_Patidar and add
targetActivate as sync action which should activate the rollout pages.
Otherwise you need to achieve your requirement by developing a
LiveActionFactory and use it in a rollout configuration.The example is
mentioned in th...
Hi @v1101 If it is working in AEM 6.5 and not in 6.4 then can you just
give a try updating your AEM 6.4 instance to latest service pack and
validate if it is still appearing for you? Regards,Arpit Varshney
Hi @v1101 Could you please validate if any of your project client-lib
has dependency property pointing to AEM jquery clientlibs like cq.jquery
or cq.jquery.ui which might call these clientlibs in publish?For
debugging in LOCAL, You can just remove your project specific clientlib
category from code and validate it if it is still appearing. If not
appearing then probably your project specific clientlib is calling them
in publish. Regards,Arpit Varshney
Hi @Sachindey11 If you are working on your local machine and have
created a sling servlet to make post request to local AEM Server , you
may be getting 403 Error Code : ForbiddenThis issue is due to CSRF
Filter blocking POST Requests.You can unblock this via OSGi
Configuration. You shouldn't be doing it on production instances.Go to
http://localhost:4502/system/console/configMgrFind Adobe Granite CSRF
Filter Remove POST from Filter MethodsSave and Test the servlet again.
Reference:
http://letusa...
Hi @AdobeID24 Could you please remove delete permission of that
particular user/group for the particular DAM assets using aem useradmin
console, it will remove the delete option for that particular
user/group. Regards,Arpit Varshney
Hi @keshav_goud It seems to be a workflow launcher that has been
triggered after modification.But before assuming anything, please set
your log level as debug in your local and try to replicate the mentioned
scenario and validate the logs if you find anything useful.
Regards,Arpit
Hi @ektaa69139387 Agreed with @Vaibhavi , if it is user-generated large
content then it should be stored centrally and shared with the all the
publishers for performance perspective and SRP is the right approach for
this. Implementation: SRP Community Content StorageAEM6.1 introduces the
concept of Social Resource Providers(SRP)(it is now renamed and should
be called as Storage Resource Provider). With this, the UGC content is
no longer replicated across your publish instances. The UGC content i...
Hi @ruchim71073425 Could you please verify:If you have updated the
custom aem code to use aem 6.4.8 uber jar? You have to update pom uber
version like below: com.adobe.aem
uber-jar 6.4.8
provided Also, the mentioned package
com.adobe.aemds.guide.aemds-guide-core-impl is related to AEM forms
package which might be missing in your local instance. You need to
verify if the AEM version 6.4.8 support different version of the package
which might be located here
https://helpx.adobe.com/in/aem-forms/kb...
Hi @aem-enthusiast After adding maven dependency, please verify the
tag of maven-bundle-plugin [You can either include
all the dependencies or you can configure to not include specific ones].
The scope attribute lets you configure which dependency jars you want to
include based on their include scope. You should not include the
dependencies which are only needed for compile and for the test.Below is
the example to add the kafka-streams & kafka-clients to the embed
dependency in your core pom.xm...
Hi @imadullakhan Please go through this blog
https://blogs.perficient.com/2018/10/26/simple-multifield-max-item-validation-for-aem-6-4/It
will help you with your usecase. Regards,Arpit Varshney
Hi @vijayt86226372 I'm assuming this is probably because of different
client libraries for multiple websites. The best way I can think is that
you can extract the generic components which need to be used across all
the websites. Just create a base clientlib for those components and
embed this base clientlib in all the other site client libraries and
remove the duplicate code from site-specific clientlibs and then you can
use style system to define the variation of your component and author in
we...
Hi @ashutoshrastogi I would say you should drag/drop/edit the classic UI
component in classic UI mode and touch UI component in touch UI
mode.Also, Adobe has already recommended everyone to move from classic
to touch UI mode so I would suggest you move your components from
classic to touch gradually but at least you can convert these dialogs
from classic to touch which are pretty easy using dialog converter tool.
Regards,Arpit
Hi @chandeshj240320 As per their documentation, the system requirement
is (Reference
https://github.com/adobe/aem-core-wcm-components/blob/master/VERSIONS.md)Core
Components Historical System Requirements: Core 2.9.0 AEM 6.5.4.0+AEM
6.4.8.0+ Java 8, 11 They only mention supporting version 6.5.4.0+ for
AEM 6.5. So, I would recommend you upgrade your AEM instance to service
pack 6.5.4.0+ if you want to proceed with the latest core component and
want to avoid any unexpected issue. Regards,Arpit Var...
