You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Backup your database first. Add field called "Field 1" to a content type. Add that same field again. It adds the duplicate field to the customm_fields table, and then throws a db error at the last moment:
Now delete the duplicate field, and here's where it starts to go bad:
because indeed, the field has been deleted from the content type table, even though you only deleted one of the two same-named fields.
And now there is no apparent way to recover without manually intervening in the db. You can't delete the original field and re-add it to sync things back up because it fails on dropping the field from the table:
Can't DROP 'field_1'; check that column/key exists
ALTER TABLE test DROP field_1
So you have to add a field called field_1 to the affected content type record structure by hand, then you can delete and re-add to make sure everything is good.
The text was updated successfully, but these errors were encountered:
Backup your database first. Add field called "Field 1" to a content type. Add that same field again. It adds the duplicate field to the customm_fields table, and then throws a db error at the last moment:
![pic1](https://camo.githubusercontent.com/5e1bb18c0f99cc2f75e7a744cfd636d1fdb2abee354ca7c54d7195edbe650654/68747470733a2f2f662e636c6f75642e6769746875622e636f6d2f6173736574732f323932363039312f313636393031372f62386264646530342d356336662d313165332d393939612d6539313632376462363533362e706e67)
![pic4](https://camo.githubusercontent.com/39ae15e8ea32ca921bfb27baf8cfa3e25937bcb8257be395c184d200431c987b/68747470733a2f2f662e636c6f75642e6769746875622e636f6d2f6173736574732f323932363039312f313636393036392f61623861363638342d356337302d313165332d383335662d6663363330633063613064662e706e67)
![pic5](https://camo.githubusercontent.com/1a24ee3261ea258faa1a8e28874da1746d33b2123e203f92e1dd006bca377e56/68747470733a2f2f662e636c6f75642e6769746875622e636f6d2f6173736574732f323932363039312f313636393038392f65306230336261652d356337302d313165332d383331612d6133626264393730346334662e706e67)
Now delete the duplicate field, and here's where it starts to go bad:
![pic2](https://camo.githubusercontent.com/999a1f5d2e08a1b8e00075d44567129b8c1d8396a31e2f0a8183e09716bf3deb/68747470733a2f2f662e636c6f75642e6769746875622e636f6d2f6173736574732f323932363039312f313636393034362f32616265353062302d356337302d313165332d396666362d3639636665373661343734312e706e67)
![pic3](https://camo.githubusercontent.com/16e195a05c13b5ac514bc770fae9bf8e48c3e9e6f47343fb658529869a7acc59/68747470733a2f2f662e636c6f75642e6769746875622e636f6d2f6173736574732f323932363039312f313636393036342f37326433616237302d356337302d313165332d393636342d3462336535663537366537372e706e67)
because indeed, the field has been deleted from the content type table, even though you only deleted one of the two same-named fields.
And now there is no apparent way to recover without manually intervening in the db. You can't delete the original field and re-add it to sync things back up because it fails on dropping the field from the table:
Can't DROP 'field_1'; check that column/key exists
ALTER TABLE
test
DROPfield_1
So you have to add a field called field_1 to the affected content type record structure by hand, then you can delete and re-add to make sure everything is good.
The text was updated successfully, but these errors were encountered: