Here’s how to create a link to a stylesheet and set the media type to “print”:

$html->css(array('filename'), 'stylesheet', array('media' => 'print'));

That will output the following code:

<link href="/css/filename.css" rel="stylesheet" type="text/css" media="print" />

Hope that helps the next person trying to figure this one out.

Share This

1) Show Hidden Files. This is huge when you’re working with a website that requires the .htaccess file or editing system files without the Terminal. If I want to copy a folder or group of files while ignoring .DS_Store files and .svn (Subversion) files, the Finder is great. But .htaccess is going to be left behind too. Path Finder shows and hides system files with a simple “show invisibles” checkbox.

2) Those Relentless .DS_Store Files. Sure, they tell the finder what font size, color or format to show each unique finder window in, but come on… do we REALLY need this written in every folder the Finder touches whether we change the layout or not? I hate clutter. Even if it’s invisible clutter. Path Finder shows folders without adding a .DS_Store file to tell you it’s been there.

3) Compressing Folders. Have you ever opened one of those .zip files you’re sending your PC friends that you compressed from the Finder? They’re filled with all kinds of extra junk that you can’t see on a Mac, but confuses the hell out of someone on a PC who’s looking at two versions of every file in the folder (a hidden __MACOSX folder contains duplicates (0 or 1KB versions) of every file - most likely meta data about each file). Path Finder compresses folders without adding… whatever that is that the Finder adds.

4) Tabs. Tabs… hello, Apple? TABS!! They’re everywhere now. They should be on the Finder too. Even my toaster has tabs now.

5) Sort Folders First. If I had to choose one thing I miss from my days on Windows, it would be that the Windows Explorer always sorted folders first, and then files. I always found it hard to quickly find things in the Finder with folders and files all jumbled together (sorting by “Kind” fixes this… sort of). Path Finder brings that back, and it’s oh so nice.

Another nice feature (I could go on with 20 more of these, but I won’t) is something they call the “Drop Stack.” It’s a magical place where you can put files… almost like a little favorites drawer, to access quickly, or burn to a CD, without creating a folder on the Desktop for them.

So I suggest you check out Path Finder - it’s well worth the $35 you’ll shell out for it.

Share This

The PHP installation is missing some key extensions, like PostgreSQL support and the GD library to name a few. But the majority of commonly used extensions are ready to go. Marc Liyanage is already on the case and working out the kinks for his own installer including those additions. The only thing missing at this point is MySQL support for Leopard. As of this writing, there is no installer available yet.

The rest of this post assumes you are working from a clean install or an “archive and install” of 10.5. I’m not sure what the Apache configuration files may look like if you simply upgraded from 10.4 or 10.3 - if they are clean this should work just fine.

Open the Apache configuration file (I’m using TextMate, which is where the ‘mate’ command comes from):
$ mate /etc/apache2/httpd.conf
and scroll to line 114 - it should look like this:
#LoadModule php5_module libexec/apache2/libphp5.so
Just remove the comment:
LoadModule php5_module libexec/apache2/libphp5.so

