[SOLVED] Profile update doesn't save

I see, so I hid it incorrectly, got it. I can see the changes you did, strange error message for it I'll implement it on the mainsite, and see what happens.

krileon wrote: Please take a look at your test site where I've reconfigured both tabs. I've disabled their CB Privacy edit display usages and configured all their fields not to display in profile edit. I've moved the params field off of HiddenFromUsers. Everything appears to be working fine now.

So
1) Reconfigure tabs to not have Privacy
2) Move Params field to 'Adgang'
3) Changed Params field to Show on Profile Edit
4) Changed fields to 'do not show on edit' on the two 'Hidden' tabs.
5) Removed the Privacy settings on the fields on the two 'Hidden' tabs.

Is that it? On the test site I had removed almost all privacy settings during testing, and that saves the info.
Currently I don't see the error on the 'live' site, but it doesn't currently save the setings either.
I'm going to create a new clone for the test site.

I've created a new clone for testing.
It seems that as soon as I have the privacy settings set up for the fields I've chosen, it doesn't save the profile.
I have 19 fields with privacy settings of different kinds.
Shall I pm you the field names if you want to have a look?

I've tried removing the 'edit' limits (ie. CB mod only and Bestyrelse only), and that makes it save.
So something is off in the privacy plugin.

I've only changed the edit limits on the live site, not on the test site if you want to dig into it.

When a field is removed from edit access its purged from the fields array during edit store processing. You need to avoid doing this against core fields like Name, Username, Formatname, Email, Params, etc.. This is why your test site was throwing errors and would not save. You need to be careful with what you block access to. CB Privacy can't prevent bad configurations without blocking possible usecases.

I see, so all fields without the cb_ in front of it, which is of course the ones created by myself, are core fields, and can't have privacy edit settings in it, but they can be on a hidden tab, and marked to not show up on edit?

More or less, yes that's the case. It really depends on what the field is though. The params field for example has to be shown on profile edit as it contains a workaround for Joomla params being infinitely json encoded (we will be moving this to our user object so you won't be forced to use the params field in a later release). You can hide these fields all you like on profile view of course as that has no impact on storage.