Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

dgordon86
Community profile dgordon86 Employee
Job title here
Location here
16 BADGES
Employee

Employee

Learn more
Joined the community 05-04-2012 7:08:13 AM
Offline
Top badges earned by dgordon86
Customize the badges you want to showcase on your profile
Re: content node ordering issue.
Avatar
Ignite 1
Employee
dgordon86
Employee

Likes

49 likes

Total Posts

73 posts

Correct Reply

26 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
dgordon86
- Adobe Experience Manager
I agree with Arun, the easiest work-around is to ensure that the parsys nodes are pre-created when a new page is created by adding the nodes as part of the page template or cq:template if they are included as a component.

Views

1.6K

Like

1

Replies

0
Re: Calling third party REST api call form clinet side on AEM (e.g. localhost:4052 )
Avatar
Ignite 1
Employee
dgordon86
Employee

Likes

49 likes

Total Posts

73 posts

Correct Reply

26 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
dgordon86
- Adobe Experience Manager
Hi @chgovind ,To make sure I am understanding the use case:During development, you are using a webpack dev server and any calls to your external service you are using the Proxy features of the webpack dev server and thus passing in a relative URL. However, when you create your production build and deploy to AEM the JS is still passing in relative URLs to your 3rd party API?You could look into using environment variables: Adding Custom Environment Variables · Create React App If you are in develo...

Views

3.4K

Likes

0

Replies

5
Re: Azure Application Insights Integration with my component
Avatar
Ignite 1
Employee
dgordon86
Employee

Likes

49 likes

Total Posts

73 posts

Correct Reply

26 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
dgordon86
- Adobe Experience Manager
Since you are using an external dependency (that is not available in AEM ootb) I believe you need to embed the dependency in your bundle: See Embedding Dependencies - Apache Felix - Apache Felix Maven Bundle Plugin (BND) on how to update your pom...

Views

10.5K

Like

1

Replies

1
Re: Where's the spa editor "Hello World" tutorial?
Avatar
Ignite 1
Employee
dgordon86
Employee

Likes

49 likes

Total Posts

73 posts

Correct Reply

26 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
dgordon86
- Adobe Experience Manager
Hi marcog1899 sorry for the delay, we pulled it because it was a little out of date. It has been re-published now: Getting Started with the AEM SPA Editor - Hello World Tutorial . As Scott mentions the Adobe Experience Manager Help | Getting Started with the AEM SPA Editor - WKND Tutorial is a fuller tutorial and probably the next step after getting your feet wet with the HelloWorld tutorial. In the HelloWorld tutorial there is a small Angular portion in case that is something you are interested...

Views

837

Likes

0

Replies

0
Re: [Tutorial] Getting Started with the AEM SPA Editor
Avatar
Ignite 1
Employee
dgordon86
Employee

Likes

49 likes

Total Posts

73 posts

Correct Reply

26 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
dgordon86
- Adobe Experience Manager
Hi jtran15 , do you have AEM 6.4 and ServicePack 2 installed?What happens when you navigate to http://localhost:4502/content/wknd-events/react.model.json ? Does the JSON render as expected?

Views

9.8K

Likes

0

Replies

1
Re: [Tutorial] Getting Started with the AEM SPA Editor
Avatar
Ignite 1
Employee
dgordon86
Employee

Likes

49 likes

Total Posts

73 posts

Correct Reply

26 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
dgordon86
- Adobe Experience Manager
Yes without the ServicePack, the components won't be able to be edited in AEM. Service Pack 2 is freely available to download and install: https://www.adobeaemcloud.com/content/marketplace/marketplaceProxy.html?packagePath=/content/companies/public/adobe/pack…

Views

9.8K

Likes

0

Replies

1
Re: Nesting AEM components and React Components
Avatar
Ignite 1
Employee
dgordon86
Employee

Likes

49 likes

Total Posts

73 posts

Correct Reply

26 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
dgordon86
- Adobe Experience Manager
Hi DriesVanbilloen,Very cool use case. I have not experimented with this but it might not be achievable with the Core Component Tab component. A few questions:Are you using the Tab Component from Core Components? aem-core-wcm-components/content/src/content/jcr_root/apps/core/wcm/components/tabs/v1/tabs at master · adobe/aem-core-wc… I haven't dug into the Tab component but at first glance, I'm not sure it will map properly to a React component since it doesn't seem that :type property is exposed...

Views

2.1K

Likes

0

Replies

2
Re: Cookie not passed to request of react.model.json
Avatar
Ignite 1
Employee
dgordon86
Employee

