We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
MODX Community Forums Archive

[SOLVED] strange cache issue after 2.11 upgrade

    • 31088
    • 14 Posts
    unsub Reply #1, 15 years, 3 months ago
    Hello,
    Cpanel system, shared hosting, fastCGI, php5.2.1.4
    MODx 2.11

    Upgraded by overwriting / merging all distro folders and running setup.

    Worked on localhost (XAMPP, php 5.3) but the following hitches on the above system:


    • Wayfinder didn’t work, trying to re-intall kept saying it couldn’t overwrite URI blah blah, but seemed to complete anyway.
    • Package manager won’t download anything. Just sits there, not downloading. Won’t say why. Like a grumpy girlfriend, won’t explain what the problem is, but clearly there’s a problem.
    • When I try to clear the cache, I get a lot of this:
    Resource URI already exists for resource id = 1; skipping duplicate resource URI for resource id = 10
Resource URI already exists for resource id = 1; skipping duplicate resource URI for resource id = 7
Resource URI already exists for resource id = 1; skipping duplicate resource URI for resource id = 17
Resource URI already exists for resource id = 1; skipping duplicate resource URI for resource id = 9
Resource URI already exists for resource id = 1; skipping duplicate resource URI for resource id = 19
Resource URI already exists for resource id = 1; skipping duplicate resource URI for resource id = 18
Resource URI already exists for resource id = 1; skipping duplicate resource URI for resource id = 4
Resource URI already exists for resource id = 1; skipping duplicate resource URI for resource id = 8
Resource URI already exists for resource id = 1; skipping duplicate resource URI for resource id = 12
Resource URI already exists for resource id = 1; skipping duplicate resource URI for resource id = 21
Resource URI already exists for resource id = 1; skipping duplicate resource URI for resource id = 3
Resource URI already exists for resource id = 1; skipping duplicate resource URI for resource id = 11
Resource URI already exists for resource id = 1; skipping duplicate resource URI for resource id = 20

      What I did to get Wayfinder to work (I’m in a hurry, I’ll fix it later.) is to open up every resource mentioned each time I try to clear cache (in the above case it was `1`, then it went to `7`, etc...) and un-check "cacheable" and save, move on to next. Then clear cache. Then re-install wayfinder. Now nave menu on front=end works again.

      I suspect that this has some thing to do with folder / file permissions on the server.... but I really can’t find any consistent and complete info on what should and should not be writeable for MODx.

      So... anyone? Am I too retarded for the Revolution?
      • 24068
      • 4 Posts
      pureppl Reply #2, 15 years, 3 months ago
      Maybe "delete everything in modx/core/cache/" does the trick. Same directory must be writeable.
        • 31088
        • 14 Posts
        unsub Reply #3, 15 years, 3 months ago
        Quote from: pureppl at Jun 02, 2011, 07:44 PM

        Maybe "delete everything in modx/core/cache/" does the trick. Same directory must be writeable.
        I thought so too, but unfortunately it didn’t make any difference. I find that really surprising, I must say.
        thanks, though.
          • 3749
          • 24,544 Posts
          BobRay Reply #4, 15 years, 3 months ago
          You probably did this, but if not, clear your browser cache and cookies.
            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
            • 31088
            • 14 Posts
            unsub Reply #5, 15 years, 3 months ago
            yeah, I did. Actually, another problem I’ve just noticed, I can’t create or edit elements. None of my edits take. If I edit, save, and reload a chunk, for instance, my edits are gone and it’s back to the way it was before the edit. huh so confused.
              • 3749
              • 24,544 Posts
              BobRay Reply #6, 15 years, 3 months ago
              You did run Setup after installing the new files, right?
                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
                • 31088
                • 14 Posts
                unsub Reply #7, 15 years, 3 months ago
                yes, always.
                All steps from the wiki.
                I am nearly positive this has to do with file / folder permissions, but I have been unable to find any definitive source for what exactly needs to be writeable, etc.
                  • 31088
                  • 14 Posts
                  unsub Reply #8, 15 years, 3 months ago
                  I don’t really care about the cache stuff now; all I want is to be able to create and edit elements...

                  I can edit a couple of them, but not others. There is no common thread that I can detect.

                  I never, ever should have upgraded, it was working. Slowly, but working. I’m an idiot.
                    • 3749
                    • 24,544 Posts
                    BobRay Reply #9, 15 years, 3 months ago
                    When you can save some elements but not others, mod_security is always the chief suspect.

                    Google MODX mod_security
                      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
                      • 31088
                      • 14 Posts
                      unsub Reply #10, 15 years, 3 months ago
                      I put 
                      <IfModule mod_security.c>
   # Turn off mod_security filtering.
   SecFilterEngine Off
</IfModule>
                      in my htaccess.
                      It doesn’t do anything.
                      ( yes, cleared browswer cache, cleared everything, just in case. )
                      I don’t think mod_security is actually there, without the If it throws a 500 error.

                      Ok, one more thing: When I click save on most existing, or any attempted new elements, I get the "Saving..." notifier, but never the "saved" on at the top.