MSM Field Manager preventing fields with identical names?
Developer Preview
When we share content between websites using EE’s MSM, we use the site parameter within the channel entries tag to determine which site’s content we want to be displayed.
We really don’t want to have to list 10 or so different field names for each of the sites (there will be over 30 sites) in order for them to share content with each other. Also, when I new site is added, we don’t then want to go back through the temples of dozens of sites and add the new site’s field names.
I’m really hoping this was just an oversight or a bug?
We have a few builds in EE v2 and v3 where all the site’s have matching field names, so this would really make upgrading a bummer too.
Are you on the release candidate? Fields are now shared between all Sites, so you can just select them in the Channel settings, rather than having to duplicate fields on every site. So the name unique-ness is install-wide.
Keep in mind that if you are testing from an upgrade, that existing fields will not be available in this manner and are still limited to the site they were created on, though name uniqueness is still required. This will be addressed in an optional migration tool rather than the updater itself, since as you point out, many people using MSM have dozens of fields that are named the same, and we can’t make assumptions about merging or renaming, since we don’t know the site builder’s intent, nor what settings from which of the “duplicates” should be observed.
I’m on RC1 but there was already an existing site and as you stated, it’s fields aren’t available for selection. So there will be a migration path available in the future, but for now, I will need to create unique field names. Looking forward to creating fields ONCE for the whole install, just wrapping my brain around how it affects everything.
Ok.. I think I’ve got it. I see how it will work moving forward. We’re still maintaining some EE 1.0 sites, so I’m trying to hold four generations of EE’s methods/rules in my tiny brain at the same time.
Thanks.
Looking forward to creating fields ONCE for the whole install, just wrapping my brain around how it affects everything.
Yes, us too! Any new installs on v4 shouldn’t require any brain wrapping, just intuitive and friendly.
so I’m trying to hold four generations of EE’s methods/rules in my tiny brain at the same time.
I hear you! Moving away from legacy without breaking things is definitely a challenge for mature software, so we can relate.