Write to log when templates are discovered in the environment or inherited templates directory
|Reported by:||Ryan J Ollos||Owned by:||Ryan J Ollos|
The site customization files are displayed in the Interface Customization section of the About Trac page. The customization files are also displayed in the error report 1.1.3.
We had a very long thread on trac-users this week where the issue was first that th:TracTicketTemplatesPlugin was not functioning, and we later discovered that the auto preview functionality also was not working because the
auto_preview_timeout variable was not being set in the template.
It turns out that the problem is due to
site.html in the environment's
templates directory. It remains to be seen what the content of those templates are, and why the user thought is was necessary to replace
A common first debug step is to "disable all plugins and see if the issue goes away". We often ask for the logs early on, so we can see which plugins are loading and if there are any exceptions. However, I haven't often thought to ask whether the user has any custom site templates.
It would be nice if we could write to the logs when templates are discovered in a site or inherited templates directory. Maybe this can be done at startup?
Or maybe there is a better idea so that we can get some hints in the logs that there are some custom templates present?