Thanks for the fast work @mattiagiupponi !
We have deployed the changes and it is starting properly. @vineetasharma105 is currently reviewing its functionality.

The keyword - 'Subsite_exclusive' is working for documents, maps, datasets!!

The keyword - 'Subsite_exclusive' is working for documents, maps, datasets!!

great!

Thanks for the fast work @mattiagiupponi ! We have deployed the changes and it is starting properly. @vineetasharma105 is currently reviewing its functionality.

@gannebamm please let me know when your tests are done so I can merge the PR

Hi,
I am facing a question when dealing with subsite exclusive contents.
Question : Why the subsite exclusive contents , redirected via the linked resources click, still points towards and redirects to the homepage of geonode and the user is not anymore on the subsite page?
Enhancement/Requirement : as a user and as an admin also, the linked resources should not redirect to the homepage and rather stay on the subsite page, as the contents are 'subsite specific'.

As can be seen in the screen shot, the map (subsite_exclusive_test_map) and its related data set (subsite_exclusive_test_data)
are part of Holisoils subsite and the keyword and the group is set up accordingly. Still , the linked resources links points to the homepage.
Map : https://geonode-demo.thuenen.de/holisoils/catalogue/uuid/20e4d7c5-09fd-46ab-843b-f1bbb4bfee8d
dataset : https://geonode-demo.thuenen.de/catalogue/uuid/ac3361f8-8299-43de-a4f7-20d51a6c7c01
Subsitelink: https://geonode-demo.thuenen.de/holisoils/#/

Hi @gannebamm @vineetasharma105
With the new push the resources in the linked resource are now pointing to the subsite instead of the main catalogue page.
NOTE: it might be redundant to say, but the resource in the map MUST be part of the subsite in order to be saw via the linked_resource link

I just deployed the changes and they do not work as intended, yet.

See: https://geonode-demo.thuenen.de/holisoils/catalogue/uuid/6e60d107-3643-4ce5-9482-e098ad4e9305

The map is subsite exlusive, belongs to the holisoils group and uses only subsite ressources. It seems all ressources which are subsite_exclusive currently fail with: [ "Subsite not found" ] for a request like https://geonode-demo.thuenen.de/de-de/api/v2/datasets/22?api_preset=viewer_common&api_preset=dataset_viewer

We used these subsite specific variables:

# SUBSITE SPECIFIC CONFIGURATION
ENABLE_SUBSITE_CUSTOM_THEMES = True
ENABLE_CATALOG_HOME_REDIRECTS_TO = False
SUBSITE_READ_ONLY = False # return download_resourcebase and view resourcebase as permissions
SUBSITE_HIDE_EXCLUSIVE_FROM_SPECIFIC_API = True # If TRUE will hide the `subsite_exclusive` resources also from the detailed endpoint `/documents`, `/maps`, `/datasets`, '/geoapps`

The code is using 270c349

Did we misconfigure something?

Can you try by set SUBSITE_HIDE_EXCLUSIVE_FROM_SPECIFIC_API = False ?

redeployed.

Can you try by set SUBSITE_HIDE_EXCLUSIVE_FROM_SPECIFIC_API = False ?

This will fix the [ "Subsite not found" ] issue but the links still point to the main portal.

https://geonode-demo.thuenen.de/holisoils/catalogue/#/maps?d=57%3Bmap

uhm is working fine on my test environment with or without that variable, i'll give another check soon

Just as additional info:
We use this deployment https://github.com/Thuenen-GeoNode-Development/thuenen_atlas/tree/subsite_exclusive_test
Which is based on the docker blueprint plus some of our contrib apps. It will use the subsite dev branch as listed here: Thuenen-GeoNode-Development/thuenen_atlas@4183280

Hi @gannebamm
I made some local test using the project you linked and as you mentioned, the linked resources still point the main catalogue:

But the API v2 is returning the linked resources as expected by adding the subsite:

While on my local instance using geonode-master and mapstore-client-master is working as expected:

I notice that the mapstore-client used by the project, is a fork of the 52north mapstore client fork which is about 20 commits behind the production one for GeoNode 4.3.x which also includes improvement for the linked resources (GeoNode/geonode-mapstore-client@c7f6d10)

Can you please evaluate to upgrade the mapstore client and align it to the GeoNode one? So we can have the same environment.

As counterproof, i run a geonode 433 on my local instance and the subsite is correctly used for the linked resources:

@mattiagiupponi Thank you very much for the in-depth look! Yes, we will upgrade soon. See: Thuenen-GeoNode-Development/thuenen_atlas#58 (comment)