Bug #23272 See Comments

Channel Import not moving Versioning settings

Version: 3.5.3 Reporter: cherrycreekmortgage

This is an archived bug report. If you are experiencing a similar issue, upgrade to the latest release and if that does not solve the problem, submit a new bug report

Channel Import is not importing the “Versioning” settings for a channel.

  • Channel settings (behavior) are not supported in Channel Sets, just the information architecture (structure). Please refer to the documentation for supported channel properties in Channel Sets.

    That does sound like a good suggestion to optionally support, though, so I’ll make sure and bring it up with the team. There would still be an issue with things like notification preferences, which should not be shared.

    Derek Jones
    03rd November, 2017 at 2:28pm
  • “Channel Import” suggests a complete copy of the channel setup, including all the channel settings. I’m surprised to learn this isn’t the case!

    We’re duplicating sites in MSM… a process that was very quick in EE2 but now takes 6-8 hours in EE3.

    03rd November, 2017 at 2:33pm
  • I am sorry that this isn’t doing what you expect, but I refer to the documentation again, which describes the purpose and behavior, including how it handles channels with relationships (ref #23271).

    Can I ask why are you cloning entire sites? In most cases this is a sign that the Site Manager is not being used in the most efficient manner, so we may have some suggestions for you that could reduce your build times.

    Derek Jones
    03rd November, 2017 at 2:43pm
  • We use MSM as intended. We are running multiple sites from one install. To create a new site, we make a clone and then make changes as needed for each site. All sites in our MSM install need to be independent from the others. They don’t share data but are similar but not exact.

    03rd November, 2017 at 2:52pm
  • The mere act of setting up channel layouts takes several hours alone since they can’t be copied.

    03rd November, 2017 at 2:54pm
  • That’s actually very uncommon for MSM installs (clones with minute changes, and no sharing). But that’s the situation you are in, so I understand and empathize because in your case I can see why those would be pain points. And it doesn’t help you now, but in v4 fields can be shared across MSM sites, which will dramatically simplify things for projects such as yours.

    Derek Jones
    03rd November, 2017 at 2:58pm
.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases