Clean up base.html template to remove legacy and unused code

[Gpetrak]

base.html template is the main template in GeoNode where many other templates depend on it. However, it currently contains a significant amount of legacy or misplaced code that should not reside in the base template.
For example, the social login logic implemented via django-allauth:

{% get_providers as socialaccount_providers %}
{% if socialaccount_providers %}
{% include "socialaccount/snippets/provider_list.html" with process="login" %}
{% include "socialaccount/snippets/login_extra.html" %}
<hr>
{% endif %}

is included even on pages like 404.html and 500.html, where it's not relevant or appropriate.

We should clean up base.html by removing legacy, unused, and unnecessary code, and ensure that only essential, shared layout elements are included.

[Gpetrak]

@giohappy I cleaned up base.html by removing unused or outdated sections. A detailed description is presented below:

1. Code related to socialaccount.
2. Code (style) related with the custom theme which seems outdated and replaced by the GeoNode client
3. The entire header block, which has been fully replaced by the GeoNode client.
4. The entire footer block, also replaced by the GeoNode client.
5. Outdated modals related to the header, such as confirmMsgBoxModalOK.
6. Long comments.
7. Legacy thumbnail-related code.

I didn't remove the following yet, let me know if we need them:

9. RTL languages support: See L163–L173. I'm not sure whether support for RTL languages is still required, so I’ve left this in for now. If it's no longer needed, we can remove it in this or on a separate issue. As I can see RTL languages like Arabic are existed in the ALL_LANGUAGES
10. GeoNode browser search support: Let me know whether we still need the OpenSearch integration. If not, I can remove that as well

The PR of this issue is available here: PR

It's worth noting that the DEBUG_STATIC setting and related template logic could be removed. This setting is used in base.html and other templates, but it doesn’t appear in any environment files unless explicitly set to True by a user. While we could remove it, it may be better to handle this in a separate issue, since several files are conditionally included only when DEBUG_STATIC is True. These files would need to be reviewed to ensure they're still needed after removing DEBUG_STATIC.

[giohappy]

Aren't the header and footer blocks used by other internal template pages still provided by GeoNode? Like profile, etc.
If it's not the case, go ahead and remove them.

I would keep the OpenSearch link. We still have the endpoint (backed by PyCSW) so I would keep it.

Regarding DEBUG_STATIC, I agree, a dedicated request must be created. I already planned to dedicate time to remove legacy and unused js libraries (source and vendored bundles, Grunt scripts, etc.). But we need to test lib by lib to see where they're still used.
Probably only inside the Profile and Groups pages.
Please go ahead and open the issue yourself.

[Gpetrak]

Aren't the header and footer blocks used by other internal template pages still provided by GeoNode? Like profile, etc.
If it's not the case, go ahead and remove them.

@giohappy I didn't remove them because the corresponding base.html of the GeoNode client extends the GeoNode's base.html and includes these blocks:
https://github.com/GeoNode/geonode-mapstore-client/blob/master/geonode_mapstore_client/templates/base.html#L18
https://github.com/GeoNode/geonode-mapstore-client/blob/master/geonode_mapstore_client/templates/base.html#L25

Beyond that, the block header is not used anywhere inside GeoNode. However block footer is used as an empty block in the app_new.html and app_edit.html templates. Not sure if these templates are still used on the current GeoNode.

In any case, since these blocks are used in the client's base template, I’ve kept them for now. Please let me know if you have a different opinion.

Regarding DEBUG_STATIC, I agree, a dedicated request must be created. I already planned to dedicate time to remove legacy and unused js libraries (source and vendored bundles, Grunt scripts, etc.). But we need to test lib by lib to see where they're still used.
Probably only inside the Profile and Groups pages.
Please go ahead and open the issue yourself.

Fine ok

[giohappy]

Beyond that, the block header is not used anywhere inside GeoNode. However block footer is used as an empty block in the app_new.html and app_edit.html templates. Not sure if these templates are still used on the current GeoNode.

In any case, since these blocks are used in the client's base template, I’ve kept them for now. Please let me know if you have a different opinion.

Those templates are somehow related to the views that create new geoapps. I'll be honest, I don't know if they're ever used, but we need to check their relation with the client code that manages geoapps (Geosory and Dashboard).

[Gpetrak]

@giohappy as I saw, the app_new.html and app_edit.html included in the geoapps app, are not used by the current GeoNode. Regarding the logic of Geostory and Dashboard, GeoNode client, replaces these files with the following ones:

• app_new.html and
• app_edit.html

which are introduced in the hooksets.py

However, I don't think that we can remove the header and footer blocks because they are used on the extended base.html from GeoNode client. As a result, if we remove them from the main base.html of GeoNode, pages like People and Groups will not display the header or footer.

For example: