Revise template section into distinct example with a note about include #5124
Conversation
Some clarifications from gitter discussion
| #. Many templates are constructed using ``#include``, for example :file:`collection.ftl` above uses ``<#include "common-header.ftl">`` located next to :file:`collections.ftl`. | ||
|
|
||
| Presently each family of templates manages its own :file:`common-header.ftl` (as shown in the difference between :file:`ogc/features` service templates, and getfeature templates above). | ||
|
|
||
| #. A restart is required, as templates are cached. |
There was a problem hiding this comment.
I'm not sure this is actually the case, I've been changing templates a lot without having to restart during development. Wondering if it's somehow context specific.
Everything other change looks ok.
There was a problem hiding this comment.
It would be great if the template was not cached, I did not figure out what was happening.
There was a problem hiding this comment.
Templates are cached through all GeoServer (the classic Freemarker ones for WMS have always been) and are listening to file changes. I cannot reproduce the issue you're trying to report in the docs. Can you confirm it's actually happening on your end? How does it happen?
There was a problem hiding this comment.
@jodygarnett mind, above I was not asking about a diagnosis, but about steps to reproduce.
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
This issue has been automatically closed because it has not had recent activity. Please re-submit with updates if you want to resume work on this topic. Thank you for your contributions. |
Some clarifications from gitter discussion
Checklist
For all pull requests:
mainbranch, eventual backports will be managed later. This can be ignored if the PR is fixing an issue that only happens in a specific branch, but not in newer ones.