WordPress.org

Support

Support » How-To and Troubleshooting » [Resolved] WordPress site turns dark and unusable.

[Resolved] WordPress site turns dark and unusable.

  • Hi. My wordpress website http://www.mamamusicians.com turns darks whenever i click anywhere on the site.
    After that, my website becomes unusable and unclickable. I am quite new to
    Wordpress and I dont know what could be the problem. I tried deactivating
    The plug ins but it did not solve the problem. I am using theme customizrCan anyone help me please?
    Thank you.

Viewing 8 replies - 1 through 8 (of 8 total)
  • i looked at site,
    the black out occours as you stated but it only flasses on screen and then delivers the requested page.if you try deactivating your theme and just use wordpress 14, with none of your installed plugins activated, what do you get?

    deactivate plugins one at a time to discover the one that could be causing the conflict.

    i played with it a little more, I think the issue is in the slider, If when I am on home page and i click into another link blog, store, about, forum,…ect
    the pages load without a black shade overlay. try deactivating the slider first. see what happens,
    then I would install Revolution slider instead to see if the results are correct.

    Mark

    There is some fancybox code on the page that is causing the issue. Did you configure that yourself? It doesn’t seem like it’s needed on a lot of pages.

    another culperate is the S2member plugin, I would use woocommerce, and their subscriptions add in plugin instead of the FREE S2 plugin,

    here is the link:
    woocommerce is FREE, but to get service and updates you will need woocommerce subscriptions.
    you can have various memberships levels and charge or make them different just as products,

    http://www.woothemes.com/products/woocommerce-subscriptions/?utm_source=extension_home_page_banner&utm_medium=banner&utm_campaign=Banners

    The side widget with the scripting may need to be removed till the code is refined, as mentioned above.

    just disable the widget. see what happens.

    \rtf1\ansi\ansicpg1252 {\fonttbl\f0\fnil\fcharset0 CourierNewPSMT;} {\colortbl;\red255\green255\blue255;\red51\green51\blue51;\red255\green255\blue255;\red34\green34\blue34; } \deftab720 \itap1\trowd \taflags0 \trgaph108\trleft-108 \trbrdrt\brdrnil \trbrdrl\brdrnil \trbrdrt\brdrnil \trbrdrr\brdrnil \clvertalc \clshdrawnil \clwWidth13540\clftsWidth3 \clmart10 \clmarl10 \clmarb10 \clmarr10 \clbrdrt\brdrnil \clbrdrl\brdrnil \clbrdrb\brdrnil \clbrdrr\brdrnil \clpadt100 \clpadl100 \clpadb100 \clpadr100 \gaph\cellx8640 \pard\intbl\itap1\pardeftab720\sl300\partightenfactor0 \f0\fs24 \cf2 \cb3 \expnd0\expndtw0\kerning0 \outl0\strokewidth0 \strokec2 \uc0\u8234 \uc0\u8236 \ \uc0\u8236 \

    tried validating the code: errors
    Notes and Potential Issues

    The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation, or other things affecting the output below. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.
    Warning 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:

    in Direct Input mode, no MIME Media Type is served to the validator
    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.

    Info 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.

    Info Using Direct Input mode: UTF-8 character encoding assumed

    Unlike the “by URI” and “by File Upload” modes, the “Direct Input” mode of the validator provides validated content in the form of characters pasted or typed in the validator’s form field. This will automatically make the data UTF-8, and therefore the validator does not need to determine the character encoding of your document, and will ignore any charset information specified.

    If you notice a discrepancy in detected character encoding between the “Direct Input” mode and other validator modes, this is likely to be the reason. It is neither a bug in the validator, nor in your document.

    ↑ TOP

    Validation Output: 2 Errors

    Error Line 1, Column 1: character “{” not allowed in prolog
    {\rtf1\ansi\ansicpg1252 {\fonttbl\f0\fnil\fcharset0 CourierNewPSMT;} {\colortbl…

    Error Line 1, Column 688: end of document in prolog
    …w0\kerning0 \outl0\strokewidth0 \strokec2 \uc0\u8234 \uc0\u8236 \ \uc0\u8236 \

    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.

    tried validating the code: errors
    Notes and Potential Issues

    The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation, or other things affecting the output below. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.
    Warning 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:

    in Direct Input mode, no MIME Media Type is served to the validator
    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.

    Info 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.

    Info Using Direct Input mode: UTF-8 character encoding assumed

    Unlike the “by URI” and “by File Upload” modes, the “Direct Input” mode of the validator provides validated content in the form of characters pasted or typed in the validator’s form field. This will automatically make the data UTF-8, and therefore the validator does not need to determine the character encoding of your document, and will ignore any charset information specified.

    If you notice a discrepancy in detected character encoding between the “Direct Input” mode and other validator modes, this is likely to be the reason. It is neither a bug in the validator, nor in your document.

    ↑ TOP

    Validation Output: 2 Errors

    Error Line 1, Column 1: character “{” not allowed in prolog
    {\rtf1\ansi\ansicpg1252 {\fonttbl\f0\fnil\fcharset0 CourierNewPSMT;} {\colortbl…

    Error Line 1, Column 688: end of document in prolog
    …w0\kerning0 \outl0\strokewidth0 \strokec2 \uc0\u8234 \uc0\u8236 \ \uc0\u8236 \

    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.

    I finally found the culprit plugin. It was because of the plughin ‘Light-Responsive Lightbox’. After I deactivated it, everything became normal 😀
    Thank you guys. I appreciate your help.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘[Resolved] WordPress site turns dark and unusable.’ is closed to new replies.