Unable to load Background image in a container WebIQ v2.9

[Yacine]

Hello Team, 

I configured a background image through a CSS class in order to be integrated in a container, 

But I noticed that it is correclty displayed using WebIQ Preview but Once I publish it to the target, in a webBrower, the Backround is no more loaded (example below), I'm using WebIQ 2.9, is it normal ?

The Image was put in the AppData folder : C:\Users\userName\AppData\Roaming\webiq-designer\workspace\pics\custom\Background

Thanks.

 

[webiq-eg]

Hello, it should normally work like this. Is there a problem with the browser cache? Please try to clear the cache. Please also see whether the background image is available in the published version of the HMI.
I wish you success
webiq-eg

[Yacine]

Hello, I cleared the cache of my browsers many times,(computer, Tablet, ) but it is background is not updated. For my point of view, the image is not published to the runtime as we are only able to see it with the preview (image copied only in the appdata folder), how can we check if the image is published in the ctrlx WebIQ runtime ? Thanks.

[GB_]

Hello, 

i have the same problem.

Anyone had found a solution?

Thanks you very much

[GB_ · Accepted solution]

I have solved the problem, you don't have to point at c:/.... but at HTTP://192.168.1.1:10123/..... you can see the right path ispectioning the web page.

[HmiGuide]

That's a very common failure. You always must use relativ pathes to the project directory. You even should not provide the URL in the path name. If you do that you must adapt it, when the IP address changes or you run the project on. When you use iq-image in WebIQ it automatically uses a relative path.

[webiq-sk]

Please note that you CANNOT use local file system paths as this instructs the browser to load the file from the viewer's disk! We're using web technology here and whatever you instruct the browser to use as a src will be honored - in this case when using a filesystem path (which would have to use file:/// syntax anyway) it would always refer to the browser side. That's how web technology works.

Always use relative paths as explained before.