Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-2595

When activating nodes in config workspace all sub nodes of mgnl:contentNode type are accidentally pulled in as well.

    XMLWordPrintable

    Details

    • Release notes required:
      Yes
    • Magnolia Release:
      5.2.2

      Description

      This is due to default rule being applied on activation trigged by "publish" action in config. Setting itemTypes to empty string on this action should be enough to work around.
      However since other apps (e.g. jcr browser) tend to extend from "configuration" app, be careful that this doesn't break activation or versioning from other apps. ... all apps extending the browser or actions from configuration need to be checked.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              mdivilek Milan Divilek
              Reporter:
              had Jan Haderka
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response: