Issue in ./help/developing/data-layer/overview.md

Regarding https://docs.adobe.com/content/help/en/experience-manager-core-components/using/developing/data-layer/overview.html#installation-activation

See below #1 has more details

NEW Detailed:

1. Create the following structure below the /conf node:

• /conf//sling:configs/com.adobe.cq.wcm.core.components.internal.DataLayerConfig
• com.adobe.cq.wcm.core.components.internal.DataLayerConfig node type: nt:unstructured , sling:configs node type: sling:Folder

2. Add a boolean property called enabled and set it to true .
3. Add a sling:configRef property to the jcr:content node of your site below /content (e.g. /content//jcr:content ) and set it to /conf/ .

OLD :

1. Create the following structure below the /conf node:

• /conf//sling:configs/com.adobe.cq.wcm.core.components.internal.DataLayerConfig
• Node type: nt:unstructured

2. Add a boolean property called enabled and set it to true .
3. Add a sling:configRef property to the jcr:content node of your site below /content (e.g. /content//jcr:content ) and set it to /conf/ .

Also, please rephrase this sentence :

Once enabled, you can verify the activation by loading a page of the site outside of the editor. When you inspect the page you will see that the Adobe Client Data Layer is loaded.

Once enabled, validate the activation by loading a page in "View as Published" mode. When you inspect the page you will see that the Adobe Client Data Layer is loaded.

Hi,
we have enabled the core components and proxy the Accordion component on to the site. The Accordion works as expected in author and publish environment but fails in dispatcher. The accordion component rte field doesn't expand. There is no trace of errors either in dispatcher or console.log.
Link to the dispatcher : http://qaweb.nonprodaem.cnb.com/content/cnbcom/en/campaigns/test/awareness-demo.html

Publisher working image:

Testing if the Jira automation works on this repo.

I was looking at the Email Components documentation and saw that all of the "Sample Component Output" sections in the components (9 of them, the Page Component does not have the said section) are leading to 404s:

Affected Documentation Pages:

1. https://experienceleague.adobe.com/docs/experience-manager-core-components/using/email/components/container.html?lang=en
2. https://experienceleague.adobe.com/docs/experience-manager-core-components/using/email/components/title.html?lang=en
3. https://experienceleague.adobe.com/docs/experience-manager-core-components/using/email/components/text.html?lang=en
4. https://experienceleague.adobe.com/docs/experience-manager-core-components/using/email/components/image.html?lang=en
5. https://experienceleague.adobe.com/docs/experience-manager-core-components/using/email/components/button.html?lang=en
6. https://experienceleague.adobe.com/docs/experience-manager-core-components/using/email/components/teaser.html?lang=en
7. https://experienceleague.adobe.com/docs/experience-manager-core-components/using/email/components/experience-fragment.html?lang=en
8. https://experienceleague.adobe.com/docs/experience-manager-core-components/using/email/components/content-fragment.html?lang=en
9. https://experienceleague.adobe.com/docs/experience-manager-core-components/using/email/components/segmentation.html?lang=en

The links that lead to 404s inside those pages are

1. https://adobe.com/go/aem_cmp_library_email_container
2. https://adobe.com/go/aem_cmp_library_email_title
3. https://adobe.com/go/aem_cmp_library_email_text
4. https://adobe.com/go/aem_cmp_library_email_image
5. https://adobe.com/go/aem_cmp_library_email_button
6. https://adobe.com/go/aem_cmp_library_email_teaser
7. https://adobe.com/go/aem_cmp_library_email_xf
8. https://adobe.com/go/aem_cmp_library_email_cf
9. https://adobe.com/go/aem_cmp_library_email_segmentation

Also all the component pages seem to mention that the Email components are Compatible with AEM Cloud Service but in the
Introduction page it's mentioned that it's not: https://experienceleague.adobe.com/docs/experience-manager-core-components/using/email/introduction.html?lang=en

Issue in ./help/components/forms/form-container.md
The image illustrating the Post Form Data dialog is barely readable, something is wrong in its resolution or JPEG quality. The other images on the same page look all good.

Issue in ./help/components/forms/form-container.md

Leads to 404 error. Applies to all form components in documentation:
https://experienceleague.adobe.com/docs/experience-manager-core-components/using/components/forms/form-container.html?lang=en

Please correct the misspelling on a page somewhere.

AEM Project Archetype should not be listed below AEM Core Components, it is a total different project and deserves it's own space

Link reference https://experienceleague.adobe.com/docs/experience-manager-core-components/using/developing/archetype/overview.html?lang=en

This is a test with Saeed.

Issue in help/using/introduction.md

Both data elements and rules require writing custom code.
That is usually not suitable for business people. Is there any better integration planned in Adobe Launch which would allow to just use the UI without coding for setting up tracking?

Issue in ./help/developing/data-layer/analytics-integration.md

Issue in ./help/developing/archetype/using.md

Archetype 24 removed it.launcher and introduced ui.tests modules.

The documentation has been incorrectly updated to describe the ui.tests as Java tests - these are actually WebDriver.IO JavaScript tests.

The it.launcher module was renamed to ui.launcher instead of being removed from the list.

A new entry ui.tests is needed to provide context for that module, and the current entry should be renamed back to it.tests.

Issue in ./help/versions.md

This page shows 2.22.12 as the latest Core release.

According to comments in SITES-14545 Jira story, 2.23.2 is deployed to CS. My testing in Sandboxes seems to confirm the same.

Please update the page to correctly identify the latest release in Cloud Service.

Issue in ./help/components/accordion.md

The link to accordion in the below text in the page is broken
The latest technical documentation about the Accordion Component can be found on GitHub.

Issue in ./help/developing/archetype/overview.md

This issue is applicable to both the links below

• https://github.com/adobe/aem-project-archetype
• https://experienceleague.adobe.com/docs/experience-manager-core-components/using/developing/archetype/overview.html?lang=en

If you specify the groupId with a '-' in it, the projects gets created but the code fails in the build. It would be good if we handle this. Some options

1. Project creation fails fast with the error that the group id is invalid.
2. The hyphens in groupId field are replaced with . or _ or some other valid characters.
3. documentation calls out the WARNING explicitly.

Issue in ./help/components/button.md

Issue: Replace the word "Image" with "button" in the very last line of doc.

Expected The Button Component supports the AEM Style System .

Issue in ./help/components/button.md

Clicking on the Anchor links "configure dialog" and "design dialog" in the Usage section does not do anything.

Expected: Links should take the user to appropriate headings.

Issue in help/using/text.md

The screen shot of the edit dialog of the text component is out-of-date. Please update to include all edit option icons.

Issue in help/using/breadcrumb.md

The link to Component Library is broken under Sample Component Output section.

Current href: http://opensource.adobe.com/aem-core-wcm-components/library/breadcrumb.html

Possible correct href: http://opensource.adobe.com/aem-core-wcm-components/library/breadcrumb/hidden/level-1/level-2/breadcrumb.html

Issue in ./help/developing/success.md

Not an issue. I just wanna say I’m 3 days into learning AEM working with a React SPA and these docs are some of the best docs I’ve ever read.

Just the fact that the docs even talk about success and failpoints highlights the quality of these docs. Breadth alone is not inherently a good thing, but these docs have breadth of everything that is relevant to software developers.

This exceeded my expectations, and the effort that went into making the documentation / tutorials is much appreciated. Thanks.

y’all should make a blog post for engineers about your strategy for this.

Issue in ./help/components/content-fragment-list.md

Order By - Field of the content fragment model by which the list will be ordered
Only text fields (including numeric, date, and time) are selectable.

should be changed to:

Order By - Field of the content fragment model by which the list will be ordered
Only text fields,date, and time (excluding numeric) are selectable.

Date & time : adobe/aem-core-wcm-components#2376 - Fixed in 2.20.0
Number : adobe/aem-core-wcm-components#2396 - will be fixed in future release

Label: DocBugBlitz2023

Issue in ./help/developing/archetype/using.md
https://experienceleague.adobe.com/docs/experience-manager-core-components/using/developing/archetype/using.html?lang=en

In ablove url "Multi-Module Maven Project" diagram depicts that core-bundle is a part of "ui.apps" but according to latest maven archetype "core bundle" is embedded as part of "all" module .

Issue in ./help/developing/archetype/uifrontend-react.md

The link
https://www.npmjs.com/package/@adobe/cq-react-editable-components
should be
https://www.npmjs.com/package/@adobe/aem-react-editable-components

Issue in ./help/components/image.md

The link in the first tip to a discussion or page on the Adaptive Image Servlet appears to be broken. It look like it currently goes to a non-existant anchor in the same page.

Please see the document Adaptive Image Servlet for details on how it works.

Issue in ./help/components/content-fragment-component.md

The "Component Library" link on this page is broken:

https://aemcomponents.dev/content/core-components-examples/library/page-authoring/content-fragment.html - 404

Issue in ./help/get-started/using.md

• Download and Install link doesn't take to the correct section on the page. Incorrect:
  

• Download and Install link on the right panel (below ON THIS PAGE) takes to the correct section on the page. Correct:
  

[Logged by AEM Support]

The current version of the Quick Search Component is v1, which was introduced with release 2.0.0 of the Core Components in January 2018, and is described in this document.

ui.apps/pom.xml
The ui.apps pom (//ui.apps/pom.xml) provides the embedded tags for the filevault-package-maven-plugin. The embedded tags include the compiled core bundle as part of the ui.apps package and where it will be installed.

I don't see <embedded> in ui.apps/pom.xml, but I do see them in all/pom.xml.

Issue in help/using/list.md

The anchor link in the sidebar under On This Page > Edit Dialog > List Settings Tab > Search is broken. The href is pointing to "#search" which is an id on the wrapper div for that section, but it looks like CSS and possibly something more global is using the same id, which I'm guessing, is conflicting (who uses an id in a stylesheet anyway!? ;-) ). Possible solution would be to use a different id in the div wrapper and href.

As as side note, sidebar won't appear unless your viewport is > 1400px.

The latest version of core components 2.8 zip package from https://github.com/adobe/aem-core-wcm-components/releases is giving the the following error.

java.io.IOException: Error while reading stream
at org.apache.jackrabbit.vault.packaging.impl.JcrPackageImpl.getPackage(JcrPackageImpl.java:312)
at org.apache.jackrabbit.vault.packaging.impl.JcrPackageImpl.getPackage(JcrPackageImpl.java:277)
at org.apache.jackrabbit.vault.packaging.impl.JcrPackageImpl.extract(JcrPackageImpl.java:376)
at org.apache.jackrabbit.vault.packaging.impl.JcrPackageImpl.extract(JcrPackageImpl.java:360)
at org.apache.jackrabbit.vault.packaging.impl.JcrPackageImpl.install(JcrPackageImpl.java:354)
at com.day.crx.packaging.impl.J2EEPackageManager.consoleInstall(J2EEPackageManager.java:352)
at com.day.crx.packaging.impl.J2EEPackageManager.doPost(J2EEPackageManager.java:190)
at com.day.crx.packaging.impl.PackageManagerServlet.doPost(PackageManagerServlet.java:127)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:644)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)
at org.apache.felix.http.base.internal.handler.ServletHandler.handle(ServletHandler.java:123)
at org.apache.felix.http.base.internal.dispatch.InvocationChain.doFilter(InvocationChain.java:86)
at com.adobe.granite.license.impl.LicenseCheckFilter.doFilter(LicenseCheckFilter.java:308)
at org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:142)
at org.apache.felix.http.base.internal.dispatch.InvocationChain.doFilter(InvocationChain.java:81)
at org.apache.sling.i18n.impl.I18NFilter.doFilter(I18NFilter.java:131)
at org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:142)
at org.apache.felix.http.base.internal.dispatch.InvocationChain.doFilter(InvocationChain.java:81)
at org.apache.felix.http.base.internal.dispatch.Dispatcher$1.doFilter(Dispatcher.java:146)
at org.apache.felix.http.base.internal.whiteboard.WhiteboardManager$2.doFilter(WhiteboardManager.java:1002)
at org.apache.sling.security.impl.ReferrerFilter.doFilter(ReferrerFilter.java:326)
at org.apache.felix.http.base.internal.handler.PreprocessorHandler.handle(PreprocessorHandler.java:136)
at org.apache.felix.http.base.internal.whiteboard.WhiteboardManager$2.doFilter(WhiteboardManager.java:1008)
at org.apache.felix.http.sslfilter.internal.SslFilter.doFilter(SslFilter.java:97)
at org.apache.felix.http.base.internal.handler.PreprocessorHandler.handle(PreprocessorHandler.java:136)
at org.apache.felix.http.base.internal.whiteboard.WhiteboardManager$2.doFilter(WhiteboardManager.java:1008)
at org.apache.felix.http.base.internal.whiteboard.WhiteboardManager.invokePreprocessors(WhiteboardManager.java:1012)
at org.apache.felix.http.base.internal.dispatch.Dispatcher.dispatch(Dispatcher.java:91)
at org.apache.felix.http.base.internal.dispatch.DispatcherServlet.service(DispatcherServlet.java:49)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:542)
at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1701)
at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1345)
at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:480)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1668)
at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1247)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144)
at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:220)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
at org.eclipse.jetty.server.Server.handle(Server.java:502)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:370)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:267)
at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)
at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117)
at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333)
at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310)
at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:168)
at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:126)
at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:366)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:765)
at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:683)
at java.lang.Thread.run(Unknown Source)
Caused by: java.util.zip.ZipException: invalid entry size (expected 0 but got 334961 bytes)
at java.util.zip.ZipInputStream.readEnd(Unknown Source)
at java.util.zip.ZipInputStream.read(Unknown Source)
at java.io.FilterInputStream.read(Unknown Source)
at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:2314)
at org.apache.commons.io.IOUtils.copy(IOUtils.java:2270)
at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:2291)
at org.apache.commons.io.IOUtils.copy(IOUtils.java:2246)
at org.apache.commons.io.IOUtils.toByteArray(IOUtils.java:765)
at org.apache.jackrabbit.vault.fs.io.MemoryArchive.run(MemoryArchive.java:91)
at org.apache.jackrabbit.vault.packaging.impl.JcrPackageImpl.getPackage(JcrPackageImpl.java:310)

