“Out of memory” error with Adobe InDesign CS6 and El Capitan

A user who upgraded to El Capitan but still uses Adobe InDesign CS6 was getting an error about InDesign being "out of memory." I did some Googling and came across this fix.

Application Frame was already disabled under the window, so the user didn't have to do that, but "trashing" (really renaming to com.adobe.InDesign.plist.bak when InDesign is closed) the ~/Library/Preferences/com.adobe.InDesign.plist file seems to have fixed the issue.


Cloning an image using Thunderbolt and Disk Utility (post–El Capitan)

I have a longer post on this, including why you would want to clone using Thunderbolt and Disk Utility, but Apple decided to switch up Disk Utility's interface completely in El Capitan (10.11). Even though the process is similar, the exact steps are different.

One procedural difference worth noting: In Yosemite (10.10), Mavericks (10.9), etc., you would select the source, and then select what you wanted to restore the source to. In El Capitan (10.11) and supposedly beyond, you start by selecting the destination, and then select what source you want to restore from.

diskutilityrestoreelcapitan01 Open up Disk Utility (from /Applications/Utilities). Select the disk you want to restore to. And then select Edit > Restore.

diskutilityrestoreelcapitan02 You have the option to restore from another disk (if you have a computer connected via Thunderbolt, it should show up in the drop-down list) or to restore from a disk image (click Image... to find the image you want to restore from), and then click Restore.

diskutilityrestoreelcapitan03 Wait for it to restore.

diskutilityrestoreelcapitan04 Click Done when it's done restoring.


Fixing Apache after upgrading to El Capitan

I'm not sure how many people are running Apache on non-server Mac OS X, but if you are and upgrade from Yosemite to El Capitan, you'll get some breakage. The breakage won't be as bad as upgrading from 10.10.4 to 10.10.5 was.

Apache generally will still work (as in the server will server up files that can be visited in a web browser). You'll just have to edit the httpd.conf file to get some other things working.

Paste this command into the terminal to edit the httpd.conf file:

sudo nano -B /etc/apache2/httpd.conf
and go ahead and uncomment (remove the # sign from the beginning of the line) from LoadModule php5_module libexec/apache2/ to get PHP working again (handy if you're using something like MunkiReport).

While you're in there, if you're using SSL, you may also want to uncomment these three lines (you may have to search for them using Control-W):

  • Include /private/etc/apache2/extra/httpd-ssl.conf
  • LoadModule ssl_module libexec/apache2/
  • LoadModule socache_shmcb_module libexec/apache2/

Once you're done, run a

sudo apachectl -t
to make sure your syntax is okay, and you didn't accidentally type anything else while uncommenting. If that's good, go ahead and restart the Apache service:
sudo apachectl restart


Installing rEFInd on Mac OS X El Capitan

If you're using rEFInd on a Mac (for example, if you're dual-booting or triple-booting with a Linux OS), you may have found rEFInd worked fine with Yosemite but broke with El Capitan.

This guide worked for me to get it going again:
Installing rEFInd on Mac OS X El Capitan.