Magazine Template Causing White Screen

Reports about issues that you encounter in Suffusion
Forum rules
1. No offensive language and no mocking
2. Please do a thorough search before you post something. Trust us, there is a high probability that the question you are asking has been asked previously.
3. No soliciting. You cannot post here soliciting bids for people offer you quotes, or even offer money to people for some work. You will be moderated if you do so. If you are looking for help, please post your request on http://jobs.wordpress.net or http://codepoet.com
4. Please be reasonable. You are getting software and support. For free. Complicated requests from a general purpose theme are not welcome and some volunteers might lose patience with you.
5. Please do your due diligence. If you posted a query and we answered with a link, take the trouble to go through the link contents.
6. Please post with complete information. Requests for help MUST be accompanied with your URL, particularly if you are asking something like "Why am I seeing a blank space?"
Post Reply
JasonSB
Posts: 11
Joined: 25 May 2010, 16:12

Magazine Template Causing White Screen

Post by JasonSB » 25 May 2010, 16:24

What I did:

1. created a page titled magazine with the magazine template chosen.
2. switched to a static page with the just created magazine page chosen.
3. checked the site.

What happened?
Completely white screen.

I checked the forum and the best idea I had was deleting the theme and reinstalling a fresh copy.

I tried:
1. Deleted the theme in the admin section.
2. redownloaded the theme via admin section.

What happened?
All the theme options were still there and when I tried the to setup the magazine layout I got the white screen again.

I tried:

I got into my files and deleted the theme directly. I then downloaded it again from the link on aquoids front page.. and ftp the file directly into the themes folder.

What happened?
Same thing.

I'm stumped and have been googling and searching for the answer to no avail.

sidenote.. where is the options being saved that when I delete the suffusion theme.. they seem to stick around for the reinstillation?
Site link:
http://storyballoon.org[currently turned off the static page causing the white so my readers aren't confused.]

User avatar
Connie
Posts: 1169
Joined: 10 Nov 2009, 04:53
Contact:

Re: Magazine Template Causing White Screen

Post by Connie » 25 May 2010, 23:11

sorry, if you deactivate what is causing the problem, we cannot check

please do this:

before you do the following steps:

re-activate the situation and validate the site with a HTML-validator.
I am sure there are some HTML-problems (not closed tags etc.)

after that:
do screenshots of your settings PLUS screenshots of the white screen
save the html sourcode

and give us a chance to study these infos!

good luck!

Connie

JasonSB
Posts: 11
Joined: 25 May 2010, 16:12

Re: Magazine Template Causing White Screen

Post by JasonSB » 26 May 2010, 05:31

I'm not sure what the html source code would be?

I did get rid of the white screen by deactivating the W3 Total Cache plugin. This left me with only the header fore/background images.

I was able to get it running with W3 Total Cache on a clean wordpress/suffusion install in a subdirectory with no validation errors at this url http://storyballoon.org/testsite/

If you're talking about the settings for the magazine template. I'm running the default settings. Same as the testsite that works.

This is what the validator says when W3 Total Cache is running with the magazine template as the static page:
Unable to Determine Parse Mode!

The validator can process documents either as XML (for document types such as XHTML, SVG, etc.) or SGML (for HTML 4.01 and prior versions). For this document, the information available was not sufficient to determine the parsing mode unambiguously, because:

