a0ecb912db
If someone deletes doctype and restores it back all customization are lost, there's no "real" reason to delete all these customization. They are only ever active if the doctype is being used. Explanations: - Custom field: is used by meta when doctype meta is requested, if meta isn't requested then custom field is effectively inactive. - Client script: loaded by meta when doctype is requested by desk. So inactive in deleted state. - Property setter: loaded by meta, so inactive when doctype isn't present. - Report: will break doctype isn't present, but user should delete them manually to avoid loss of "scripts" or anything special they might have done. Also report's doctype don't 100% indicate that it's based solely on that doctype. |
||
|---|---|---|
| .. | ||
| doctype | ||
| form_tour/doctype | ||
| page | ||
| report | ||
| web_form | ||
| workspace | ||
| __init__.py | ||
| notifications.py | ||
| README.md | ||
| utils.py | ||
Core module contains the models required for the basic functioning of frappe including DocType, User (user), Role and others.