Likes

49 likes

Total Posts

73 posts

Correct Reply

26 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
dgordon86
- Adobe Experience Manager
Hi aquavento,Are you logged into AEM in the browser and navigating to: http://localhost:4502/content/we-retail-journal/react/home.html ?It shouldn't prompt you to authenticate the ajax request. Also what version of AEM and We.Retail journal app are you using?It is designed for AEM 6.4 + SP2. You can find the latest version of the We.Retail Journal here: GitHub - adobe/aem-sample-we-retail-journal: We.Retail Journal is a sample showcasing SPA Editing capabilities in AEM us…

Views

1.1K

Likes

0

Replies

0
Re: Migration project error
Avatar
Ignite 1
Employee
dgordon86
Employee

Likes

49 likes

Total Posts

73 posts

Correct Reply

26 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
dgordon86
- Adobe Experience Manager
Are you moving from the Classic UI to Touch UI in addition to moving from AEM 6.2 - 6.4? Do you see the Editor Drop zones?I'm curious if you see additional information in the error log or anything else in the browser console. The error you posted, unfortunately, is quite common and can be seen when selecting an empty drop zone even in We.Retail...Upgrading to AEM 6.4 and Upgrading Code and Customizations provide some good high level information on upgrading to AEM 6.4.

Views

2.1K

Likes

0

Replies

0
Re: Adobe AEM Angular 6 Support for Multi Functionality Component
Avatar
Ignite 1
Employee
dgordon86
Employee

Likes

49 likes

Total Posts

73 posts

Correct Reply

26 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
dgordon86
- Adobe Experience Manager
You should also check out the We.Retail Journal Sample Angular application: aem-sample-we-retail-journal/angular-app at master · adobe/aem-sample-we-retail-journal · GitHub . The recommendation is to develop the Angular application outside of AEM (using webpack, or other build project of your choice). Only the compiled JavaScript and CSS would be ported into AEM in the form of a client library, aem-clientlib-generator - npm is a useful tool for this. This design pattern could be used on 6.2/6.3 ...

Views

945

Like

1

Replies

0
Re: Issue with card component in AEM 6.4
Avatar
Ignite 1
Employee
dgordon86
Employee

Likes

49 likes

Total Posts

73 posts

Correct Reply

26 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
dgordon86
- Adobe Experience Manager
Hi vinis2730879 ,The following simply describes what fields will be in the dialog.```articlePath - path finder field for authors to select an article that will drive the content of the card. It is a required field.titleOverride - The card by default will display the underlying Article's title. This is an optional text field for authors to override the display title in the card.hideDescription - A checkbox that allows an author to toggle the display of the article's description in the card.```Ste...

Views

851

Likes

0

Replies

0
Re: Unable to resize components in AEM site
Avatar
Ignite 1
Employee
dgordon86
Employee

Likes

49 likes

Total Posts

73 posts

Correct Reply

26 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
dgordon86
- Adobe Experience Manager
Ah ok looks like the forward slash was accidentally deleted? make sure the contents of /apps/wknd/clientlibs/clientlib-site/components/text/text.less looks like below:/* WKND Text Styles */@import (once) "styles/default.less";@import (once) "styles/quote.less";

Views

1.0K

Likes

0

Replies

0
Re: Unable to resize components in AEM site
Avatar
Ignite 1
Employee
dgordon86
Employee

Likes

49 likes

Total Posts

73 posts

Correct Reply

26 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
dgordon86
- Adobe Experience Manager
Can you check: http://localhost:4502/etc.clientlibs/wknd/clientlibs/clientlib-base.css to see if there are any LESS compilation errors?

Views

1.0K

Likes

0

Replies

0
Re: where can I find clientlib-base.css through crxdelite?
Avatar
Ignite 1
Employee
dgordon86
Employee

Likes

49 likes

Total Posts

73 posts

Correct Reply

26 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
dgordon86
- Adobe Experience Manager
Hi arjuns75800874 , We.Retail uses the client library feature of embed to include additional client libraries so that only a single request needs to be made to the browser:I would inspect the we-retail.site client library and the file main.less for what you are looking for: /apps/weretail/clientlibs/clientlib-site/less/main.less

Views

847

Likes

0

Replies

0
Re: Styles not replicating to publish instance
Avatar
Ignite 1
Employee
dgordon86
Employee

Likes

49 likes

Total Posts

73 posts

Correct Reply

