Current Behavior
When trying creating a page based on core/wcm/components/page/v3/page a error is written to the error log.
ERROR* [127.0.0.1 [1708344060911] GET /mnt/overlay/wcm/core/content/sites/createpagewizard/properties.html/conf/wknd/settings/wcm/templates/article-page-template HTTP/1.1] com.adobe.cq.wcm.core.components.commons.editor.dialog.inherited.InheritedField page is null
The error occours when a template is selected in the createpagewizard and the properties of the cq:dialog is shown.
It did not happen with the v2 page. I could replicated it with the wknd project in the version 3.2.0.
The InheritedField model trys to load a page with the PageManager based on the path of the template. There no page is found. And the error is logged.
Expected behavior/code
Best would be that the error don't appear. But a confirmation that this has no additional side effects would also be enough. :)
juw177
commented
1 week ago
Bug Report
Current Behavior When trying creating a page based on core/wcm/components/page/v3/page a error is written to the error log.
ERROR* [127.0.0.1 [1708344060911] GET /mnt/overlay/wcm/core/content/sites/createpagewizard/properties.html/conf/wknd/settings/wcm/templates/article-page-template HTTP/1.1] com.adobe.cq.wcm.core.components.commons.editor.dialog.inherited.InheritedField page is nullThe error occours when a template is selected in the createpagewizard and the properties of the cq:dialog is shown. It did not happen with the v2 page. I could replicated it with the wknd project in the version 3.2.0.The InheritedField model trys to load a page with the PageManager based on the path of the template. There no page is found. And the error is logged.
Expected behavior/code Best would be that the error don't appear. But a confirmation that this has no additional side effects would also be enough. :)
Environment