To enable Virtual Hosts, uncomment line 461:
Include /private/etc/apache2/extra/httpd-vhosts.conf
and add your own directories in your /etc/apache2/users/you.conf file. Similar to the 10.4 configuration, change the first two lines (inside <Directory "/Users...>) like so:
Options All
AllowOverride All
and add your Virtual Host directives after that:

<VirtualHost *:80>
DocumentRoot /Users/yourname/Sites
ServerName localhost
</VirtualHost>

<VirtualHost *:80>
DocumentRoot /Users/yourname/Sites/devsite
ServerName devsite
</VirtualHost>

Restart Apache:
$ sudo apachectl restart
and you’re all set.

The only thing left to do is update your hosts file:
$ mate /etc/hosts
and add whatever you used for your ServerName after the other entries:
127.0.0.1 devsite

Enjoy!

Now I need to figure out if those rumors of Ruby on Rails out of the box are true…

Share This

Using a few built-in tools in OS X, I’ve found a great way to develop sites as Virtual Hosts on Apache. If you are a web developer working on a Mac and you need to develop sites using root relative paths without adding a base href tag to every page on your site, this tutorial should help tremendously. Here’s how it works:

First, make sure you’ve got PHP and MySQL installed - those are the only two things you should need to install outside of the stock OS X configuration.

Next, follow this tutorial on enabling mod_rewrite on OS X that I’ve written previously.

The rest will involve some basic command line use, but it’s pretty painless. As mentioned in the mod_rewrite tutorial, I highly recommend TextMate for editing the configuration files. If you’re a UNIX purist, there’s always vi.

For this example, create a new folder in your /Users/yourname/Sites folder called devsite and place some files there (a simple html or php file with something to output in a browser will do).

1. Open your httpd.conf file and enable Virtual Hosts:
   $ mate /etc/httpd/httpd.conf
   Around line 1063 (almost at the bottom of the file), you should find and uncomment this line:
   NameVirtualHost *:80
2. Open your users.conf file and add a Virtual Host directive:
   $ mate /etc/httpd/users/yourname.conf
   After the <Directory>...</Directory> portion, add the following:

   <VirtualHost *:80>
DocumentRoot /Users/yourname/Sites
ServerName localhost
</VirtualHost>

   <VirtualHost *:80>
DocumentRoot /Users/yourname/Sites/devsite
ServerName devsite
</VirtualHost>

   Keeping the localhost portion at the top will still allow you to view the root of the server and anything in it’s directory at http://localhost.

3. Open your hosts file and add your new site name to bypass DNS:
   $ mate /etc/hosts
   Make sure these three lines stay at the top:
   127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
   And add this line after it:
   127.0.0.1 devsite
4. Restart Apache
   $ sudo apachectl restart

You can now view your local files in your browser at http://devsite.

Let’s step back and look at what we’ve done and why this is so useful.

Most likely, until now, you were viewing local development sites by going to something like http://localhost/~yourname/devsite/fancy/url (or 127.0.0.1 instead of localhost) and doing anything with mod_rewrite meant lots of base href tags and RewriteBase configurations, which in turn meant lots of ../../ paths before your images or included scripts to make things work. Now, viewing the same files in your browser is as easy as http://devsite/fancy/url and all of your paths can begin with a single slash ( / ) meaning it will still work the same when you migrate your site to the live server. Root relative paths are a life saver - and this setup makes it possible.

It’s also useful for quick access to commonly used tools, like phpMyAdmin. What I’ve done is install phpMyAdmin in /Users/me/Sites/phpMyAdmin and set up a Virtual Host like this:

<VirtualHost *:80>
DocumentRoot /Users/me/Sites/phpMyAdmin
ServerName admin
</VirtualHost>

In the /etc/hosts file:
127.0.0.1 admin

And I can always get to my phpMyAdmin install by simply typing http://admin into the browser.

The reason http://admin works is because most operating systems (even Windows!) will look at the local hosts file first before requesting information from DNS servers. Apache is told to handle requests to http://admin through the Virtual Host we set up. And all of this is done without www’s or .com’s.

By now you should realize that you can add as many Virtual Hosts as you like for as many sites as you need. All you need is these three commands:
$ mate /etc/httpd/users/yourname.conf
$ mate /etc/hosts
$ sudo apachectl restart

This can also be done on Windows, but it takes a little more work, and would of course work the same as described above on Linux/UNIX. If anyone would find it useful, let me know and I’ll post a new tutorial on the same method for Windows developers.

Share This

Open the Terminal application (or, I much prefer iTerm) and type the following:
defaults write com.apple.finder AppleShowAllFiles TRUE
and after hitting return, follow it up with
killall Finder
which restarts the Finder and shows all files.

To revert back to hiding those files, simply run the same command above again but change TRUE to FALSE

Share This

To stop this behavior, you won’t find any preference in iTunes or iPhoto, where you would normally think to look. This little gem can be found in a separate application in your Applications folder called Image Capture.

Open Image Capture and go to the Preferences menu (under the Image Capture menu item). Under the General tab, change the option for “When a camera is connected…” to “No Application” instead of “iPhoto”.

This means you’ll have to manually start iPhoto when you connect your digital camera, but you won’t have to CLOSE iPhoto every time you plug in your iPhone (which, for me, is a heck of a lot more often than plugging in a camera!)

Share This

Options +FollowSymLinks
RewriteEngine on
RewriteCond %{HTTP_HOST} ^(.*)ablogapart.org [NC]
RewriteRule ^(.*)$ http://michaelkrol.com/$1 [R=301,L]

This reference was extremely helpful.

This RewriteRule lives in the .htaccess file at ablogapart.org and tells any request coming in to that domain to swap ablogapart.org out and replace it with michaelkrol.com. This includes ANYTHING after the trailing slash, like a direct link to a previous post. So http://ablogapart.org/this/direct/link gets sent properly to http://michaelkrol.com/this/direct/link

The important part is the [R=301] which sends a 301 (Permanent) Redirect header. That tells search engines that the page has moved permanently.

Just imagine what you’d have to go through setting up individual forwarding links…

Share This

Share This

The email instructions appear to be referencing a Plesk installation.

Here’s a copy of the email that was sent in case anyone else receives it:

Best Regards

Nettica Inc.

Share This

mysqldump -u username -p -h dbserver.host.com --compatible=mysql40 dbname > filetosave.sql

The --compatible command was added because the database server was running MySQL 4.1 and we needed the export for MySQL 4.0.

Share This