Hi @subrato_kha,The image section on Teaser component will be rendered
from the proxy component defined with imageDelegate property on
component node. so, adding custom Sling Model for Teaser component using
Sling Delegate Pattern & passing static link from overridden method will
not work in this case because link on image will be referred from Sling
Model object "com.adobe.cq.wcm.core.components.models.Image" (i.e.
${image.link}) imageDelegate property on Teaser component:refer this :
https://g...
Hi @viki1101 You can directly access current page properties in Sling
Models as mentioned below. @ScriptVariableprivate ValueMap
pageProperties;pageProperties.get(JcrConstants.JCR_TITLE);
@jayv25585659 keeping all OSGI config xml under specific folder(ex:
"runmodes") is good practice from project structure & maintainability
perspective instead putting it under /project/
Hi @jayv25585659 If you want custom OSGI configs to picked up from
runmodes then precedence will be as mentioned below irrespective of
environments or author/publisher then put config xml under below
path./project/runmodes/config specific to environment
/project/runmodes/config.stage/project/runmodes/config.prod specific to
environment +
author/publisher/project/runmodes/config.stage.author/project/runmodes/config.stage.publish/project/runmodes/config.prod.author/project/runmodes/config.prod.pub...
Hi @sreedobe If its resource based servlet then you can access component
policy configuration by passing current resource to getPolicy(). in
below example component policy configuration has title field & same
configured value is retrieved using ContentPolicyManager.
ContentPolicyManager policyManager =
request.getResourceResolver().adaptTo(ContentPolicyManager.class);if
(policyManager != null) { ContentPolicy contentPolicy =
policyManager.getPolicy(request.getResource()); //ex:
request.getResour...
@adobecq-venkat this is not based on AEM version, if this runmodes
folder not present in your project structure then create these folders &
put config xml files under config/environment specific config folder.
refer this in crx/de/apps/weretail/config/apps/weretail/config.publish
@adobecq-venkat You need put these config xml files under project
runmodes folder structure. if these config property values varies from
environment to environment in your project then create environment
specific config folder as mentioned below.
/apps/project/runmodes/config/apps/project/runmodes/config.stage.publish/apps/project/runmodes/config.prod.publishSample
xml
file:com.day.commons.datasource.jdbcpool.JdbcPoolService-uniqueName.xml
Hope this helps!
Hi @adobecq-venkat ,You can add this JDBC config xml in runmodes with
the property values as you mentioned above & these runmode configs will
be deployed part of build.
Hi @srinivas_chann1 Can you please share sample code or screenshot with
detail, it will be helpful to understand your use case/problem which you
are facing. you can achieve this using single component, load both
desktop & mobile view in sightly. using css media query hide/show
desktop and mobile view based on viewport.@media (max-width: 958px) {
//write css style to hide/show using different class names on desktop &
mobile view html markup} you can identify mobile or desktop using
User-Agent val...
Hi @dips1 In AEM siteadmin OOTB we have option to sort pages based on
modified by in "List View". If you want to sort pages based on "Created
By" then try using "ACS Commons Page Report"
http://localhost:4502/var/acs-commons/reports/sample-page-report.html?wcmmode=disabled
1. Access
http://localhost:4502/editor.html/var/acs-commons/reports/sample-page-report.html,
add "ACS Commons Report Builder Text Column" component & define custom
column to be added in report like in this case "jcr:createdBy"...
@SebNamek You’re welcome 🙂I am not sure about your use case why you
need to have different field names under component A & B. Ideally
foundation include helps in reusability but in some cases like reusing
same dialog field more than once in same component dialog will result in
conflict in field names.
@SebNamek you mean adding different names to image fields under
component A & component B using foundation include. if yes, as per my
knowledge that option is not feasible to have dynamic property names.
foundation include accept only two properties as mentioned in below doc.
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
Hi @SebNamek ,Hope i understood your requirement, you can create
reusable dialog fields at one location & refer same fields from
component A, component B etc. using foundation include. Create reusable
field at common location (ex:
/apps/project-name/widgets/image-field/.content.xml) & add image field
in .content.xml
In
Component A reuse the image field using foundation include: In
Component B reuse the image field using foundation include:
Hope this helps!
Hi @cqsapientu69896 You can pass query map with properties as mentioned
below to QueryBuilder API, define paths which needs to be excluded in
group as highlighted below & then you can get hit.getExcerpt() from
QueryBuilder search result.
1_property=property-name1_property.value=property-valuepath=/content/mysite/engroup.1_group.p.not=truegroup.1_group.path=/content/mysite/en/testfolder1group.1_group.path.self=truegroup.2_group.p.not=truegroup.2_group.path=/content/mysite/en/testfolder2group.2_gr...
Hi @Anderson_Hamer You can achieve this with dialog listeners, please
refer below code for the same. Dialog field : Add listener js
code with clientlib category mentioned below :(function ($, $document) {
"use strict"; $(document).on("click", ".cq-dialog-submit", function (e)
{ var $concatTextInput = $('.concat-txt-input'); var $inputVal =
$concatTextInput.val(); if($inputVal.val()){ var prefix =
'/hardcodevalue/'; $concatTextInput.val(prefix+$inputVal); //before
submit concatenate input value ...
Hi @Rajalakshmi,If you want reuse component configured in one page in
another page, there are many ways to achieve this. below are some 1.
Convert component A configured on Page A to "Experience Fragment
Variation" & reuse that converted experience fragment variation on Page
B by configuring fragment variation path in Experience Fragment
component. Convert to Experience Fragment Variation Configure fragment
variation path in Experience Fragment component 2. Use iparsys, drag &
configure componen...
Hi @Kam-nyc ,In backed you can call third party API as mentioned below,
you can pass the response from API back to client side & use that
response data as per your requirement.
MultiThreadedHttpConnectionManager connectionManager = new
MultiThreadedHttpConnectionManager();
connectionManager.getParams().setConnectionTimeout(); //set this
valueconnectionManager.getParams().setSoTimeout(); //set this
valueconnectionManager.getParams().setMaxTotalConnections(); //set this
valueconnectionManager.getP...
Hi @BrianStager Using query parameter as mentioned below will open page
in preview mode.
http://localhost:4502/content/we-retail/us/en.html?wcmmode=preview refer
below
article:https://helpx.adobe.com/experience-manager/kb/LinkToPreviewMode.htmlhttps://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/issue-with-wcmmode-disabled/qaq-p/274124
Hope this helps!
Hi @manasip Hope below article will resolve the issue which you are
facing.
https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-forms/the-package-share-server-login-page-is-currently-not-accessible/qaq-p/368364
Hi @Pirateglen ,When author instance shows successfully published but
when same asset shows 404 when its accessed via dispatcher/publisher
then please check replication agent queue to make sure asset is
successfully pushed to publish instance or not? there are chances that
asset still in replication queue.
http://localhost:4502/etc/replication/agents.author/publish.html Hope
this helps!
@sreedobe Can you please add headercompoent.html screenshot & also is it
complete markup not generated on publisher or partial markup
generated(publisher screenshot which you have attached doesn't show
header section div). also did you you check logs on crxde console after
reloading the page? it will be difficult to analyze the issue which you
are facing just looking into screenshot so more details on the issue
will be helpful to understand the issue.
Hi @sreedobe,Can you please add screenshot of header component html &
html structure from browser page source where header is missing. also if
you access to crxde in higher environment try reloading the page & check
if there are any error printed on crxde console tab where logs will be
generated
Hi @viki1101 Try to add data attribute value within single quote as
mentioned below, then it will save value as expected. Test String Test
Page Access same data attribute values in front end: Hope this
helps!
Hi @hello-liana2 Have you deployed WKND project? if not please deploy
code by cloning the project from here
https://github.com/adobe/aem-guides-wkndIf yes, please check "WKND Sites
Project - Core" bundle status whether its in active status or not. if
its not active check if there is any dependency error. Hope this helps!
