I.E. blocks scripts, etc.:: SOLVED
Posted: Wed Jun 22, 2011 11:42 pm
Hello,
I have set up TP with html to be viewed in web browser. Under folders I appear to have this set up properly because I am able to see my pages. Content is served via an internal web server.
The problem is that Internet Explorer pops up a message with every page stating that it has blocked Active X and scripts on this page.
I have tried setting the options in I.E. 9 under Security > Local Intranet to the lowest possible settings and still this message pops up.
I should add that I have added the site to the allowed list to no effect.
One more thing I noticed: the same page accessed directly through I.E., does not have this issue. It has something to do with the path through TextPad.
Does anyone know how to stop/fix this?
Windows 7 64 bit I.E. 9
SOLVED (I like to save bits):
Although I was able to view pages in the web browser with the settings I had put into TextPad, the setting pointed to what the Apache web server considered the root folder, to eliminate the problem I went up one level to the directory containing the root.
I have no idea why this works this way.
I have set up TP with html to be viewed in web browser. Under folders I appear to have this set up properly because I am able to see my pages. Content is served via an internal web server.
The problem is that Internet Explorer pops up a message with every page stating that it has blocked Active X and scripts on this page.
I have tried setting the options in I.E. 9 under Security > Local Intranet to the lowest possible settings and still this message pops up.
I should add that I have added the site to the allowed list to no effect.
One more thing I noticed: the same page accessed directly through I.E., does not have this issue. It has something to do with the path through TextPad.
Does anyone know how to stop/fix this?
Windows 7 64 bit I.E. 9
SOLVED (I like to save bits):
Although I was able to view pages in the web browser with the settings I had put into TextPad, the setting pointed to what the Apache web server considered the root folder, to eliminate the problem I went up one level to the directory containing the root.
I have no idea why this works this way.