View secured content when using HTTPS

Suite and Optimus Suite 5
#1

Hi,

We are having problems with secured content when using https (the same problems as viewtopic.php?f=3&t=14477)

That is we get this security warning when opening a specific node in the 3rd level of the tree, so ONLY SOME NODES produce the problem.

We use dhtmlxtree (dhtmlxSuite v25 pro 91111) and IE (both IE7 (7.0.5730.13) and IE8 (8.0.6001.18702)). It does not happen in Chrome (1.4.1.0).
We use methods setImagePath,setSkin,enableCheckBoxes,enableSmartRendering and loadXML.
We load the WHOLE TREE AT ONCE and only use attr id and text in the xml (so NO IMAGES).

It does NOT happen if SMARTRENDERING is DISABLED.

I used fiddler to see which traffic (urls or images) is going back and forth but none cause its all client side without image attr.

Is there a solution for this problem?

#2

Hi,

In IE dynamic setting of background images can cause this issue. This is a known bug.

Unfortunately there isn’t a workaround for tree.

You may try to use treegrid with smart rendering instead of tree. In treegrid this problem won’t occur:

dhtmlx.com/docs/products/dht … _srnd.html

#3

Thank you for the answer…but I think that my problem differs from the other thread in that the warning only popups when opening a specific node in the tree. I think namely that the necessary background images (like lines etc) are already loaded at that time.

I produce the problem as follows:
i open Root 2…nothing happens

I open Item 1…the warning popups

but i cant produce the problem as follows:
i open Root 2 AND Root 1…nothing happens

I open Item 1…nothing happens

So if i open Root 1 first the warning on Item 1 does not popup? That is why i dont see dynamic setting of background images (like lines etc) can cause this issue…

Hope my problem is clear enough.

Thank you,
Filip

#4

Hi,

we reproduced this issue before and tried to find the workaround for it. But unfortunately we haven’t succeeded.

i dont see dynamic setting of background images

there could not be any other reason for this problem.

#5

Any updates on this topic ?
Anybody solved ?

#6

You may try to disable tree lines:

tree.enableTreeLines(false);

Hope, it’ll solve the problem.