Did you make the same mistake I did, and update to Safari 4 when it was offered as a Software Update, then found some things didn't work any more, or you just plain don't like Safari 4? If so, here's how to revert back to Safari 3.2.3 on Mac OS X Leopard.
/Applications/Safari.app to the Trash, and rename the ~/Library/Safari folder (where ~ is your home folder, e.g. /Users/your-username) to something else (you're essentially making a backup here). It is important that you empty the Trash after doing this, as I found my 'new' Safari copied itself to my Trash folder.~/Library/Preferences/com.apple.Safari.plist and ~/Library/Preferences/com.apple.Safari.RSS.plist (if you have it - I didn't, but then I wasn't subscribed to any feeds) to something else (backups again - these files contain your bookmarks and RSS feeds so if you don't want to lose them, don't skip this step)/System/Library/Frameworks/WebKit.framework/Resources/Info.plist and replace all instances of the number 5530 with 5525. Please note: you may need to modify the file's permissions in order to be able to edit it. This can be done by right-clicking it, selecting Get Info, and modifying the permissions at the bottom - you need to give your username read and write access.There you go, just thought I would share :P
Edit: I have been asked for instructions for Mac OS X 10.4 (Tiger) - unfortunately, I don't have access to that version, but I'm told the instructions do work, except that the following modifications are to be made:
Tutorials. Everyone has them (ok, so not everyone. But a lot of people - even I had some... and for far too long, I might add). They bulk out the content of the average site and which makes the site look more important and useful and the site owner feels better about themselves, knowing they're helping people out.
The point of a tutorial is that it should help people out. It should take them through, step by step, instructions on how to perform a particular task which would otherwise be demanding and/or difficult. It should be clear, to the point, and easy to follow.
Let's take Jane Jones, a fictional website owner who loves writing tutorials. She writes them about anything and everything; Photoshop, HTML, CSS, JavaScript, PHP, you name it. She copied wrote all the iframe and blur effect tutorials first, dontchaknow. Anyway. Jane Jones comes across a script she likes - it takes text entered in a form and stores it in a database. She hasn't written a tutorial for at least a day now and she really loves this new script she's found, so she decides she'll write a tutorial for it.
She could start by writing about how the form could be extended - adding an extra field, for example. She could also write about how you can jazz up the layout a bit, for those who don't know how to do it. But this is all far too advanced for Jane... She starts with the traditional installation tutorial. "Create a database, see my other tutorial for details," writes Jane. "Then upload all the files. That's it!". Yay, one tutorial done. Second tutorial: "How to add text. To add text, write in the box and then press ok. That's it!". Next one: "How to delete text. To delete text, click the delete button. You're done!"
Let's say I'm using the script Jane has written the tutorial about. What have I learned here? I already know how to add text - it's fairly obvious, and anyone with half a brain would have guessed that you enter text in the box and then click the button. Even the most dim-witted person in the world would be able to guess that clicking 'delete' would, oh, I don't know, delete text?
So I ask you this: as a site owner, why are you writing that tutorial? Because you feel like sharing knowledge? Because you think that explaining the way you did something would help others? Or is it because you want more content? Or even because your hits are low and you want more on your site to keep them entertained?
Does your tutorial point out the obvious? Is it actually teaching anything? Writing a tutorial of the type Jane wrote above will insult the intelligence of your visitors. People will read it and wonder why you bothered writing it.
(And no, before anybody asks, this is not directed at anyone or any tutorial in particular. I see these sorts of tutorials all over the place and they do my head in.)
One of the questions I am asked most is "will you write a tutorial on how to install PHPAskIt?". My answer to this is always no because people need to learn to read. Included in the PHPAskIt zip file is a file called readme.txt. Now I don't know about you, but when I'm unsure of how to install something, the first thing I do is to look at the readme file (if there is one). When a file is called "READ ME" it usually signifies that it should be read, no?
So why am I bombarded time and time again with this question when I clearly explain how to install the script in the readme file? That, I cannot tell you. But what I do know is the internet population appears to be getting stupider. People use known insecure scripts such as Wak's Ask&Answer and CuteNews because "nothing's ever happened to me" and "I like that script"; people take images they have absolutely no permission to use (and they know this) and make website layouts out of them; and as Jem regularly points out with her Pants Awards, there is no shortage of people giving out stupid advice in the form of tutorials.
I came across a site the other day which combined the aforementioned issues. The site owner had been asked "please can you write a tutorial on how to install and use PHPAskIt" and had done just that. They wrote exactly what I wrote in the readme file, just worded slightly differently. I'd link the tutorial but the site's gone on hiatus (how convenient). What was the point of that? So imagine my delight when I found yet another one of these tutorials. I kid you not, this one is even worse than the other one, and assumes the visitor can't read or something (um, redundant much?).
The tutorial basically follows this format:
- Download the script!
- Upload everything then go to install.php! Yay! Done!
- It will say delete so and so files, delete these files: import directory, upgrade.php, install.php
PLEASE LINK ME IF YOU USED THIS TUT!1!!
"So and so files"?! So basically you're assuming your visitor hasn't read what's on their screen (it tells them which files to delete) or that the message is too confusing (um, you just wrote it out again, word for word. The point?) or something and that your tutorial is the answer to all that? Get over yourself.
Oh yes, and while I'm in a rant mood... I've noticed someone is commenting around the place using my URL. This person appears to go by the name of "Nancy" and uses my site (or the link to PHPAskIt) as their URL. Thanks for the extra hits and everything, "Nancy", but this site actually belongs to me and I'd appreciate it if you could stop doing that.
If you came here from one of "Nancy"'s comments, sorry to disappoint and all, but my name's Amelie and I've never heard of anyone called Nancy.
Pssst: If you have received a comment from "Nancy" using my details, please contact me as I'd love to see who on earth is doing this. :)