Pashua for mac os x full#
Pashua for mac os x windows#

Maybe you can come up with a different workflow that can provide the data from a source that can be automated without user interaction. In most cases, when you believe you need to prompt the user for, well, anything, you should take that moment to re-think your workflow. User input also requires validating and checking user entered data. User interaction slows down the process as the script is waiting for the user to confirm or enter data. In nearly all cases, we want the automation to happen “magically” in the background, without any user interaction. You immediately reduce the workload, but also reduce the potential for someone to make a mistake, which would mean even more work later.

Pashua for mac os x full#

However, if as you say, you want to log to a file, you uncomment by removing the leading semi colon to make error_log = php_errors.log become error_log = php_errors.log or using a full path to place it where you want.As MacAdmins our goal is to automate workflows when ever possible.

Pashua for mac os x windows#

If you want to log to the syslog (or Windows Event Log on Windows) then error_log = syslog should become error_log = syslog Log errors to syslog (Event Log on Windows). PHP's default behavior is to leave this value Then, in this section: Log errors to specified file. Log_errors = On (this will turn the logging engine on) now edit /etc/php.ini - you want to make sure the following lines (NOT the same line starting with a semi-colon ' ') are exactly as follows: Typing this: php -ini at the prompt should report this: Configuration File (php.ini) Path: /etc then you will see if you run php -ini again that it now sees your new file: Type: $ sudo cp /etc/ /etc/php.ini (and enter your password) You need to copy that file to the name php expects so that you can edit it, like this: this is because in /etc there is a file called /etc/ as an example and to show it is not in use. ini files in: /Library/Server/Web/Config/php Run php -ini at the prompt by typing it and pressing enter On OSX/MacOS do the following in a Terminal window: I made my changes to the php.ini file that was listed there, restarted apache, and re-ran the web page the new edits were shown there. Because I was interested in what the web server was using I knew that I should use the path returned from the web-page results. (the '2>&1' and 'grep' elements just restrict the output of the command to useful information, i.e. You can find all the possible php.ini files using this:įind / -name php.ini 2>&1 | grep -v 'denied' | grep -v 'directory' If you are interested in what PHP is being used by the web server, only use the information gathered from a web page that uses the 'phpinfo()' function.įor example, on my system the versions reported by the two different methods were:įor the php.ini file path things were different, too:

If you have a system that has multiple PHP installations (like mine did) the results you get from using the command line tools MAY BE different than what is actually used by the web server. This is rather old thread, but I would like to add a further clarification.