26 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
dgordon86
- Adobe Experience Manager
Have you ensured that the templates and associated policies have been published as well? There are also permissions associated with templates that need to be set on the publish environment so that it can be read by the anonymous user...

Views

1.2K

Likes

0

Replies

0
Re: CaaS for a page content in aem
Avatar
Ignite 1
Employee
dgordon86
Employee

Likes

49 likes

Total Posts

73 posts

Correct Reply

26 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
dgordon86
- Adobe Experience Manager
karansheel that is the expected behavior since when you call model.json at the Page level you will get the exported JSON from the Core Component Page: aem-core-wcm-components/PageImpl.java at master · Adobe-Marketing-Cloud/aem-core-wcm-components · GitHub and the JSON exported by the Responsive Grid Exporter: ResponsiveGridExporter ("The Adobe AEM Quickstart and Web Application.") If you want to override this JSON you will need to provide your own Sling Model for the Page component and your own ...

Views

2.7K

Like

1

Replies

0
Re: CaaS for a page content in aem
Avatar
Ignite 1
Employee
dgordon86
Employee

Likes

49 likes

Total Posts

73 posts

Correct Reply

26 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
dgordon86
- Adobe Experience Manager
With the latest version of the Content Services feature pack hitting: "/content/my-site/homepage.model.json" as you described should give you a combined JSON of the Page + any components that have been added to the page. Are you not seeing this behavior? Or are you trying to do something else?

Views

2.7K

Likes

0

Replies

3
Re: AEM ContextHub - how to add key:value to any store?
Avatar
Ignite 1
Employee
dgordon86
Employee

Likes

49 likes

Total Posts

73 posts

Correct Reply

26 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
dgordon86
- Adobe Experience Manager
Have you tried the setProperties method on the Store object? Store ("The Adobe AEM Quickstart and Web Application.")

Views

3.3K

Likes

0

Replies

0
Re: AEM 6.4 - Editable templates - Multiple parsys inside single component
Avatar
Ignite 1
Employee
dgordon86
Employee

Likes

49 likes

Total Posts

73 posts

Correct Reply

26 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
dgordon86
- Adobe Experience Manager
I'm assuming your wrapper component includes the Parsys Left/Right via a data-sly-resource or cq:incude? These will be artificial resources at first and the Template editor does not seem to like artificial resources. The solution is to make sure the nodes exist, either by manually adding them in the Template Type definition or by using something like cq:template in the component definition. Check out how Asset Share Commons does this:Root Component - asset-share-commons/root.html at develop · Ad...

Views

1.0K

Likes

0

Replies

0
Re: Empty Component Placeholder Text Missing
Avatar
Ignite 1
Employee
dgordon86
Employee

Likes

49 likes

Total Posts

73 posts

Correct Reply

26 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
dgordon86
- Adobe Experience Manager
The code looks good. The placeholder template just pulls from the component jcr:title property. I'm wondering if maybe there is an error with the ts.isEmpty method? What happens if you just change:data-sly-test.hasContent="${false}"andAlso FWIW I'd recommend using Sling Models over WCMUsePojo as a best practice

Views

1.3K

Likes

0

Replies

0
Re: Resizing of components in layout mode
Avatar
Ignite 1
Employee
dgordon86
Employee

Likes

49 likes

Total Posts

73 posts

Correct Reply

26 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
dgordon86
- Adobe Experience Manager
I would look at the CSS the responsive grid is outputting in your client library and make sure there is not a LESS compilation issue...

Views

6.8K

Likes

0

Replies

0
Re: How to use a workflow task step in a workflow.
Avatar
Ignite 1
Employee
dgordon86
Employee

Likes

49 likes

Total Posts

73 posts

Correct Reply

26 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
dgordon86
- Adobe Experience Manager
Hi Saurabh, how are you launching the workflow? Are you kicking it off via the Projects UI > Add work? The Create Task step relies on workflow metadata properties. If the project path is not set you will receive that error.

Views

119

Likes

0

Replies

0
Re: Workflow Launcher problem with project task workflow
Avatar
Ignite 1
Employee
dgordon86
Employee

Likes

49 likes

Total Posts

73 posts

Correct Reply

26 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
dgordon86
- Adobe Experience Manager
Correct. When you kick off the workflow through the Project UI the project.path is set on the workflow's metadata node.Possible workarounds when using the workflow launcher is to persist a project path property via workflow process step prior to the Create Task step.

Views

682

Likes

0

Replies

0
Re: how to do servlet unit testing
Avatar
Ignite 1
Employee
dgordon86
Employee

Likes

49 likes

Total Posts