the MIME Media Type (text/html) can be used for XML or SGML document types
No known Document Type could be detected
No XML declaration (e.g <?xml version="1.0"?>) could be found at the beginning of the document.
No XML namespace (e.g <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">) could be found at the root of the document.
As a default, the validator is falling back to SGML mode.

No Character encoding declared at document level


No character encoding information was found within the document, either in an HTML meta element or an XML declaration. It is often recommended to declare the character encoding in the document itself, especially if there is a chance that the document will be read from or saved to disk, CD, etc.

See this tutorial on character encoding for techniques and explanations.

↑ TOP

Validation Output: 1 Error

Line 1, Column 1: end of document in prolog ✉
This error may appear when the validator receives an empty document. Please make sure that the document you are uploading is not empty, and report any discrepancy.


This is the info for the site before magazine template with W3 Total Cache running:

Validation Output: 15 Errors

Line 69, Column 29: character "&amp;" is the first character of a delimiter but occurred as data
if ( scrollY > descripY && !fixedShare ) {

This message may appear in several cases:

You tried to include the "<" character in your page: you should escape it as "&lt;"
You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
Another possibility is that you forgot to close quotes in a previous tag.
Line 69, Column 30: character "&amp;" is the first character of a delimiter but occurred as data
if ( scrollY > descripY && !fixedShare ) {

This message may appear in several cases:

You tried to include the "<" character in your page: you should escape it as "&lt;"
You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
Another possibility is that you forgot to close quotes in a previous tag.
Line 77, Column 25: character "<" is the first character of a delimiter but occurred as data
} else if ( scrollY < descripY && fixedShare ) {

This message may appear in several cases:

You tried to include the "<" character in your page: you should escape it as "&lt;"
You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
Another possibility is that you forgot to close quotes in a previous tag.
Line 77, Column 36: character "&amp;" is the first character of a delimiter but occurred as data
} else if ( scrollY < descripY && fixedShare ) {

This message may appear in several cases:

You tried to include the "<" character in your page: you should escape it as "&lt;"
You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
Another possibility is that you forgot to close quotes in a previous tag.
Line 77, Column 37: character "&amp;" is the first character of a delimiter but occurred as data
} else if ( scrollY < descripY && fixedShare ) {

This message may appear in several cases:

You tried to include the "<" character in your page: you should escape it as "&lt;"
You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
Another possibility is that you forgot to close quotes in a previous tag.
Line 485, Column 5: end tag for "div" omitted, but OMITTAG NO was specified


You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 484, Column 4: start tag was here
<div id="container" class="fix">
Line 485, Column 5: end tag for "div" omitted, but OMITTAG NO was specified


You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 473, Column 5: start tag was here
<div id="wrapper" class="fix">
Line 485, Column 5: end tag for "div" omitted, but OMITTAG NO was specified


You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 472, Column 2: start tag was here
<div id="page" class="fix">
Line 485, Column 5: end tag for "body" omitted, but OMITTAG NO was specified


You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 457, Column 1: start tag was here
<body>
Line 485, Column 5: end tag for "html" omitted, but OMITTAG NO was specified


You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 2, Column 1: start tag was here
<html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en-US">
Line 69, Column 29: xmlParseEntityRef: no name
if ( scrollY > descripY && !fixedShare ) {

Line 69, Column 30: xmlParseEntityRef: no name
if ( scrollY > descripY && !fixedShare ) {

Line 77, Column 25: StartTag: invalid element name
} else if ( scrollY < descripY && fixedShare ) {

Line 77, Column 36: xmlParseEntityRef: no name
} else if ( scrollY < descripY && fixedShare ) {

Line 77, Column 37: xmlParseEntityRef: no name
} else if ( scrollY < descripY && fixedShare ) {

Line 485, Column 4: Premature end of data in tag div line 484


Line 485, Column 4: Premature end of data in tag div line 473


Line 485, Column 4: Premature end of data in tag div line 472


Line 485, Column 4: Premature end of data in tag body line 457


Line 485, Column 4: Premature end of data in tag html line 2


And here is the info when I run the magazine template without W3 Total Cache:

Validation Output: 30 Errors

Line 406, Column 429: there is no attribute "type"
…ullscreen" value="true" /><embed type="application/x-shockwave-flash" width="5…

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Line 406, Column 467: there is no attribute "width"
…"application/x-shockwave-flash" width="576" height="324" src="http://www.youtu…

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Line 406, Column 480: there is no attribute "height"
…x-shockwave-flash" width="576" height="324" src="http://www.youtube.com/v/y5p-…

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Line 406, Column 490: there is no attribute "src"
…e-flash" width="576" height="324" src="http://www.youtube.com/v/y5p-zgesoTY&am…

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Line 406, Column 574: there is no attribute "allowscriptaccess"
…n_US&amp;fs=1&amp;" allowscriptaccess="always" allowfullscreen="true"></embed>…

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Line 406, Column 599: there is no attribute "allowfullscreen"
…1&amp;" allowscriptaccess="always" allowfullscreen="true"></embed></object></p>

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Line 406, Column 605: element "embed" undefined
…1&amp;" allowscriptaccess="always" allowfullscreen="true"></embed></object></p>

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
Line 409, Column 124: there is no attribute "share_url"
…_share' type='button_count' share_url='http://storyballoon.org/tuscan-arizona-…

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Line 409, Column 526: there is no attribute "data-button-style"
…ogle.com/buzz/post" data-button-style="small-count" data-url="http://storyball…

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Line 409, Column 549: there is no attribute "data-url"
…a-button-style="small-count" data-url="http://storyballoon.org/tuscan-arizona-…

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Line 434, Column 32: document type does not allow element "script" here; assuming missing "caption" start-tag
<script type="text/javascript">

Line 442, Column 24: document type does not allow element "col" here
<col class='suf-tile'/>

The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

Line 443, Column 24: document type does not allow element "col" here
<col class='suf-tile'/>

The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

Line 444, Column 6: document type does not allow element "col" here
<col>

The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

Line 444, Column 7: end tag for "col" omitted, but OMITTAG NO was specified
<col>

You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 444, Column 2: start tag was here
<col>
Line 445, Column 4: document type does not allow element "tr" here
<tr>

The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

Line 478, Column 4: document type does not allow element "tr" here
<tr>

The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

Line 509, Column 4: document type does not allow element "tr" here
<tr>

The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

Line 540, Column 4: document type does not allow element "tr" here
<tr>

The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

Line 574, Column 4: document type does not allow element "tr" here
<tr>

The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

Line 607, Column 8: end tag for "caption" omitted, but OMITTAG NO was specified
</table>

You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 434, Column 2: start tag was here
<script type="text/javascript">
Line 607, Column 8: end tag for "table" which is not finished
</table>

Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

Line 637, Column 34: document type does not allow element "script" here; assuming missing "li" start-tag
<script type="text/javascript">

Line 645, Column 7: end tag for "li" omitted, but OMITTAG NO was specified
</ul>

You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 637, Column 4: start tag was here
<script type="text/javascript">
Line 647, Column 764: required attribute "alt" not specified
…ogo_small.png" title="NetworkedBlogs"/></a></div><div id="networkedblogs_nwidg…

The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Line 607, Column 8: Opening and ending tag mismatch: col line 444 and table
</table>

Line 612, Column 12: Opening and ending tag mismatch: table line 433 and div
</div><!-- content -->

Line 840, Column 7: Opening and ending tag mismatch: div line 379 and body
</body>

Line 841, Column 7: Opening and ending tag mismatch: body line 371 and html
</html>

Line 841, Column 7: Premature end of data in tag html line 2
</html>



BTW, I found where the suffusion options were being saved. it's in the wp_options

Post Reply