Today I was listening to Talking Drupal #168. The topic was how to ensure that open source project developers can afford to provide updates to their users. As an open source developer myself, I have to disagree with the premise that we should support a distinction between users and developers. The projects that I develop for are the projects that I use. As a user-developer, I do not care how many users a project has. I care how many user-developers it has.

PATH is a variable that determines where the system looks for commands. Most guides I found suggest setting this in a Bash configuration file. But this only affects commands run in a Bash terminal. Global paths on macOS High Sierra are set in /etc/paths. You can also add a file to /etc/paths.d. Files in that directory have their paths included automatically.

When I was trying to get PHP session upload progress data from a site that uses a custom session handler, I learned that PHP stores the upload progress data using its built-in session handler before it runs any code. This means the upload data is not included when the site starts the session with its custom handler. However, I learned that it is possible to retrieve data from a session, abort it, and start another session with a different session handler.

After some hard-coded links stopped working when I moved a site to a subdirectory, I wondered why Drupal doesn’t use a <base> tag and relative paths for URLs. According to a 2007 article by Barry Jaspan, the <base> tag was removed in version 4.7 for reasons he did not know.

I was used to flushing memcached by connecting with telnet and issuing the flush_all command. Today I found that the telnet command has been removed from macOS High Sierra. Netcat works just as well for sending text over a TCP connection and is available on High Sierra.

Found an article that provides essential information not found in PECL installation messages: https://arcadian83.livejournal.com/16386.html. The key is that the php.ini path has to be added to both PEAR and PECL.

System Integrity Protection on OS X El Capitan makes it a challenge to install software that was easy to install on previous Mac OS X versions. I just found a simple, clear guide to installing PEAR on OS X 10.11 El Capitan. Now I can run PEAR and PECL to install PHP extensions.

This afternoon, most of the sites running on my computer started responding with “500 Internal Server Error”. The Apache error log showed the following error:

[Tue Jul 19 16:17:01.418642 2016] [core:alert] [pid 79692] [client 127.0.0.1:53041] /Users/darren/.htaccess: <IfModule not allowed here

composer require is the command to add packages to a composer project. Dreamhost shared hosting kills this command for using too much memory. To install new packages on Dreamhost shared hosting,