73 posts

Correct Reply

26 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
dgordon86
- Adobe Experience Manager
I'd look into using Sling Mocks or other mocking frameworks to simulate complex objects that are impractical to incorporate into the unit test. The goal should be to isolate and test behavior of the code within the servlet, not necessarily the servlet itself. Check out Sling Mocks: Apache Sling :: Sling Mocks . Mocks can be used to unit test code prior to deployment.If you do want to some more real-world testing (on say a stage/QA environment) you can also look into server side integration testi...

Views

64

Likes

0

Replies

0
Re: Workaround for vh units in aem 6.3 (touch ui editor)
Avatar
Ignite 1
Employee
dgordon86
Employee

Likes

49 likes

Total Posts

73 posts

Correct Reply

26 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
dgordon86
- Adobe Experience Manager
In some cases, due to the AEM sites editor rendering the page in an iframe, certain CSS/JS is not compatible. It seems that you are running into that when using vh units. The work around is to have a small amount of CSS that is only loaded on the Authoring environment (wcmmode=edit / preview). This can facilitate the authoring experience but you can continue to use whatever CSS rules you want for the publish experience. This is the technique used for AEM screens since with screens most of the co...

Views

670

Likes

2

Replies

0
Re: Don't understand cssClassNames in aem-core-wcm-components 2.0.0
Avatar
Ignite 1
Employee
dgordon86
Employee

Likes

49 likes

Total Posts

73 posts

Correct Reply

26 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
dgordon86
- Adobe Experience Manager
Ultimately the method getCssClassNames() of ComponentContext is called: aem-core-wcm-components/PageImpl.java at master · Adobe-Marketing-Cloud/aem-core-wcm-components · GitHub .This is an internal api, but has some logic built in to inspect the component and add classes based on the name of the component and any any responsive grid integration. This method also integrates the Style System in AEM 6.3 /6.4: Style System . You can use the style system at the Page level by editing an Editable Templ...

Views

878

Likes

2

Replies

0
Re: Apply cug on dam asset folder
Avatar
Ignite 1
Employee
dgordon86
Employee

Likes

49 likes

Total Posts

73 posts

Correct Reply

26 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
dgordon86
- Adobe Experience Manager
In AEM 6.4 managing Closed User Groups for Assets is available ootb. A video can be found here: Using Closed User Groups with AEM Assets Unfortunately I don't know if this feature will be back ported to AEM 6.3...

Views

1.7K

Likes

0

Replies

1
Re: Identifier com.adobe.cq.wcm.core. cannot be correctly instantiated by the Use API
Avatar
Ignite 1
Employee
dgordon86
Employee

Likes

49 likes

Total Posts

73 posts

Correct Reply

26 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
dgordon86
- Adobe Experience Manager
Another user had a similar issue and it was because the version of Java was not 1.8. More details here: Unresolved dependencies on fresh AEM 6.3.1 · Issue #12 · Adobe-Marketing-Cloud/aem-guides-wknd · GitHub

Views

1.2K

Likes

2

Replies

0
Re: Identifier com.adobe.cq.wcm.core. cannot be correctly instantiated by the Use API
Avatar
Ignite 1
Employee
dgordon86
Employee

Likes

49 likes

Total Posts

73 posts

Correct Reply

26 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
dgordon86
- Adobe Experience Manager
The error indicates that Core Components Page model is not registered correctly. A couple of things to check:1. Verify Local AEM Instance setup:Java 1.8AEM 6.3Service Pack 1​6.3 Feature Pack 205932. Verify that Core Components 2.0 have been uploaded and installed by navigating to CRX Pack Manager (http://localhost:4502/crx/packmgr/index.jsp)3. Look in the OSGi console (http://localhost:4502/system/console/bundles ) for the Core WCM Components Core bundle

Views

1.2K

Likes

2

Replies

0
Re: Getting Started with AEM Sites - WKND Tutorial
Avatar
Ignite 1
Employee
dgordon86
Employee

Likes

49 likes

Total Posts

73 posts

Correct Reply

26 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
dgordon86
- Adobe Experience Manager
Hi Madiha,IIRC a common convention in CQ development pre 6.x was to name the maven module content -> for htl, jsp, CSS/JS, etc... and bundle for OSGi/Java code. Since we now refer to content as page content it was confusing. The new convention is ui.apps -> for htl, CSS/JS, configs and core for OSGi/Java code. tl;drUse New Module Naming Convention = use ui.apps and core for the name of the maven modules

Views

1.0K

Like

1

Replies

0