Oct 24th, 2011, 12:36 PM
Hi Yavor,
Hmm! First off, this isn't related to the 2.1.5 upgrade - that just contained bug fixes & a new way to manage the field types (the Core Field Types module).
It sounds like something didn't get updated properly in the database when you renamed the field. Try this: edit the View that you're encountering the error, and just click "update". That should reset a lot of the info. Then try to add/delete a record in that View again.
Let me know how it goes!
- Ben
[btw, part of the upcoming System Check module (not the 1st release, which will be today) will be some additional database integrity tests to confirm there aren't problems with the actual data. That will no doubt help for things like this - it'll also help ME locate issues].
Hmm! First off, this isn't related to the 2.1.5 upgrade - that just contained bug fixes & a new way to manage the field types (the Core Field Types module).
It sounds like something didn't get updated properly in the database when you renamed the field. Try this: edit the View that you're encountering the error, and just click "update". That should reset a lot of the info. Then try to add/delete a record in that View again.
Let me know how it goes!
- Ben
[btw, part of the upcoming System Check module (not the 1st release, which will be today) will be some additional database integrity tests to confirm there aren't problems with the actual data. That will no doubt help for things like this - it'll also help ME locate issues].