-
Bug
-
Resolution: Fixed
-
Major
-
4.4.0
-
None
-
4.4 RC4
In front-edition, it is possible to use the AddPageWizard with a custom configuration.
With this configuration, and no creation metadataset, the content properties card is displayed but blank.
<xsl:with-param name="config">{ "title": "<xsl:value-of select="ametys:escapeJS(ametys:translate(concat('skin.', $skin, ':SKIN_FO_ADD_ALERT_DIALOG_TITLE')))"/>", "force": true, "workflowInitActionId": "15", "show-card-tags" : false, "show-card-content" : false, "show-card-type" : false, "default-pagetype" : "template", "default-template" : "page", "default-zone" : "default", "default-pagecontent-type" : "contenttype", "default-contenttype" : "org.ametys.plugins.workspaces.Content.alert", "right-contenttype": "Plugin_Workspaces_Right_Alert_Create", "default-page-title" : "<xsl:value-of select="ametys:escapeJS(ametys:translate(concat('skin.', $skin, ':SKIN_FO_ADD_ALERT_DEFAULT_TITLE')))"/>", "default-contenttype-label" : "<xsl:value-of select="ametys:escapeJS(ametys:translate(concat('skin.', $skin, ':SKIN_FO_ADD_ALERT_CONTENT_TYPE_LABEL')))"/>", "pagecontent-service" : false} </xsl:with-param>
The test to check if the card is available should detect that it is not.
(And if there is a creation metadataset, with only the title, check if it was already set in another previous displayed card)