Posted on September 13th, 2007 in OS X | 52 Comments »
Every time I plugged in my iPhone, it had this nasty habit of opening iPhoto for me. Not because it wanted to drive me to drink, but because iPhoto is set to open any time a digital camera is connected to my computer - which, technically, an iPhone is.
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
When moving our site from ablogapart.org to michaelkrol.com, this handy little bit helped move our entire website with four lines of code:
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
Well, virtually, that is. If you’ve found yourself here after going to ablogapart.org, fear not - you’re in the right place. It was time to bring some focus - to who this is and why I’m doing this - and start adding some meaningful posts. The important ones have been migrated over to the new site, while others weren’t quite relevant enough to carry on. More helpful info on the way…
Share This
This morning I received an email hoax purporting to be from Nettica, our DNS provider. Details aren’t clear yet on what it’s intent was (the attached file was encrypted, which we’re working on decrypting), but I’ll post an update as soon as we figure it out. We’re working with Nettica Support to find out what’s going on.
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:
Dear Nettica Inc. valued MembersRegarding our new security regulations, as a part of our yearly maintenance we have provided a security guard script in the attachment.So, to secure your websites, please use the attached file and (for UNIX/Linux Based servers) upload the file “safeguard.php” in: “./public_html” or (for Windows Based servers) in: “./wwwroot” in your site.If you do not know how to use it, you can use the following instruction:For Unix/Linux or Windows based websites that use PHP/CGI/PERL/ASP:
1) Download the attachment named “safeguard.php”
2) Login to your site Control panel.
3) Open “File Manager” window.
4) Go through “Public_html” or “htdocs” (for UNIX/Linux Based servers), but for Windows Based server, please Go through “wwwroot” directory.
5) Choose “Upload Files”
6) Upload the file “safeguard.php”
7) Check its URL too “http://www.yoursite.com/safeguard.php”, if it is okThank you for using our services and products. We look forward to providing you with a unique and high quality service.
Best Regards
Nettica Inc.
[UPDATE] Nettica has added a post about this
on their blog as well.
Share This
I needed to export a MySQL database that was on a different server than the web server and was bound and determined to do it without going through the hassle of installing phpMyAdmin (port 3306 was blocked as well, so I couldn’t use any GUI tools either). The trick was adding the -h option. Here’s the command line that made some magic:
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