Well, when the site loads, it automatically loads the 3 files (topo.php, and paginas.php rodape.php).
I have some links set to open pages or external images by SB, but when I click on any of these links it results in an error page.
Details of the errors of the Web page
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2;. NET CLR 2.0.50727;. NET CLR 3.5.30729;. NET CLR 3.0.30729; Media Center PC 6.0; InfoPath .2)
Stamp Date / Time: Tue, 19 Jan 2010 17:52:17 UTC
Of course, this error happens only in IE8.
Interestingly, ran the file topo.php separately and worked without problems now when he is running the 3 pages together it does not work and reports the error. Have any other browser it runs the 3 pages together and SB works normally.
I think it is something very simple and nothing wrong with "DOCTYPE html ....." file and so on, I think in my case is up to something silly, because running topo.php file separately, it worked normal.
Can anyone help me solve this problem? I will be very grateful.
I look carefully.
And your setup is concatenating three doctypes and three heads and everything else into one Page which is absolutely wrong. I'd place a sure bet if i'd say that this is the source of your problems.
Install Firefox with Html Validator -Addon (at least) and have a look at your page source. You'll wonder how many errors it will list.
Quote from bash #4753
<xterm> The problem with America is stupidity. I'm not saying there should be a capital punishment for stupidity, but why don't we just take the safety labels off of everything and let the problem solve itself?
Archetrix Dear friend, thank you for your attention in answer to my question.
I removed the Head's and other unnecessary items that were not also
necessary and my "DOCTYPE ..." did not understand where you said you were wrong
Well removed all you got to be pointed and convinced that this would be the same
error, but unfortunately the time to test IE8 showed the same error. I am now
install Firefox as you recommended and even try to find a solution.
Do you by chance have any other possible solution to my problem?
In IE6 standard mode an invalid argument can occur due to a haslayout error, as described on the website:
http://reference.sitepoint.com/css/haslayout IE6 mysteriously thinks that some elements should not be displayed and doesn't calculate offset-height.
as a result the height of other elements is calculated to a negative value, which results into this error.
This problem still occurs in shadowbox 3.0b and shadowbox 3.02
To solve this you need to make some changes to the shadowbox.css, this will trigger IE6 to give the elements a layout.