Uploaded image for project: 'Hippo CMS'
  1. Hippo CMS
  2. CMS-14112

Show "Add" button in CM for xpages even when xpages folder is not in channel root

Details

    • Improvement
    • Status: Closed
    • High
    • Resolution: Fixed
    • None
    • 14.4.0
    • None
    • None
    • 0.5
    • Flagged
    • Quasar
    • Puma Sprint 247, Puma Sprint 248, Puma Sprint 249

    Description

      Currently, for the Add button to show up in the channel manager, the xpages folder that is associated with the channel must be located in the channel root and can not be a subfolder. This is limiting for certain customers / use cases. It should be possible to have the xpages folder anywhere in the channel content.

      Attachments

        Issue Links

          Activity

            There is a strange behavior that even though you set-up all the properties for another folder to be the root xpage folder for a channel, you have to delete all the channelids from the previous folder and all its subfolders.

            After discussion with meggermont we have concluded that this is not expected.

            ntrajkovski Nikola Trajkovski added a comment - There is a strange behavior that even though you set-up all the properties for another folder to be the root xpage folder for a channel, you have to delete all the channelids from the previous folder and all its subfolders. After discussion with meggermont we have concluded that this is not expected.

            I now understand why it's failing: sitemap configuration is missing for the cmxpagefolder. 

            Suppose I create a new (translated) folder in the content perspective named 'foo' and add the mixin hippostd:cmxpagefolder to /content/documents/brxsaas/foo and set channelid property to brxsaas. Then I also have to add a new sitemap entry at /hst:brxsaas/hst:configurations/brxsaas/hst:workspace/hst:sitemap:

            /foo:
              jcr:primaryType: hst:sitemapitem
              /_any_:
                jcr:primaryType: hst:sitemapitem
                hst:relativecontentpath: foo/${1}
            

            Once that is in place then it all works as expected. That's the part I forgot to mention in the verification instructions. We'll also have to describe that in the documentation (in PRODDOCS-2249).

            The way to verify this is best via some custom bootstrap yaml because that is also how developers will have to do it. This also will prevent issues because then all config is present at the start and is automatically copied into the preview channel.

            meggermont Michiel Eggermont (Inactive) added a comment - - edited I now understand why it's failing: sitemap configuration is missing for the cmxpagefolder.  Suppose I create a new (translated) folder in the content perspective named 'foo' and add the mixin hippostd:cmxpagefolder to /content/documents/brxsaas/foo and set channelid property to brxsaas. Then I also have to add a new sitemap entry at /hst:brxsaas/hst:configurations/brxsaas/hst:workspace/hst:sitemap: /foo: jcr:primaryType: hst:sitemapitem /_any_: jcr:primaryType: hst:sitemapitem hst:relativecontentpath: foo/${1} Once that is in place then it all works as expected. That's the part I forgot to mention in the verification instructions. We'll also have to describe that in the documentation (in PRODDOCS-2249). The way to verify this is best via some custom bootstrap yaml because that is also how developers will have to do it. This also will prevent issues because then all config is present at the start and is automatically copied into the preview channel.

            Hi ntrajkovski

            As indicated, it's working with the additional sitemap configuration. Can you please verify.

            meggermont Michiel Eggermont (Inactive) added a comment - Hi ntrajkovski As indicated, it's working with the additional sitemap configuration. Can you please verify.
            ntrajkovski Nikola Trajkovski added a comment - meggermont LGTM!

            Merged, back-ported, closing as fixed.

            meggermont Michiel Eggermont (Inactive) added a comment - Merged, back-ported, closing as fixed.

            People

              Unassigned Unassigned
              ghendrix Gijs Hendrix (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: