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

Answered site_start updated but not outputting the correct value

    • 37031
    • 93 Posts
    Jeff Miranda Reply #1, 8 years, 2 months ago
    I've never encountered this before but I've updated the site_start value in system settings to be 12 but when I view the output on a dummy page using [[++site_start]] it outputs one.

    I've turned off Friendly URLs, I don't have any overriding context settings, and other settings like site_url work properly. Does anybody have any suggestions?

    Thanks!

    Jeff
    MODX v2.4.2

    This question has been answered by jeffmiranda. See the first response.

      • 37031
      • 93 Posts
      Jeff Miranda Reply #2, 8 years, 2 months ago
      I also checked the DB and the value is set to 12.
        • 3749
        • 24,544 Posts
        BobRay Reply #3, 8 years, 2 months ago
        Delete all files in the core/cache directory.

        Also, make sure Resource 12 is published and not protected by security rules. Otherwise, you'll get sent to the page designated by the error_page System Setting (which is probably page 1).
          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
        • discuss.answer
          • 37031
          • 93 Posts
          Jeff Miranda Reply #4, 8 years, 2 months ago
          Thanks for the reply Bob! It turns out that it was a context setting. I recently installed MODXStart (https://modx.com/extras/package/modxstart) and the package creates site_start under the Web context. That's fine and all but when I went to view the context settings for the Web context, nothing was loading in the grid so I assumed that it didn't have any overriding settings.

          I suspect that the grid didn't load—and this is me guessing—because I had to turn off compress_js. Ever since then, the manager has been working, but it's just a bit "finicky". I'll reload the manager page and the finickiness will be gone.

          I know this is now off topic of the thread but I had to turn compress_js off because it was spiking my server CPU memory. I would hit 1GB of virtual memory and then the server would error 500 on me. I turned compress_js off and it stopped. Do you (or anyone) know why this would happen?
            • 3749
            • 24,544 Posts
            BobRay Reply #5, 8 years, 2 months ago
            I'm glad you got it sorted. Both compress_js and compress_css should be turned off, imo. They don't really speed things up and they often cause trouble.
              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