We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 3749
    • 24,544 Posts
    Most of these are not in the System Settings table but they are available with [[++setting_name]] in Revo.

    Is there a name for them? I don’t much like "pseudo system settings" but can’t think of anything else. Or are they just system settings that don’t appear in the default grid?

    Site url: [[++site_url]]<br />
    Base Path: [[++base_path]]<br />
    Base URL: [[++base_url]]<br />
    Core path: [[++core_path]]<br />
    Manager Path:  [[++manager_path]]<br />
    Manager URL: [[++manager_url]]<br />
    Processors path: [[++processors_path]]<br />
    Assets path: [[++assets_path]]<br />
    Connectors path: [[++connectors_path]]<br />
    Connectors URL: [[++connectors_url]]<br />
    URL Scheme: [[++url_scheme]]<br />
    HTTP Host: [[++http_host]]<br />
    Cache Disabled: [[++cache_disabled]]<br />


    I’m not sure what to say about the user adding them to the settings grid and changing them, because doing so with some of them could cause serious problems, but Shaun’s context tutorial suggests adding some of them. Could I get a list of ones that can be safely modified? Is it correct that if they are in the grid, they’ll override the ones set in the config file?


    This one isn’t available with a setting tag, but maybe it should be:

    Server Port: [[++server_port]]<br />

      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
    • They are just configuration settings; like all system, context, and user settings. MODx uses some automatic calculations to determine these particular settings automatically, and if you add them to system settings, you will be basically overriding that automatically-determined value. We just need to better document all possible core settings so it’s clear the presence or absence of those settings in the database can affect behavior in certain cases. There are several session-related settings that are the same way, allowing you to fallback to the php session settings unless you add the setting to the database to override the behavior. In many cases, this is the only way to make it easy and allow customization for when the default behavior is not appropriate or fails for some reason in a particular environment.

      IMO, server_port should never be used; it will be a part of http_host if needed. IOW, if the server_port is 80 or the server port is configured to the SSL port (usually 443, but not always), it should not be used and will not be part of http_host, but if the value is a different port, it has to be used and will be a part of http_host.
        • 3749
        • 24,544 Posts
        Quote from: OpenGeek at Mar 13, 2010, 02:21 PM

        IMO, server_port should never be used; it will be a part of http_host if needed. IOW, if the server_port is 80 or the server port is configured to the SSL port (usually 443, but not always), it should not be used and will not be part of http_host, but if the value is a different port, it has to be used and will be a part of http_host.

        I was just thinking of having [[++server_port]] always report the actual port number so a user might do something like this:
        [[++server_port:is=`80`:then=`[[$someChunk]]`else=``]]


        It’s blank on my localhost install.

          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
        • Quote from: BobRay at Mar 13, 2010, 06:23 PM

          Quote from: OpenGeek at Mar 13, 2010, 02:21 PM

          IMO, server_port should never be used; it will be a part of http_host if needed. IOW, if the server_port is 80 or the server port is configured to the SSL port (usually 443, but not always), it should not be used and will not be part of http_host, but if the value is a different port, it has to be used and will be a part of http_host.

          I was just thinking of having [[++server_port]] always report the actual port number so a user might do something like this:
          [[++server_port:is=`80`:then=`[[$someChunk]]`else=``]]


          It’s blank on my localhost install.
          Right, it’s not set, and could easily be added. However, you can also get it from the $_SERVER global easily enough. If we feel it’s useful though, add a ticket to create this new pseudo setting. tongue
            • 3749
            • 24,544 Posts
            Quote from: OpenGeek at Mar 13, 2010, 10:02 PM

            If we feel it’s useful though, add a ticket to create this new pseudo setting. tongue

            Done. http://svn.modxcms.com/jira/browse/MODX-1755
              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