The neighborhood audit trail (/p/admin/audit/) includes changes to the neighborhood project (e.g. membership, tools) and some of the neighborhood settings (e.g. tracking id) but not all of the neighborhood settings (e.g. Project Template). Everything on the /p/_admin/overview form should be tracked. Some of the form fields don't show up by default (e.g. custom CSS, tracking field) but make sure those are recorded to the audit trail too.
I don't think we've stored multi-line records (like home content HTML, and project template) to the audit log before, so make sure they come through decently.
created #114: [#4534] Save changes to neighborhood settings in audit trail (2cp)
Related
Tickets:
#4534closed #114, changes are in 42cc_4534
Good. Nice refactoring with the
log_if_changed
function