Caconfig Editor is not publishing child nodes for collections | Community
Skip to main content
J
johns43992246
Level 2
March 7, 2023

Caconfig Editor is not publishing child nodes for collections

  • March 7, 2023
  • 1 reply
  • 2498 views

I have caconfig editor package as a maven dependency

 

<dependency>
    <groupId>io.wcm</groupId>
    <artifactId>io.wcm.caconfig.editor.package</artifactId>
    <version>1.12.0</version>
    <type>zip</type>
</dependency>

 

The caconfig editor renders like this,  it looks a little different from what I've seen documented, so I do wonder if its configured correctly. 

 

 


When I publish though, non of the resource nodes under the configuration are replicated into the publish environment.

 

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

Kiran_Vedantam
Community Advisor
Kiran_VedantamCommunity Advisor
Community Advisor
March 7, 2023

Hi @johns43992246 

 

Quick question:

When you publish it, is it showing the rest of the changes in the publish page?

Do you have access to publish the nodes?

Do you see the logs in the replication queue?

DO you see any errors in the logs?

 

Thanks,

Kiran Vedantam.

    J
    johns43992246Author
    Level 2
    March 7, 2023

    Do you have access to publish the nodes? YES

    Do you see the logs in the replication queue? I'm not sure how to setup the logger for caconfig in the sling logs. Any advice?

    DO you see any errors in the logs? I cannot find any in the error logs but I need help trying create a logger for this.

      J
      johns43992246Author
      Level 2
      March 9, 2023

      When I try to publish the collection I see this error:

       

      08.03.2023 14:29:09.989 *INFO* [[0:0:0:0:0:0:0:1] [1678303749956] GET /libs/wcm/core/content/sites/publishpagewizard.html HTTP/1.1] libs.cq.gui.components.siteadmin.admin.publishwizard.references.references$jsp Resource is /mnt/overlay/wcm/core/content/sites/publishpagewizard/jcr:content/body/items/form/items/wizard/items/publishstep/items/fixedColumns/items/fixedColumn1/items/references
      08.03.2023 14:29:10.018 *INFO* [[0:0:0:0:0:0:0:1] [1678303749956] GET /libs/wcm/core/content/sites/publishpagewizard.html HTTP/1.1] com.adobe.granite.ui.clientlibs.impl.HtmlLibraryManagerImpl Start building JS library: /libs/cq/gui/components/siteadmin/admin/publishwizard/clientlibs
      08.03.2023 14:29:10.314 *ERROR* [[0:0:0:0:0:0:0:1] [1678303749956] GET /libs/wcm/core/content/sites/publishpagewizard.html HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Uncaught SlingException
      acscommons.com.google.common.util.concurrent.ExecutionError: java.lang.OutOfMemoryError: unable to create new native thread
      at acscommons.com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2049) [com.adobe.acs.acs-aem-commons-bundle:4.11.2]
      at acscommons.com.google.common.cache.LocalCache.get(LocalCache.java:3951) [com.adobe.acs.acs-aem-commons-bundle:4.11.2]


      I did a little more reading and compared to the current implementation of the io.wcm.caconfig.editor

      Publish configurations

      By default, Context-Aware configurations are stored below /conf and can thus not published by editors using the AEM Author GUI. The Editor provides an “publish this page” button, which published the editor page itself.

      It is recommended to also deploy the wcm.io Context-Aware Configuration Extensions and activate the AEM Page persistence strategy. Then the reference provider also included in the extensions bundles detects changed and unpublished configuration pages below /conf when publishing the editor page, and allows to publish the configurations as well.

       

      I don't see any references to the io.wcm.caconfig.extensions in my POM files. I started trying to get the correct Maven dependency added. According to the support matrix here

      https://wcm.io/caconfig/extensions/

      I should be on 1.9.2 for extensions for the version of AEM I'm running. I only see it going up to in maven-central I only see it going up to 1.9.0 also in Github tags only go up to 1.9.0 

      https://github.com/wcm-io/io.wcm.caconfig.extensions/tags

      I'm going to try 1.9.0 but I have to get that maven artifact on boarded to my companies repo. Does this sound like the right approach?

      Terms & ConditionsAccessibility statement

      Loading footer...