We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 28719
    • 2 Posts
    Hi Guys,

    First of all I’d like to say MODx is a fantastic tool and really impressed with everything I’ve seen thus far. However I seem to have some issue related to cache and hoped someone may be able to help.

    MODx Revolution 2.0.7-pl (traditional)
    Linux linweb12.atlas.pipex.net 2.6.18-194.17.4.el5
    mysql 5.1.47, pdo installed
    php 5.2.6 CGI/Fast CGI
    Used multiple browsers (Safari, Chrome, FF, IE)
    Site is about a month old and prior to today seemed bug free.

    The background -
    Made some changes to pages within the last 24-48hrs which published OK.

    Checked this morning, site had reverted to previous versions of pages. The new pages could be viewed in the resource content of the manager but the old pages appeared in the live site. Any changes made to existing or new pages would not publish to the site, the manager was running very slow and some of the manager pages were blank whilst emptying the site cache failed.

    On IE, Chrome & Firefox I was getting this error, which appears to have come up elsewhere from googling -

    Message: ’dom’ is null or not an object
    Line: 7
    Char: 136438
    Code: 0
    URI: sitename/manager/assets/ext3/ext-all.js

    Anyway after a couple of hours of searching for a solution it seemed to resolve itself despite me making no system changes?! Errors are gone and everything seems OK and bug free again. Would be good to understand what’s gone wrong in the meantime - for future use - any ideas would be greatly appreciated!

    Thanks very much,

    Stuart
      • 3749
      • 24,544 Posts
      I believe there were some issues with cache corruption that were fixed in 2.0.8. When clearing the cache doesn’t work, you can delete all the files in the core/cache directory manually and get a fresh start. I find that clearing the cache in the Manager still fails occasionally in 2.0.8 on my platform (XAMPP).
        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
        • 22303 MODX Staff
        • 10,725 Posts
        Quote from: BobRay at Mar 25, 2011, 12:02 AM

        I believe there were some issues with cache corruption that were fixed in 2.0.8. When clearing the cache doesn’t work, you can delete all the files in the core/cache directory manually and get a fresh start. I find that clearing the cache in the Manager still fails occasionally in 2.0.8 on my platform (XAMPP).
        FWIW, it does not fail actually—the console just fails to report the logged updates.
          • 3749
          • 24,544 Posts
          Quote from: OpenGeek at Mar 25, 2011, 09:56 AM

          Quote from: BobRay at Mar 25, 2011, 12:02 AM

          I believe there were some issues with cache corruption that were fixed in 2.0.8. When clearing the cache doesn’t work, you can delete all the files in the core/cache directory manually and get a fresh start. I find that clearing the cache in the Manager still fails occasionally in 2.0.8 on my platform (XAMPP).
          FWIW, it does not fail actually—the console just fails to report the logged updates.

          The last time I looked, the files were still there in the cache dir. when the console came up blank, though that was before 2.0.8 so it may have changed.
            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
            • 28719
            • 2 Posts
            Thanks for the posts guys, I’ll keep it all on in mind for any potential future issues, site’s been fine since this anyway...