If the Landing Page configuration is activated in Configure Views, it shows on the live site, but not while rendering the view in proxy. On the live site, we see that the direct child of nde-landing-page-config is nde-landing-page-renderer, and the nde-landing-page element does not exist. In proxy, the direct child of nde-landing-page-config is nde-landing-page, and nde-landing-page-renderer does not exist.
This is inconvenient for anyone who wants to develop/test customizations but also wants to use landing page configuration in Alma. Is it intended?
If the Landing Page configuration is activated in Configure Views, it shows on the live site, but not while rendering the view in proxy. On the live site, we see that the direct child of nde-landing-page-config is nde-landing-page-renderer, and the nde-landing-page element does not exist. In proxy, the direct child of nde-landing-page-config is nde-landing-page, and nde-landing-page-renderer does not exist.
This is inconvenient for anyone who wants to develop/test customizations but also wants to use landing page configuration in Alma. Is it intended?