Bug #23271 See Comments

Channel Import errors on relationship fields

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

I’m trying to duplicate a site in MSM using Channel Imports. Any channel with a relationship fields tries to set up the “other channel” fields if they already exist instead of just creating a relationship field which connects.


There is no way to skip the errors and hence no way to import the channel.

  • Same errors if a second Channel intentionally uses a field group that already exists… no way to skip the errors.

    03rd November, 2017 at 1:43pm
  • This is by design and not a bug. If you need a Channel to use existing fields, you may just create it and assign it the existing field group. Importing a Channel Set is only used to create new Channels with their accompanying fields, categories, etc.

    Derek Jones
    03rd November, 2017 at 1:45pm
  • In the case of the channels with relationship fields, the import shouldn’t set up fields for second channel in addition to the one being imported, just need the relationship field set up.

    For channels sharing a field group, there is a need to import all the channel settings. Need a way to continue the import past the errors.

    We are trying to duplicate a site in MSM.

    03rd November, 2017 at 2:30pm
  • I appreciate that it’s not behaving the way you are wanting it to, but this is not what Channel Sets were designed for. It is not intended to duplicate entire sites, and further, doesn’t have any way of knowing that you have an existing group that might match the necessary properties exactly.

    They are specifically made so that you can speed up the creation of new channels and all of the field groups that they need, enabling sharing between ExpressionEngine developers of complete information architecture of a specific channel. If it did not create the related channel and fields, then channel set would be incomplete.

    I agree that in your case a feature that allowed you to have a single export and import of all channels together would be useful, but that is not the intent of Channel Sets.

    Derek Jones
    03rd November, 2017 at 2:40pm
  • EE2 allowed for quick and easy cloning of sites in MSM… what in EE3 is there to replace this if not Channel Exporting/Importing.

    03rd November, 2017 at 2:57pm
  • Sadly we had to remove that feature entirely because it so frequently failed on even medium-sized databases, completely breaking the installation. It was great when it worked, but failed too often, was unable to support third-party fields that store data in their own tables, among other things. I’m sorry there is not a quick in-app solution to clone entire sites. Drop me an email at support@expressionengine.com, I have an idea that might save you some time that I cannot provide here in the bug tracker.

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

ExpressionEngine News!

#eecms, #events, #releases