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

    FastCGI and no directives in .htaccess.

    There is php.ini but that just has the magic_quotes_gpc = Off line, nothing else. I assume this was put there by my host as it was not there earlier.

    Thanks
      Argue for your limitations and they are yours!
      • 36416
      • 589 Posts
      Quote from: d3signr at Oct 19, 2011, 06:01 AM

      There is php.ini but that just has the magic_quotes_gpc = Off line, nothing else. I assume this was put there by my host as it was not there earlier.

      Rename it and your timezone problems are gone... wink
        • 28042 ☆ A M B ☆
        • 24,524 Posts
        The proper way to have custom php.ini files is to have a complete copy of the default php.ini file with your custom modifications, whether these be changes to the default settings or additional settings.

        One of these files needs to be in every directory that needs to use the custom directives. In the case of MODx, you would need one each for the two index.php files, as the rest of MODx is handled from those two files (the one in the root for the front-end and the one in /manager/ for the back-end); so you would need one in the web root directory (or the directory MODx is installed into) and one in the manager/ directory.

        In your case, the only .htaccess directive that may apply would be one that directs which PHP engine to use when handing off .php files for processing by the PHP engine; this is used mostly when various version of PHP are available.
          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
          • 36416
          • 589 Posts
          Quote from: sottwell at Oct 19, 2011, 10:19 AM
          The proper way to have custom php.ini files is to have a complete copy of the default php.ini file with your custom modifications, whether these be changes to the default settings or additional settings.

          Sure, very "proper" & practical on VPS with 50+ domains and various customer's websites demands. tongue

          PHPsuExec + CGI setup gives ability to just override global PHP settings in local php.ini three-liner, propagating those to whole domain. I intend to continue to use it that way...