Details
-
Bug
-
Resolution: Unresolved
-
Major
-
xCM 6.0.0
-
None
Description
I am logued with the ADUMAS user which only has RWA permissions on the "About" section on the default prepackaged demo (through a LDAP group and not directly as a user).
All LDAP users have a forced integrity and WAI checks rule in the admin center. I added two images which are cuasing a WAI warning.
I turned on the workflow toolbar and I could publish this page (why if I have some blocking integrity checks?).
When clicking on it, this process something and launches the alert msg with the link to the workfow batch report. I click on it: blank pop-up.
Source code of the pop-up is:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<!-- cache:vars var="gwtInit" --><script type='text/javascript'>
var jahiaGWTParameters = {
op:"edit",
allowFileUnlock:"false",
serverPath:"http://localhost:8080/cms",
pathInfo:"/",
lang:"en",
serviceEntryPoint:"/gwt/",
pid:"14",
currentUser:"ADUMAS"
};
</script>
<link type="text/css" href="/gwt/resources/css/jahia-ext-all.css" rel="stylesheet"/>
<link type="text/css" href="/gwt/resources/css/xtheme-jahia.css" rel="stylesheet"/>
<link type="text/css" href="/gwt/resources/css/jahia-gwt-engines.css" rel="stylesheet"/>
<link type="text/css" href="/gwt/resources/css/jahia-gwt-templates.css" rel="stylesheet"/>
<!-- /cache:vars --><title>?org.jahia.engines.processDisplay.jobresult.label?</title>
</head>
<body>
<script id='jahia-gwt' type='text/javascript' src='/gwt/org.jahia.ajax.gwt.module.jobreport.JobReport/org.jahia.ajax.gwt.module.jobreport.JobReport.nocache.js'></script>
<div class="jahia-admin-gxt jobreport-gxt" id="jobreport" jahiatype="jobreport" groupName="QuickActivationJob" name="BackgroundJob-4f612bca-4844-4d2f-b414-d8aef80c54ea" ></div>
<script type='text/javascript'>
var jahia_gwt_messages = {
"workInProgressProgressText":"Chargement en cours...",
"workInProgressTitle":"Travail en cours, veuillez patienter..."
};
</script>
</body>
</html>
retestd by today's build, the problem of blank alert is still here even without any integrity check issue
Just published the home page of demo and clicked on wf alert's link...