Page not visible in just one publisher among set of publishers within card carousel component | Community
Skip to main content
V
Veena1
Level 2
February 16, 2025
Question

Page not visible in just one publisher among set of publishers within card carousel component

  • February 16, 2025
  • 5 replies
  • 1571 views

Hi All,

we have a set of publishers for different regions like region A, B, C, D. One of the page within the card carousel component is missing in region A publisher, but is displayed fine in other regions publishers like B C D.

tried comparing the data of the page which is not visible with the page in working publishers and figured out a missing date property which is renamed with @named annotation as originalPublishedDate in the model.

On providing the published value missing page appears back and republish of page too works fine by fetching the current published date.

I tried to resolve in above mentioned way but the issue keeps resuming only in one publisher making us to figure out root cause. my assumption was the page might have been installed directly on to publisher A via package without publishing via author and i tried the same scenario by creating a new page but the new page appeared on card carousel component as i installed the package. w/o any publishing done from author side

Removing the published date from existing pages in the card carousel component causes them to disappear. 

Not sure what is causing the issue Any suggestions please?.

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

5 replies

aanchal-sikka
Community Advisor
aanchal-sikkaCommunity Advisor
Community Advisor
February 17, 2025

@veena1 

 

Is it the OOTB Replication properties being used? Are we selecting pages based on OOTB replication date?

As per my understanding, Replication properties are not synced to Publisher OOTB.

PID = org.apache.sling.distribution.serialization.impl.vlt.VaultDistributionPackageBuilderFactory.4c1becb6-7c02-4089-8aa6-1e779948815e Factory PID = org.apache.sling.distribution.serialization.impl.vlt.VaultDistributionPackageBuilderFactory aclHandling = IGNORE name = default package.filters = [/home/users|-.*/.tokens, /home/users|-.*/.rep:cache] property.filters = [/|-^.*/cq:lastReplicated|-^.*/cq:lastReplicatedBy|-^.*/cq:lastReplicationAction] type = jcrvlt

 Please verify the above configuration on all publish environments. The property.filters defines which properties should not be pushed while publishing. 

Aanchal Sikka
    V
    Veena1Author
    Level 2
    February 17, 2025

    @aanchal-sikka I am not sure if it is OOTB Replication properties being used? or Are we selecting pages based on OOTB replication date? but pages can be enabled and disabled either from actual published date or from the republished date. yet to check this.

    But whatever the case is shouldn't it work for all pages in my case its only one page that is not visible and just in one publisher but works fine in others

    aanchal-sikka
    Community Advisor
    aanchal-sikkaCommunity Advisor
    Community Advisor
    February 17, 2025

    @veena1 

     

    Ideally yes... The behavior should be same on all publisher. However, something is different for 1 that could be causing difference in behaviour.

     

    The configuration can be validated from http://localhost:4502/system/console/configMgr 

     

    Configuration name: Apache Sling Distribution Packaging - Vault Package Builder Factory

    Aanchal Sikka
      ManviSharma
      Adobe Employee
      ManviSharmaAdobe Employee
      Adobe Employee
      February 17, 2025

      Hi Veena,

      The issue you're experiencing with the missing page in the card carousel component in Region A's publisher seems to be related to the handling of the originalPublishedDate property.

      1. Have you tested the scenario by creating a new page and observing if it encounters the same issue?
      2. Are there any errors or warnings in the logs when trying to render the page on Region A's publisher?
      3. Is the originalPublishedDate property explicitly required for the page to render in the card carousel component?

      Regards,

      Mnavi Sharma

       

        V
        Veena1Author
        Level 2
        February 17, 2025

        Hi @manvisharma Yes the originalPublishedDate is explicit for the page to be visible i tried removing the date in existing pages of card Carousel the page will simply not be visible. 

        i created page in local author and tried to reproduce same scenario in local publisher via package. And the page was visible couldn't try it on PROD publisher because of minimal access. Let me see if i can obtain

        kautuk_sahni
        Community Manager
        kautuk_sahniCommunity Manager
        Community Manager
        February 18, 2025

        @veena1 Did you find the suggestions helpful? Please let us know if you need more information. If a response worked, kindly mark it as correct for posterity; alternatively, if you found a solution yourself, we’d appreciate it if you could share it with the community. Thank you!

        Kautuk Sahni
        V
        Veena1Author
        Level 2
        February 18, 2025

        Not yet, will keep it posted as i venture right answer further help would benefit

         

        giuseppebaglio
        giuseppebaglio
        Level 10
        February 18, 2025

        The behaviour you're describing points to a few potential root causes:

        1. Content inconsistency: The originalPublishedDate property may be handled differently across publishers during package installation vs. normal replication. Since installing packages directly bypasses normal replication filters and handlers, this could explain why direct package installation works while regular publishing fails.

        2. Replication filter: Check if there's a custom replication filter on Publisher A that might be filtering out pages missing the originalPublishedDate property. This would explain why the issue is isolated to one publisher.


        Here some suggestions that can help you for troubleshooting:

        1. Compare the complete node structure (not just visible properties) between Publisher A and working publishers using CRX/DE
        2. Review replication logs on Publisher A when publishing from author
        3. Check for any custom replication filters or preprocessors specific to Publisher A
        4. Verify Publisher A's OSGi configuration matches other publishers
        5. Consider clearing Publisher A's repository and performing a full content sync (really extreme though!)


        Given the importance of it for proper rendering, you may also want to implement a validation check in your model to ensure the displayed slides are in numbers that is expected.

          V
          Veena1Author
          Level 2
          February 19, 2025

          @giuseppebag Thanks for the detailed list. How do i check for custom replication filters or preprocessors in publishers?

          Also this is just happening with only one page in the card carousel component but rest are fine?

           

          giuseppebaglio
          giuseppebaglio
          Level 10
          February 19, 2025

          @veena1 in AEM they implement interfaces such as ReplicationContentFilter, AgentFilter or Preprocessor. To locate custom implementations navigate to http://localhost:4502/system/console/components (adjust the host and port as necessary). Now search for ReplicationContentFilter, AgentFilter or Preprocessor, you will see all components implementing these interfaces - custom filters typically have unique names or identifiers distinguishing them from Adobe's default implementations.


          Besides you can examine your project's source code to identify classes implementing the ReplicationContentFilter, AgentFilter or Preprocessor interfaces.
           
          In case you're under a multi-tenant AEM solution, you can browse to /apps to locate custom OSGI configuration files from other projects (under pattern /apps/project-name/config) whose name contains ReplicationContentFilter, AgentFilter or Preprocessorr as prefix/suffix - it is possible some custom logic occurs in the related implementation class.
            kautuk_sahni
            Community Manager
            kautuk_sahniCommunity Manager
            Community Manager
            March 5, 2025

            @veena1 Did you find the suggestions helpful? Please let us know if you need more information. If a response worked, kindly mark it as correct for posterity; alternatively, if you found a solution yourself, we’d appreciate it if you could share it with the community. Thank you!

            Kautuk Sahni
            Terms & ConditionsAccessibility statement

            Loading footer...