I get the following message when going to my wiki home page using IE6 as a browser (but not in Opera or Mozilla...). If I refresh the screen it then loads.
What gives?
Thanks, David
____________________________________________
The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
The short answer seems to be to use the latest cvs source and disable compression (a new flag that was added). Here's the full post:
Problem with IE 6 when using PhpWiki 1.3.3
This is using PhpWiki 1.3.3 on a hosted isp account (the machine where I installed phpwiki is running FreeBSD release 4.7 with the latest PHP on latest 1.3.x apache). Problem that I was seeing on IE 6:
The XML page cannot be displayed Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later. Cannot have a DOCTYPE declaration outside of a prolog. Error processing resource 'http://lilly.csoft.net/~elev/elilev/phpwiki-1.3.3/'. Line 4, Position 11 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
^
So I took a look at index.php via Opera 7. At the top of the page, I saw: lib/Request.php:116: Warning[2]: ob_start(): output handler 'ob_gzhandler' cannot be used after 'URL-Rewriter' but Opera continued displaying the page.
I went to Request.php code and commented out the code as follows:
The problem is solved in terms of IE since its not seeing any bad html/xml. My question: Am I causing any potential functionality problems with phpwiki by commenting the above? --EliLev
answer from Jeff: Short answer: Leaving the compress_output() code commented out is fine.
Details:
The HTTP protocol allows for the transmission of web data in a compressed format (if both the web browser and web server support it.) That code attempts to get PHP to compress it's output (if PHP thinks the browser can handle it.)
If you comment the code out, the worst that happens is that the PHP output gets sent uncompressed. (It may well be that apache is compressing the output for you --- that may actually be the reason for the trouble --- in which case you lose nothing other than the time you've had to spend to figure this all out.)
Jeff
PS: The latest CVS code has a config define in index.php which controls when PhpWiki tries to compress it's own output. (So you only have to adjust the configuration instead of commenting out code...)
Commenting out that code solved another problem for me: Mozilla 1.3.1/Win, Mozilla Firebird/Win and IE5.5/Win produced a page full of rubbish (random characters etc.) when trying to open my Wiki. I guess those browsers couldn't handle the compression or so...
-- OnnoBroekmans
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I get the following message when going to my wiki home page using IE6 as a browser (but not in Opera or Mozilla...). If I refresh the screen it then loads.
What gives?
Thanks, David
____________________________________________
The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
--------------------------------------------------------------------------------
Cannot have a DOCTYPE declaration outside of a prolog. Error processing resource 'http://www.zygosis.co.uk/phpwiki/'. Line 4, Position 11
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
----------^
I have the same problem. http://sailesha.com
It's a real pain. The same version of phpwiki installed on a different server doesn't give me that error.
The short answer seems to be to use the latest cvs source and disable compression (a new flag that was added). Here's the full post:
Problem with IE 6 when using PhpWiki 1.3.3
This is using PhpWiki 1.3.3 on a hosted isp account (the machine where I installed phpwiki is running FreeBSD release 4.7 with the latest PHP on latest 1.3.x apache). Problem that I was seeing on IE 6:
The XML page cannot be displayed Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later. Cannot have a DOCTYPE declaration outside of a prolog. Error processing resource 'http://lilly.csoft.net/~elev/elilev/phpwiki-1.3.3/'. Line 4, Position 11 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
^
So I took a look at index.php via Opera 7. At the top of the page, I saw: lib/Request.php:116: Warning[2]: ob_start(): output handler 'ob_gzhandler' cannot be used after 'URL-Rewriter' but Opera continued displaying the page.
I went to Request.php code and commented out the code as follows:
function compress_output() {
// if (function_exists('ob_gzhandler')) { // ob_start('ob_gzhandler'); // $this->_is_compressing_output = true; // }
}
The problem is solved in terms of IE since its not seeing any bad html/xml. My question: Am I causing any potential functionality problems with phpwiki by commenting the above? --EliLev
answer from Jeff: Short answer: Leaving the compress_output() code commented out is fine.
Details:
The HTTP protocol allows for the transmission of web data in a compressed format (if both the web browser and web server support it.) That code attempts to get PHP to compress it's output (if PHP thinks the browser can handle it.)
If you comment the code out, the worst that happens is that the PHP output gets sent uncompressed. (It may well be that apache is compressing the output for you --- that may actually be the reason for the trouble --- in which case you lose nothing other than the time you've had to spend to figure this all out.)
Jeff
PS: The latest CVS code has a config define in index.php which controls when PhpWiki tries to compress it's own output. (So you only have to adjust the configuration instead of commenting out code...)
Commenting out that code solved another problem for me: Mozilla 1.3.1/Win, Mozilla Firebird/Win and IE5.5/Win produced a page full of rubbish (random characters etc.) when trying to open my Wiki. I guess those browsers couldn't handle the compression or so...
-- OnnoBroekmans