Tag Archives: Apache

Laravel Blank (White) Screen of Death on Mac OS X

Kept getting a blank screen / white screen of death upon copy-pasting a new Laravel project from a Windows machine to Mac OS X (Mavericks – PHP 5.4). Nothing helped. No errors were shown or logged. Whoops was not showing either. It was probably a permissions issue, but no debugging help.

Got to the bottom of the issue only after installing a fresh copy of Laravel 4.1:

This emitted the following error upon browsing project in the browser:

That was it: permissions issue!

So here is the solution: set permissions of all files and folders in app/storage. So, go to your project root from Terminal, and enter the following:

That’s it!
 

Unable to Upload Files into WordPress on Localhost – OS X Apache

Came across a very weird bug in WordPress 3.7.1, which was not letting me upload any image/file through the Media Uploader. It was constantly giving the following error:

  • I tried changing folder permissions to 777; error.
  • Tried changing folder owner to _www; error.
  • Tried changing folder group to _www; error.

None of these solutions worked.

I have a custom folder structure, where wp-content has been renamed to content. So I turned to wp-config.php file. This is how it looks like in my wp-config.php:

I tried changing the last line back to /wp-content/uploads (and renamed the folder), but still the same error! I was pulling my hair at this point!

Then I don’t know what occurred to me, and I commented out that last line. And voila! It worked!

Now I have no clue why explicitly defining the uploads folder was causing the issue, whereas on the WordPress Codex that’s exactly how the uploads folder – on a custom path – is supposed to be defined. Anyway, if anyone is having this issue in WordPress 3.7.x (or other versions), simply try removing this line from your wp-config.php file:

That’s all folks.

Local Websites in Apache after updating to OSX Mavericks 10.9

If after updating OS X to Mavericks, your local Apache setup stopped returning the websites that you had setup locally, then it’s highly likely that your httpd.conf has been overwritten. However, before it was overwritten the Mavericks setup created a backup of the httpd.conf file, httpd.conf.pre-update, in /private/etc/apache2/ folder. You can use diff tools to find out the difference between the new and old httpd.conf files. Most likely, the inclusion of httpd-vhost.conf file must have been commented out, so uncomment that (along with any other changes that you might have had in the older httpd.conf file).

Reference: Quick Tip: Getting Apache Up And Running After Updating To Osx Mavericks (10.9)

Subversion has a new home at Apache Software Foundation

Late last year (November 2009), the CollabNet sponsored open source version control system Subversion (SVN) was submitted to the Apache Incubator, in order to become part of the Apache Software Foundation. A press release was issued to this effect.

Subversion is now officially called Apache Subversion and has a new home address at http://subversion.apache.org/.

The old homepage of Subversion is showing the following message:

Subversion message on old homepage before moving to Apache 

It’s an exciting development for me, as I have recently become more interested in the whole Open Source lifecycle: the community, the forking, the contributions, and the learning. This submission, and consequently the acceptance, of Subversion into the folds of Apache Software Foundation is an important case in point of how open source softwares (will) continue to live and flourish.

Another feather in the cap of Apache Software Foundation in particular, and open source in general. Keep going!

Related reading elsewhere:

Subversion moving to the Apache Software Foundation