-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extending Geonode Template #6995
Comments
👍 |
There's a need to exclude the free keywords from the editing page. |
… maps and documents
* [Resolves #6995] Increase UI block coverage in geonode * [Resolves #6995] ADVANCED_EDIT_EXCLUDE_FIELD available also in maps and documents Co-authored-by: Alessio Fabiani <alessio.fabiani@geo-solutions.it> (cherry picked from commit 76f62f2) Co-authored-by: mattiagiupponi <51856725+mattiagiupponi@users.noreply.github.com>
This issue has been used for extending the metadata editing page. By adding |
Is your feature request related to a problem? Please describe.
If you need to change a little part of geonode template (without touching the core) from an external app, sometimes is required to override the entire HTML instead of a small piece of the template due to the lack of
{% block %}
tags.For example, if I want to add a new facet in
_search_content.html
, I need to extend the template and override the whole content instead of override only the part related to the facets.Describe the solution you'd like
I'd like to start adding
{% block %}
tags in order to let geonode be more customizable from an external application.Here is an example:
Actual code:
geonode/geonode/templates/search/_search_content.html
Lines 29 to 46 in 2ebd319
Will become something like this:
So from my application, i can do something like this:
I think that will be really useful.
For sure will be a progressive process, I'll probably start from
search.html
,_search_content.html
andpanels.html
Describe alternatives you've considered
The alternatives, are don't add block tags and directly override the original template with the custom one, by changing the whole template
HTML
Additional context
Django docs on {% block %} tags.
The text was updated successfully, but these errors were encountered: