Mac OS X and the php.ini upload limit
Finding and fixing php.ini upload limits on Mac OS X.
Last night I was messing round exporting a WordPress blog and importing it into WordPress on my own Mac so I can play around with the design.
The MacTips blog I exported has almost 900 posts (ie 900 Tips). The downloaded file was 2.1Mb. That’s not particularly large, but it was enough to cause a problem when I tried to import it into the blog I’d set up on my Mac.
Maria Langer and I wrote in Chapter 10 of WordPress 2 Visual Quickstart Guide about exporting and importing between blogs.
When I came to import that 2.1Mb file I received an error message: The uploaded file exceeds the upload_max_filesize directive in php.ini. That upload limit is set at 2Mb, so I needed to change it.
It seemed obvious that the file php.ini was the one to edit, but where and how? Some Googling brought me to Enabling PHP and Apache in Leopard by David Powers.
First I had to create php.ini by copying another file, then it was a simple matter to locate the 2Mb limit and change it. I changed it to 8Mb.
David’s instructions are clear and easy to follow. You need a decent text editor such as TextWrangler (free) or BBEdit, and to paste in a few lines of code in the Terminal.
After amending the upload limit I went to the Sharing System Preference, turned Web Sharing off and then on again. That done, the import went smoothly. Now I can experiment with blog designs, with real content, but without disrupting the public blog.
These posts might be related:
Upgrade WordPress Plugins Automatically
One of the challenges of keeping a WordPress blog running smoothly is making sure all installed plugins are updated promptly when new versions become available. WordPress 2.5 makes this easier than ever by adding an Automatic Upgrade feature.
As shown in the following illustration, the a note in the Plugin Management administration panel indicates that the Bad Behavior plugin (which I rely on to keep the spambots off my blogs) has been updated.
I have two options for bringing my blog up to date:
- Download version takes me to the Bad Behavior page on the WordPress.org’s Plugin Directory so I can read about and download the update. This functionality has been around for a while — at least since WordPress 2.3 — with all plugins that support it.
Upgrade automatically takes the update process a step further. When I click this link, WordPress automatically downloads, uncompresses and installs the new version of the plugin for me. It displays its progress as it works, as shown here, and confirms that the upgrade has been successful.
I’ve been using this new feature for a few weeks now and it’s worked like a charm. It’s a heck of a lot easier than upgrading the old fashioned way.
These posts might be related:
- Check your plugins when you upgrade WordPress
- Simple blog, simple update
- Upgrading to 2.1: Dealing with Plugin Compatibility
This blog now on WordPress 2.5
We’ve just updated this blog to the new WordPress 2.5. If you notice any quirks or see any problems, please let us know.
These posts might be related:
- No related posts
WordPress 2.5 Admin screens totally changed
·
After upgrading from WordPress 2.3.3 to 2.5 the first, most obvious difference is in the Dashboard. The screenshot on the left above is from my Oddity59 blog, not yet upgraded, while that on the right is from TiKouka.
The colour scheme has changed, information and links have been moved around, fonts reduced in size, and some previously ‘fixed’ items have been made mutable. Overall things seem slicker and sleeker, more efficient and more compact.
A nice touch is the summary of your blog — how many posts and pages and so on. Here’s what mine says right now:
You have 2,325 posts, 12 pages, 2 scheduled posts, contained within 34 categories and 558 tags.
You are using Neoclassical theme with 13 widgets. Change Theme This is WordPress version 2.5.
Immediately below that are lists of Recent Comments and Incoming Links.
Very obvious are the buttons to go straight to write a new Post or a new Page.
Changes continue through each individual Admin screen. New features include a Media Library that displays all the images and other media you’ve uploaded, and tells you which posts they’ve been used in.
WordPress 2.5 is a new version, rather than a minor point upgrade. If you’re not a confident WordPress user, I suggest you do some reading before you upgrade, and maybe watch the 4 minute screencast.
These posts might be related:
Make a Lasting Impression in WordPress
My most recent article about customising WordPress has appeared on the Peachpit site. It’s about editing the footer of your blog — Make a Lasting Impression:
The footer may be the last thing visitors see on your blog. It leaves a lasting impression, so you should use it well. In most themes, a separate file called footer.php contains this part of the site. In this article, you’ll learn how easy it is to edit the footer to display exactly the information you’d like your blog’s visitors to see.
[Via : Peachpit: Web Design Reference Guide > Customizing WordPress: Make a Lasting Impression.]
These posts might be related:
WordPress vs Safari: Mars Edit to the rescue.
I’ve been using Mars Edit since it was part of NetNewsWire. It’s an excellent, stand-alone editor for blog posts, with all kinds of cool features. So I wasn’t aware of the problems Safari users are having with WordPress.
While I sometimes use the web editor for my WordPress blogs, especially when I need to include an image from my online photo albums (MacTips screenshots, personal photos), I’ll always use Mars Edit when I can.
What’s more, I seldom use Safari; OmniWeb is my main browser of choice, though I also use Flock quite often for browsing.
WordPress and the web editor
If you do decide to write WordPress posts in your web browser, the first thing to do is turn off the stupid Visual Rich Editor, or you’re likely to go postal. Maria and I wrote about how to do this in our book WordPress 2 Visual Quickstart Guide. Look at pages 26 and 27 to get started.
I also avoid using Flock for writing posts as it seems to just mess up what I write, whatever I do. OmniWeb works nicely though. But the best choice of all is separate software, such as Mars Edit or Ecto. Daniel Jalkut, author of Mars Edit, explains more of the web editor problem, in The Broken Web Editor:
Recently there has been an increase of new MarsEdit buyers who cite as their motivation a frustration with the WordPress web editor. I respect and admire the WordPress team. In fact, their web interface is among the best out there. But even in the best of circumstances, it’s hard to compete with the usability of a desktop app. And when something goes bad, it becomes downright impossible.
Currently the situation is especially bad for people who use WordPress with Safari. For whatever reason these two pieces of software have fallen slightly out of accord. It’s common to hear tale of people who use Safari for “everything but WordPress.” In short, WordPress has a reputation for messing up or even eliminating parts of your post when using the web-based editor in Safari. I know, because I see the comments of my customers and would-be customers on the web. There is a chorus of confirmation for this problem.
I look forward to WordPress and Safari to ironing out their differences.
[Via Red Sweater Blog: The Broken Web Editor.]
Ways to solve the web editor problem
So, if you’re working with WordPress, which is, after all, about the best blogging platform, here are some steps to take to make the experience even better:
- if writing posts via the web interface, turn off the Visual Rich Editor, and use OmniWeb rather than Flock or Safari
- use Mars Edit instead of the web interface
- use some other stand-alone editor.
These posts might be related:
