You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 19, 2020. It is now read-only.
When there is no access to /conf folder ( and hence the page policy) to anonymous user on publish instance, then content attribute is empty as it gets populated via HierarchyPageImpl and code is not able to access conf folder
so to fetch the model json it accesses the current page's model
But when anonymous user has access to 'conf' folder, then it is populated
and now there are two calls to for model.json
because of these two calls nothing gets loaded in the app. I know the call is originated by page model manager, but the app should load in case of two calls as well, or the page specific call should not be initiated when rootmodel url is populated.
For now I removed the content attribute in rootmodel meta tag altogether, please let me know the better and appropriate solution.
The text was updated successfully, but these errors were encountered:
The two calls originate only on dispatcher - on publish, when cq:pagemodel_root_url is populated, only once call(rightly so) on the root page is sent to fetch the model, but in dispatcher with the shortened url and without .html , two calls originate. Please let me know if a cleaner solution is available.
When there is no access to /conf folder ( and hence the page policy) to anonymous user on publish instance, then content attribute is empty as it gets populated via HierarchyPageImpl and code is not able to access conf folder
so to fetch the model json it accesses the current page's model
But when anonymous user has access to 'conf' folder, then it is populated
and now there are two calls to for model.json
because of these two calls nothing gets loaded in the app. I know the call is originated by page model manager, but the app should load in case of two calls as well, or the page specific call should not be initiated when rootmodel url is populated.
For now I removed the content attribute in rootmodel meta tag altogether, please let me know the better and appropriate solution.
The text was updated successfully, but these errors were encountered: