If you uninstall a field, the field values remain in the database. This is good if you have issues with the field and try to uninstall and reinstall, but shouldn´t there be any option to delete field-data that is not used anymore?
Labels |
Added:
?
|
Category | ⇒ | com_fields |
Status | New | ⇒ | Discussion |
So it´s the developers responsibility, right?
I think the next time you save the item that data was associated with, the values would be deleted.
The values will not show up anywhere, right? It's just the orphaned data that bugs you?
Imho it's not a big issue beside that it is filling the database a bit.
It's just the orphaned data that bugs you?
Yes, i think thats not "clean" - is it?
I think it would be great if the field is somehow marked in the fields manager as unavailable because the plugin is either unpublished or uninstalled. But I wouldn't delete it automatically.
If the orphaned field is deleted manually, the assigned values will be deleted as well.
I think it is the responsibility of com_fields to manage that situation properly. At minimum I would expect a warning message that there are still fields of that plugin which got unpublished or uninstalled.
Status | Discussion | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-10-05 13:28:01 |
Closed_By | ⇒ | brianteeman |
When a 3pd component is uninstalled are then not also the categories uninstalled automatically of this component?
The extension installer API does that, not the components involved. And there have been a fair number of issues opened about that behavior as well.
@coolcat-creations I think you an use the postflight script and remove the data manually