Optional enable/disable status

[maderlock]

When creating a bunch of entities, only one of which is the front-end entity, it tends to only make sense for that single front-end entity to have enable/disable as an option. Along with the mandatory name field, it is the enable/disable status that I find myself having to manually strip out from most entities. Didn't this use to be an option?

[tzyganu]

@maderlock. I guess you are right. It does make sense to have the status field when you have frontend listings also.This also used to be an option in the older versions. I removed that option because It became hard to manage when generating the files for the extensions. I had a lot of if statements and a lot of different cases to tackle when the status field was optional. So I decide it to make it a system field. In case you don't need it when you have a module that affects only the backend all you need to do is to remove it from the install script and from the admin add/edit form and grid, before installing the module.
Sorry for disappointing you but I have no plans in the near future to make this optional again.
Like I said, to much work needed for something that can be removed easily after the module creation.

I will leave this open though, in case I have a sudden change of heart. 😄

[maderlock]

Thanks for the reply. I understand the decision to leave it out due to complexity. Having a system option seems a reasonable compromise.