Revision history for TruncatedPageWorkaround
Revision [19234]
Last edited on 2008-01-28 00:14:44 by JavaWoman [Modified links pointing to docs server]No Differences
Additions:
=====Truncated pages=====
===Symptoms===
Every page is truncated: the bottom of the page does not appear: the "small print" and maybe some elements above that like comments are not displayed in the browser.
If you look at the HTML source code in the browser, the page stops abruptly and the ending tags </body> and </html> are not there.
===Cause===
==Analysis==
Check if the host that Wikka is installed on is inserting banners in your pages. The way to check is to install plain HTML page (so Wikka can be avoided). Many free (and some very cheap) hosts insert a banner. If your host does indeed insert a banner, the workaround below can provide a solution.
==Technical explanation==
When a (free) host inserts a banner, it interferes with two things Wikka does by default:
~-when Gzip-encoding is active, inserting a banner just messes things up (causing the blank page); and
~-Wikka calculates content-length for a HTTP header - which will be incorrect after the banner is inserted, so you would see a **truncated page** when Gzip is not active.
===Applies to===
Any Wikka version.
===Solution===
See BlankPageWorkaround for a solution.
----
===Symptoms===
Every page is truncated: the bottom of the page does not appear: the "small print" and maybe some elements above that like comments are not displayed in the browser.
If you look at the HTML source code in the browser, the page stops abruptly and the ending tags </body> and </html> are not there.
===Cause===
==Analysis==
Check if the host that Wikka is installed on is inserting banners in your pages. The way to check is to install plain HTML page (so Wikka can be avoided). Many free (and some very cheap) hosts insert a banner. If your host does indeed insert a banner, the workaround below can provide a solution.
==Technical explanation==
When a (free) host inserts a banner, it interferes with two things Wikka does by default:
~-when Gzip-encoding is active, inserting a banner just messes things up (causing the blank page); and
~-Wikka calculates content-length for a HTTP header - which will be incorrect after the banner is inserted, so you would see a **truncated page** when Gzip is not active.
===Applies to===
Any Wikka version.
===Solution===
See BlankPageWorkaround for a solution.
----
Deletions:
===Symptoms===
Every page is truncated: the bottom of the page does not appear: the "small print" and maybe some elements above that like comments are not displayed in the browser.
If you look at the HTML source code in the browser, the page stops abruptly and the ending tags </body> and </html> are not there.
===Cause===
==Analysis==
Check if the host that Wikka is installed on is inserting banners in your pages. The way to check is to install plain HTML page (so Wikka can be avoided). Many free (and some very cheap) hosts insert a banner. If your host does indeed insert a banner, the workaround below can provide a solution.
==Technical explanation==
When a (free) host inserts a banner, it interferes with two things Wikka does by default:
~-when Gzip-encoding is active, inserting a banner just messes things up (causing the blank page); and
~-Wikka calculates content-length for a HTTP header - which will be incorrect after the banner is inserted, so you would see a **truncated page** when Gzip is not active.
===Applies to===
Any Wikka version.
===Solution===
See BlankPageWorkaround for a solution.
----
Additions:
=====Truncated pages=====
===Symptoms===
Every page is truncated: the bottom of the page does not appear: the "small print" and maybe some elements above that like comments are not displayed in the browser.
If you look at the HTML source code in the browser, the page stops abruptly and the ending tags </body> and </html> are not there.
===Cause===
==Analysis==
Check if the host that Wikka is installed on is inserting banners in your pages. The way to check is to install plain HTML page (so Wikka can be avoided). Many free (and some very cheap) hosts insert a banner. If your host does indeed insert a banner, the workaround below can provide a solution.
==Technical explanation==
When a (free) host inserts a banner, it interferes with two things Wikka does by default:
~-when Gzip-encoding is active, inserting a banner just messes things up (causing the blank page); and
~-Wikka calculates content-length for a HTTP header - which will be incorrect after the banner is inserted, so you would see a **truncated page** when Gzip is not active.
===Applies to===
Any Wikka version.
===Solution===
See BlankPageWorkaround for a solution.
----
===Symptoms===
Every page is truncated: the bottom of the page does not appear: the "small print" and maybe some elements above that like comments are not displayed in the browser.
If you look at the HTML source code in the browser, the page stops abruptly and the ending tags </body> and </html> are not there.
===Cause===
==Analysis==
Check if the host that Wikka is installed on is inserting banners in your pages. The way to check is to install plain HTML page (so Wikka can be avoided). Many free (and some very cheap) hosts insert a banner. If your host does indeed insert a banner, the workaround below can provide a solution.
==Technical explanation==
When a (free) host inserts a banner, it interferes with two things Wikka does by default:
~-when Gzip-encoding is active, inserting a banner just messes things up (causing the blank page); and
~-Wikka calculates content-length for a HTTP header - which will be incorrect after the banner is inserted, so you would see a **truncated page** when Gzip is not active.
===Applies to===
Any Wikka version.
===Solution===
See BlankPageWorkaround for a solution.
----
Deletions:
===Symptoms===
Every page is truncated: the bottom of the page does not appear: the "small print" and maybe some elements above that like comments are not displayed in the browser.
If you look at the HTML source code in the browser, the page stops abruptly and the ending tags </body> and </html> are not there.
===Cause===
==Analysis==
Check if the host that Wikka is installed on is inserting banners in your pages. The way to check is to install plain HTML page (so Wikka can be avoided). Many free (and some very cheap) hosts insert a banner. If your host does indeed insert a banner, the workaround below can provide a solution.
==Technical explanation==
When a (free) host inserts a banner, it interferes with two things Wikka does by default:
~-when Gzip-encoding is active, inserting a banner just messes things up (causing the blank page); and
~-Wikka calculates content-length for a HTTP header - which will be incorrect after the banner is inserted, so you would see a **truncated page** when Gzip is not active.
===Applies to===
Any Wikka version.
===Solution===
See BlankPageWorkaround for a solution.
----
Additions:
===Applies to===
Any Wikka version.
Any Wikka version.
Additions:
~-Wikka calculates content-length for a HTTP header - which will be incorrect after the banner is inserted, so you would see a **truncated page** when Gzip is not active.
Deletions:
Additions:
==Analysis==
Check if the host that Wikka is installed on is inserting banners in your pages. The way to check is to install plain HTML page (so Wikka can be avoided). Many free (and some very cheap) hosts insert a banner. If your host does indeed insert a banner, the workaround below can provide a solution.
==Technical explanation==
When a (free) host inserts a banner, it interferes with two things Wikka does by default:
~-when Gzip-encoding is active, inserting a banner just messes things up (causing the blank page); and
~-Wikka calculates content-length for a HTTP header - which will be incorrect after the banner is inserted, so you would see a truncated page when Gzip is not active.
===Solution===
Check if the host that Wikka is installed on is inserting banners in your pages. The way to check is to install plain HTML page (so Wikka can be avoided). Many free (and some very cheap) hosts insert a banner. If your host does indeed insert a banner, the workaround below can provide a solution.
==Technical explanation==
When a (free) host inserts a banner, it interferes with two things Wikka does by default:
~-when Gzip-encoding is active, inserting a banner just messes things up (causing the blank page); and
~-Wikka calculates content-length for a HTTP header - which will be incorrect after the banner is inserted, so you would see a truncated page when Gzip is not active.
===Solution===
Deletions:
===Workaround or Patch===
Additions:
=====Truncated pages=====
Every page is truncated: the bottom of the page does not appear: the "small print" and maybe some elements above that like comments are not displayed in the browser.
If you look at the HTML source code in the browser, the page stops abruptly and the ending tags </body> and </html> are not there.
//later//
See BlankPageWorkaround for a solution.
Every page is truncated: the bottom of the page does not appear: the "small print" and maybe some elements above that like comments are not displayed in the browser.
If you look at the HTML source code in the browser, the page stops abruptly and the ending tags </body> and </html> are not there.
//later//
See BlankPageWorkaround for a solution.
Deletions:
//This page is a **template** intended for documentation of **workarounds** for unusual Wikka problems. This page belongs to CategoryTemplate (which contains more handy templates). To create a Wikka **workaround** page, [[http://wikka.jsnx.com/WorkaroundTemplate/clone clone this page]] (most workaround page names end in 'Workaround' so it's useful to stick to that convention) and replace the title with a problem description (in a few words). Then remove this paragraph and provide actual page content in the outline below.//
