(Click to enlarge)

In fact, none of the names of the fields of the edit profile screen are showing either.

(Click to enlarge)

(Click to enlarge)

Oh, they are showing, halfway down the page after all those blank entries. Adding info to what I believed to be the CPF I created then saving-

PHP NOTICE [8] Undefined offset: 2 in sources_custom\hooks\systems\upon_query\user_export.php on line 81 (version: 10 RC7, PHP version: 5.6.20, URL: /sites/kal/site/index.php?page=members&type=view&id=2)

Same with the CFP names, viewing the last page of entries shows that they are there after the blank entries.

The CPF I added doesn't seem to be appearing on the profile edit screen though... Adding my first and last name and saving tells me that 'the two passwords do not match'.

Some elements of the profile, like the selection of which groups can message you isn't styled correctly.

(Click to enlarge)

CPF I added has the name '83' and the description '84' on the main site, it is 'Hero Name' on MSN and the id is 81 and I didn't enter a description :)

Usergroups on the MSN all have the name N/A.

I think I will end my venture into the exciting but confusing world of MSN installs for now.

The crux of this is one of your sites has Support content translations enabled, and one does not. It must be the same for all, otherwise the DB structures are not compatible.

We will document this, as Support content translations was not a choice in prior versions.

The user_export.php thing is a specific bug between the non-bundled user_simple_csv_sync addon and M.S.N.s. Fixed.

Yes this is true. I thought the MSN site only used the CNS tables for Members. I thought the MSN database could have different settings. If it cannot, then should there be a config option for translations? Can it not just use the main site settings for things that would conflict?

It's due to fundamental difference in database structure caused by that installation option, it's much deeper than an on/off setting.

Okay, but would it not make sense for MSN installs to use the main site db settings for things this like (anything that would conflict or cause an issue) and not present these sort of options at all? I enabled it on the MSN because it seemed relevant there and I was presented with the option. If not, fair enough, I don't understand how everything works really, just how it appears to be :)

If content translation is on for the main site then it is enabled for all sites. Otherwise if it is off, then enabling it on a MSN is pointless anyway?

To be honest we don't want to invest in making MSN stuff more user-friendly due to the sheer amount of tuning it would need to achieve that in a way reflecting current expectations for consumer products - there's no way we could re-coup that investment unless a company comes along and is willing to put salary-level investment into it to meet their needs. That could happen, but until it does, we just want to make sure it does what it says and that any particular requirements like this are covered within the documentation.

TBF, what we are or aren't willing to invest in is nothing to do with what should and shouldn't be on the tracker - so I'll create an issue for it :).

Thanks, I wasn't pushing this as an actual issue. As the feature exists I was trying to ensure it is foolproof. It is a useful feature and I think it's a major selling point of Composr, as is Demonstratr. A lot of people over the years have wanted this kind of functionality (I recall WordPress and phpbb attempts at this) on far less useful platforms than this. On Composr it's pretty amazing, but I can understand the reluctance to highlight and support these features as I am sure it is a lot of work.