Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
In my mashup, when embedding a "Variable Input" extension object from a QS app, require.js automatically rename the stylesheet reference from "style.css" to "style.css.js" which causes a "404 Not Found" javascript error. Anyone knows what to do to bypass or rectify this?
My code below.
var prefix = window.location.pathname.substr( 0, window.location.pathname.toLowerCase().lastIndexOf( "/extensions" ) + 1 );
var config = {
host: "###", // Hidden in code snippet for privacy
prefix: "/",
port: 443,
isSecure: true
};
//to avoid errors in workbench: you can remove this when you have added an app
var app;
require.config({
baseUrl: (config.isSecure ? "https://" : "http://" ) + config.host + (config.port ? ":" + config.port : "" ) + config.prefix + "resources"
});
function QlikObjectsRender() {
window.qlik.resize();
}
require(["js/qlik"], function (qlik) {
window.qlik = qlik;
qlik.setOnError( function (error) {
console.log(error);
PageLoader(-1, error);
});
app = qlik.openApp('652969cf-2092-4884-af59-fe6464b3c92d', config);
// The code to add the variable input extension object.
app.getObject('qsInput', 'pxZVCZe');
});
function ReloadApp() {
app.doReload(0,false,false).then(function(){
app.doSave()
});
}
Which version of Qlik Sense are you running ?
There were a few defects in regard to that extension, the symptoms you report is related to defect QB-831, but there were other issues such as QB-2016.
All of those issues should already be solved in the latest Qlik Sense release (February 2021)
Hello @hermandup_anz
Is this the variable input extension from the Qlik bundled extension or something 3rd party ?
This should be easily solved by modifying the extension’s code.
There should be a line with text!./style.css
if you change it to css!./style.css
it should solve the issue.
The extension is Qlik bundled extension, so editing it is not preferable.
Which version of Qlik Sense are you running ?
There were a few defects in regard to that extension, the symptoms you report is related to defect QB-831, but there were other issues such as QB-2016.
All of those issues should already be solved in the latest Qlik Sense release (February 2021)
Thanks Damien for pointing that out. You're right, that does look like it's resolved in September 2020 version and we're on June 2020.