there is a ticket about. I understand the problem but there is a logic problem. if is_active=False with versioning it means the record was deleted. So the record is ignored. It should not be visible at all except for auditing purposes. Now you are trying to bring it back to life (undelete it). It is not 100% obvious to me what the right behavior is. Granted that the right behavior is incorrect. Should one be allowed to set is_active=True or should one be forced to create a new record?
On Wednesday, 26 December 2012 04:27:04 UTC-6, Mandar Vaze wrote: > > I am also seeing this problem. Using Version 2.3.2 (2012-12-17 15:03:30) > stable > I get a flash "done" on submit. but is_active is still False. I wouldn't > call it "failing silently" either. > > Should I file a bug ? > > -Mandar > > On Monday, July 16, 2012 12:16:24 AM UTC+5:30, simon wrote: >> >> If you edit a record with is_active=True in admin then the edit does not >> commit but just fails silently. At worst there should be a warning to say >> this has failed. However sometimes would be useful to be able to reset >> is_active=True in admin. Or would that cause some confusion in the archive >> with undeleted rows? >> >> Also when you delete_record with versioning on then the record is still >> available but with is_active = True. To be consistent the record should be >> set to None. >> >> >> --