However if we download from Maven Repository
https://repo1.maven.org/maven2/com/adobe/cq/core.wcm.components.all/2.8.0/ the package installs.

Issue in help/using/text.md

The screenshot of the text component edit dialog is out-of-date. Please update so that it shows all of the edit option icons.

Issue in help/using/using.md
Issue in help/using/authoring.md

The contributors to the Core Components project state that core components will not work with static templates, but the documentation specifically states that it would work for both. Please update the docs to reflect the current state of affairs.

See below issues describing that Static Templates are not supported:
adobe/aem-core-wcm-components#100
adobe/aem-core-wcm-components#551

https://experienceleague.adobe.com/docs/experience-manager-core-components/using/developing/archetype/uifrontend.html?lang=en

(Image)
Running npm run dev starts the front-end build process

The image and text describes the ui.frontend (general), but the commands are different for ui.frontend (react).

Issue in ./help/components/tableofcontents.md

We are trying to follow this documentation, but nothing is getting displayed on the page. We think the documentation is not clear enough to explain how the content will get rendered. Either the component is not working or the documentation is not clear enough for us to follow and get this working.

Could you please review this ?

This is a test

See the title.

I don`t understand. Please what am i to download?

Issue in help/using/introduction.md

Issue in ./help/components/v2/list.md

https://experienceleague.adobe.com/docs/experience-manager-core-components/using/components/v2-components/list.html?lang=en#item-settings-tab

The List V2 at Item Settings Tab {#item-settings-tab} contains V3 dialog screenshot

Issue in ./help/components/sharing.md

This Social Sharing component has been DEPRECATED since Core Components 2.18.0, but this doc page makes no mention of this.

Ignore this issue