What El Capitan Broke

Located in:

For my own memory, I'm listing things that upgrading to El Capitan broke in my dev environment. (All these were working before the upgrade.)

Apache

  • httpd.conf - I guess this file got reset in the upgrade so I had to reconfigure it to work again with my vhosts etc.
  • php version - The above reset also reset the php module used by Apache, so I needed to fish out the newer php version I had installed with Homebrew and tell Apache to use it. In httpd.conf:
    # Comment out original Apache conf line
    #LoadModule php5_module libexec/apache2/libphp5.so
    # Tell Apache to use the homebrew 5.6.17 version of php.
    LoadModule php5_module local/Cellar/php56/5.6.17/libexec/apache2/libphp5.so

MySQL by way of Drupal?

  • All my settings.php files needed to have the db host changed from localhost to 127.0.0.1. Not sure why this should break, but whatever - changing to 127.0.0.1 worked.

I will likely come across other weird behaviour that I'll have to fix, but suffice it to say, the main headache was having my various Apache customisations blown away and then having to figure out what to do all over again.

Ruby, Compass, Bundler

(Discovered this several days after original blog posting)

  • Needed to update/reinstall Ruby brew install ruby
  • Then ran sudo gem install compass
  • sudo gem install bundler
  • bundle install
0
No votes yet
Your rating: None

Social mediatize it!

Twitter Twitter Facebook Facebook     
How about that! I'm a Drupal association member.

Attention IE user!

It turns out you are using an outdated browser and my site might look a bit weird for you. (images are off colour, text gets cut off, layout is wacky) This is because your browser does not implement web standards. Please consider an upgrade.

Alternatively, you can try other browsers like Google Chrome, Mozilla Firefox, Opera or Apple's Safari. Every web developer on the planet will thank you! (and that's not really an exaggeration)

Hide this notice for the rest of your visit