We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 36811
    • 5 Posts
    I don't know how this happened i've been adding documents on my cms install [running a 2.2.2-pl] halfway though modx seemed to slow down. then after i finished working on my documents. now when i try to view the document resource the whole pages goes blank
    I've attached a screenshot of what is being displayed every time i try to open a document resource.

    I installed batcher ver 1.1.1 after installing it this started to pop-up on my browser.

    I hope someone can tell me what to do to fix this.
    • What happens if you remove Batcher?
        Studying MODX in the desert - http://sottwell.com
        Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
        Join the Slack Community - http://modx.org
        • 36811
        • 5 Posts
        Same thing happens when I remove batcher.
        For now I found a workaround to it. For some reason changing the documents template fixes the problem. And the document resource thats affected where the ones using minishop2.

        I used batcher to change the document templates. But I still dont have a clue what cuased it.
        • Well, something was crashing your browser. Could be a corrupted string somewhere; character set conflicts perhaps. I always use the [[++modx_charset]] tag whenever the character set is indicated in a template's HTML. When MODx generates a page, it sends the HTTP headers to the server using that system setting. If you have a different charset in the meta tags in your HTML template, you will at least get a complaint from the W3C validator. But I don't know if it would cause any other problems; this is just a thought.
            Studying MODX in the desert - http://sottwell.com
            Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
            Join the Slack Community - http://modx.org
            • 36811
            • 5 Posts
            I found the cause it was the values my TVs was adding to the template. i was using the wrong input type. it should have been "number" but i used "._number" and caused all sorts of problems.