Copying custom fields on personnel file may lead to loss of data!

[J.Drake]

We used copy to create a new field but instantly got a MySQL error stating that "Column 'personnel_field_x' already exists". Surprisingly the field was added though, so after seeing that error we deleted the field again and created a field from scratch. However because that copied field had a link to the column in perscom_personnel it deleted the original column. We had to partially restore the table from a backup to get back to where we were.

Perhaps some defensive programming is required on this section, I suspect adding custom application fields is going to cause the same issue.

[ClanHBS]

@J.Drakethis is not an issue with perscom to my knowledge there is a bug in IPB that causes this to happen

[Jon Erickson]

As @ClanHBS stated, yes, this is linked to the magic clone method in PHP and IPB's method for copying active records. I've brought it up before but appears it still may be an issue.

[J.Drake]

Understood. Thanks for coming back to us about it. Perhaps if we all create enough support tickets with Invision they'd be more inclined to take a look at it ?