On March 26, 2019 we launched new MODX Forums. Please join us at the new MODX Community Forums.
Subscribe: RSS
  • For some really odd reasons, the resources in one particular section of my site would not save. Whenever I make an edit to a resource, it would stall for like a minute and then loaded up a blank page. I assume that it got time out. Nothing is save. I can't even delete the resource. It would also load up a blank page.

    I haven't ran into this problem in the past; therefore, I can't track down what is going on. I sat on this for three days and still can't figure out the issue. Have anyone ran into similar situation? Perhaps some permission issues?

    I am running MODX Evo 1.0.6.

    Thanks for your help.
    • Never had that b4, all I can come up with is problem with double alias names allthough doubt that one, or try database repair in phpmyadmin?
        Evolution user, I like the back-end speed and simplicity smiley
      • Yes, I did repair the database. I also cleared the cache, but haven't deleted the files in the cache. Is that save to do so?
        • No need for manual cleaning.
          When cleaning cache files like: docid_x.pageCache.php are deleted.

          /assets/cache needs these files:
          siteCache.idx.php
          sitePublishing.idx.php
          rss
          .gitignore


            Evolution user, I like the back-end speed and simplicity smiley
          • It's very possible that this is related to mod_security on the server: http://wiki.modxcms.com/index.php/What_is_mod_security_and_how_does_it_affect_me

            There can be words inside the text that will be filtered by mod_security before post and reject the post if it is there. Best case is to have it disabled if it is there.
              Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup magician. BlogTwitterLinkedInGitHub
            • +1

              If it's just a single Resource, it's almost certainly modx_security. If you're curious, you can delete paragraphs one at a time until it goes away and, once you find the paragraph, delete a sentence at a time, then words in the offending sentence. Sometimes it's a command word like Select or delete. Other times, it's just a word your host doesn't like casino or viagra.
                Did I help you? Buy me a beer
                Get my Book: MODX:The Official Guide
                MODX info for everyone: http://bobsguides.com/modx.html
                My MODX Extras
                Bob's Guides is now hosted at A2 MODX Hosting
              • I read recently someone concluded it was the word "Form" that blocked the user.
                  Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup magician. BlogTwitterLinkedInGitHub
                • Somebody else had a problem with the word "select".
                    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
                  • Thank you so much for your responses. Unfortunately turning on SecFilterEngine doesn't solve the problem. This is the error that I get after turning on SecFilterEngine

                    No data received
                    Unable to load the webpage because the server sent no data.
                    Here are some suggestions:
                    Reload this webpage later.
                    Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data.


                    I am not having a problem with just one resource, but all resources under one container (directory). I can't edit and can't delete any of those resources. It doesn't seem like saving gets input into the database. Please advise.

                    [ed. note: visualgui last edited this post 8 years, 7 months ago.]
                    • I figured out the cause. The template, let say "a," is longer working. When I created a new templete called "a-new", copy and paste the exact codes from "a" to "a-new," the resource saves fine when I switch to "a-new."

                      There's no different between the two other than their IDs. The codes are exactly the same. While changing to "a-new" works, I would prefer fixing "a" so that I don't have to change thousands of pages from "a" to "a-new."

                      Could someone advise on how to fix template "a"?

                      Thanks,