This is a weird issue and I can’t seem to locate the issue.
I have an attribute that doesn’t get saved when using the create view, but does when using the update view?
I checked the serialized data upon submission and the value is there, but I can’t figure out why it isn’t committed to the database.
Would anyone have any ideas of where I should be looking, what could possibly be causing this.
I’ve checked the model, controller, view files, I just can’t spot any differences or issues.
The Controller reports the value of the Attribute correctly in the post when saving, validates without issue, yet it isn’t actually committed to the database.
I’ve managed to get it function in a horrible way, after the initial controller save, I retrieve another model of that entry, push the same value and save it again.
Thank you bpanatta for the suggestions, I will investigate each.
For clarity, in the controller, I was already performing validation and then save(false), but the attribute would not save, yet, if I then find that same model, push the value a 2nd time and save(false) again, it takes?
I have to wait until this evening, but I will do more detailed testing. My biggest issue here is locally, on my dev machine it works fine, it is only on the production host that I am experiencing the issue, but can’t track down the difference. I’ve pushed the files (controller, model, view, …) and it remains.
Thank you once again for the pointers, I will explorer.
This appears to be Database related, as I just attempted to perform an Insert in the db, it save the records, but once again that one column is blank, so not a Yii issue, but something is off with my table.