Tag Archives: wordpress

A fork of the Recent Photos widget by Asad Iqbal for WordPress

September 19th, 2012

I’ve been planning on figuring out a simple way to show the latest photo from my mobile photos category on the sidebar of my site for a while. Today I did a quick search for a plugin that would simply add a widget that I could drag/drop into place to do exactly that.

I came across the Recent Photos widget by Asad Iqbal. Asad hasn’t updated the plugin in a little while so it didn’t work for me out of the box. I also made a few slight revisions for my use (mostly removing a bunch of inline HTML). I’ve created a fork in a Gist of the widget and I plan on making a few more revisions. Feel free to use the code or fork it yourself if you find it useful.

Complexity and control, simplicity and peace of mind »

August 26th, 2012

Justin Blanton, in a piece only a veteran-nerd-blogger-type like myself could enjoy all the way through, is dancing on two directions to take his blogging technology. On the one hand, he’d like to stop worrying about the entire stack and just get down to writing. On the other hand, he wants to be up to his ears in control but he’ll have to manage every last bit.

The simple solution:

Ideally, I think Squarespace is where I’d like to end up, because it would offer me the most peace of mind. I’d never have to worry about upgrading or maintaining anything.

And, the solution that offers control:

Moreover, to publish a new post I simply create a new file, supply the relevant YAML Front Matter, write the post, save the file, and execute rake deploy and rake generate. Those commands cause Octopress to re-build (on my personal machine) the site’s pages and upload them to the server.

“Simply.” Sure.

Every blogger that’s been doing this awhile has had a similar struggle. Probably more than once. Before WordPress came along I had my own blogging platform that I built in ASP. Then I had one in PHP. And since switching to WordPress (when it was still called b2) I’ve dabbled, installed, imported using just about every service/script imaginable – including the two Justin is playing with right now.

As a writer you’ll want to play around with new tools. Shake things up and find some sort of writing zen to get back into the groove. But the technology doesn’t matter to anyone except the person(s) maintaining the site. If Justin wants a suggestion I’d suggest that rather than switching CMSs to use a different text editor to write his posts. Rather than MarsEdit, use nvAlt (it is what I generally use). Or any of the dozens of good editors for the Mac. It will shake things up for you creatively while not taking up your waking moments worrying about switching.

Blogging is a simple medium – whatever you choose to use is typically good enough. WordPress is now more powerful than it needs to be for blogging. So this can get daunting. But, at the end of the day, we’re serving up blog posts. Install WordPress. Install a caching plugin. And that is all you will ever need as a blogger.

Oh, and Justin, you’re a huge nerd. We love you.

Why the WordPress theme customizer matters »

July 24th, 2012

Andy Adams of The Theme Foundry:

I’d like to suggest that competitors like Squarespace are going to start eating WordPress’s lunch on the “ease of use” front if WordPress does not adapt.

Adams goes on to say how important the theme customizer is to helping WordPress to keep its competition at bay.

Remember, Matt Mullenweg said that they are focused on “radically simplifying what we currently do”. This is key for WordPress to continue to be the platform of choice for so many sites. There are much easier solutions out there – though arguably more or less powerful – but WordPress really could use a major (radical as Matt put it) rethink because the years of adding features have made it much more complex than its newest competition.

The Theme Foundry’s themes all support WordPress’s new theme customizer

June 18th, 2012

The Theme Foundry, who is arguably doing the best work in professional WordPress theming, just announced that all of their themes already support WordPress 3.4′s new theme customizer.

We’ve been keeping an eye on WordPress 3.4, and now that it is released we’re proud to announce that our 4 most recent themes (PortfolioChalkDuet, and Anthem) support the theme customizer for all theme options.

This is what it means to be on top of things. To be doing great work. Watching your area of expertise and being ready for what is next. An awesome example to everyone.

Matt Mullenweg on a much more simple WordPress

May 25th, 2012

First, yes please.

Now, Matt Mullenweg on what tablets should mean to WordPress:

How we democratize publishing on that sort of platform will not and should not work like WordPress’ current dashboard does. It’s not a matter of a responsive stylesheet or incremental UX improvements, it’s re-imagining and radically simplifying what we currently do, thinking outside the box of wp-admin.

I’m sort of disappointed that WordPress used to set the trends and now it simply reacts to them. However, I’m very happy that the most influential person in the WordPress world is now focusing on making it easier to publish from something other than the typical computer set up.

I can publish to my blog using my iPhone or iPad. But it is painful when compared to publishing from my Macbook Pro.

How do blogs need to evolve?

March 16th, 2012

This is a subject that is near and dear to me. It is a bit cliché to say this but I’ve been blogging since before it was a common verb. I’ve watched, very closely, as the blogging world has evolved over the last decade and even took some small part in that evolution.

It wasn’t that long ago that I wrote that I thought that blogs were ripe for disruption. And I still think we’re on the cusp of that. Or, perhaps, it is happening right in front of my eyes and I am simply not noticing it.

In a recent discussion between Anil Dash and a few other veterans of blogging Anil mentioned that even something as simple as a status update or tweet could be considered blogging. Although Twitter is rarely referred to this way today it was, at its inception, called a microblogging service. So maybe blogging has already evolved and we just haven’t noticed. The frog in the boiling pot comes to mind.

Although the conversation seemed to focus a lot on commenting I would have liked to have seen much more discussion around the topic of ownership. Some of the participants felt that ownership was important. Others not as much. If you look at how the party split it was split between the platform-builders and service-builders. Ev and Meg built services (Blogger, Kinja, Twitter) while Anil worked on a platform (Movable Type). I think there was much more to say on this topic.

Meg Hourihan on ownership:

But I’m not convinced people view what they’re doing [on social networks] as producing content, nor thinking it’s something they should own, anymore than I want to “own” my phone call with a friend. (Sure I don’t want someone to record it and sell it, but that’s different.) My call is ephemeral, and it’s about conversation and communication, not content.

While Meg believes that she’s seeing the world as it is I think she’s really just identified the problem with these social networks. Twitter and Facebook have permenant URLs for every single tweet and status update that people post. Those links are not ephemeral as Meg describes. She may feel as though they are because Twitter doesn’t give you access to your entire stream but – in reality – these tweets do not go away.

And that’s where Anil nails it.

So that point is very, very interesting, Meg: What if the phone company gave you free unlimited phone calls but they could record, monitor and sell your phone calls and information about what you said on them.

I do agree so much of why people don’t value ownership in social media is that they see it as conversation, not content, but that’s often because we don’t *know* in advance when it becomes meaningful.

In other words, people are viewing Twitter and Facebook as conversation platforms more than they view them as publishing platforms. Facebook and Twitter are finding value in what we all consider to be valueless conversation. They are making money based on what we are saying, what we’re interested in, and what is happening in the world. If they find value in our “content” why don’t we? And, if they treat this information as permanent why aren’t we?

Back to the evolution of blogs. I don’t think there is much argument about whether or not Twitter and Facebook can be considered blogging platforms. So we should lump them into the conversation of how blogs need to evolve. Which brings us full circle back to ownership. I think that people should own their own content. And they should know, up front, that they will own the content if they use a particular service or choose to host it themselves. It shouldn’t matter. They should also feel as though the content they post to any service is to be considered permanent – not a phone call that is soon forgotten.

I don’t think that a blog needs to run on software that you install on your own server in order for you to feel as though you own the content. WordPress.com and WordPress.org are nearly identical services with the same import and export capabilities yet one is a service and the other a platform. So you can use either of these products and feel pretty confident that you own the content and that the information you post there is permanent.

So how does this particular aspect of blogging need to evolve? I think other services such as Tumblr, Twitter, Facebook, and (fill in the blank) should do a better job of making your content searchable and accessible (read: exportable into a readable format) right out of the box. Not hidden somewhere in a Mac-only application or three-levels-deep in an API doc. One click easy.

The next aspect of blogging that I believe needs to evolve is the reverse-chronological homepage. In May of 2011 I wrote:

I believe the blog format is ready for disruption. Perhaps there doesn’t need to be “the next” WordPress, Tumblr, or Blogger for this to happen. Maybe all we really need is a few pioneers to spearhead an effort to change the way blogs are laid-out on the screen. There are still so many problems to solve; how new readers and also long-time subscribers consume the stream of posts, how people identify with the content of the blog on the home page, how to see what the blog is all about, how to make money, how to share, and how interact and provide feedback on the content.

Imagine you landed on /blog/ here at my cdevroe.com URL. What you’d find there would be what the typical blog homepage looks like. Just a list of posts from newest to oldest. It’d be very difficult to find out what I blogged about based on only the last few posts. This is why I chose to put my about page front-and-center. I believe that is a better way to get to know me, what I’m up to, and what my blog is about.

I don’t think the blog format is broken but it is certainly stale. Someone needs to come along and give us a new way to look at things. And not just in a novel way like tiles or something else that is pretty and neat to look at – I’d like to see something that is valuable, makes it really easy to see what the blog is about, perhaps what is popular now, or what was at one time popular. I think of the currently most visited URLs here on this blog. They are not the most recent posts. Not by a long shot. My top URLs on this blog are a few links that I’ve posted in the past that have somehow found their way to the top of the search engine rankings. Would that be important to show on the homepage of a blog? Or, what about the fact that a few of my posts have had hundreds and hundreds of comments? Would that be important to show?

Sidebar “widgets” sprang up years ago as ways to solve some of these issues. Related posts, popular posts, most-used tags, and other widgets made it easier to discover content that has already been pushed off of the homepage. But I still think that someone, somewhere has an idea of how to fix these issues and that one day we’ll wake up and someone will have made something better.

One last issue that I would have liked to see discussed in regards to what aspect of blogs that may need to evolve would be the use of databases. This is a more technical topic than the others but many platforms and services suffer from downtime whenever a post goes viral or hits the mass media. This simply shouldn’t happen.

Each platform and service chooses to handle content management in their own unique ways. Blogger and Moveable Type, for instance, used to publish HTML files (I have no idea what they do nowadays) while WordPress opted to use a simple database to host the content and serve those pages dynamically. Each approach has their pros and cons. But one thing is certain – it is far easier to serve a static HTML file millions of times than it is to request content from a database millions of times. Today’s web is one where at any moment an URL could be plagued by millions of visitors. Modern day blogging platforms and services should take this into consideration regardless if it was manually installed or hosted.

Blogger, Tumblr, WordPress.com, Twitter, Facebook all have extremely capable infrastructures in place to handle these issues. With WordPress.org you’re on your own to setup WordPress properly to handle load. It has taken some heat for this and while the argument could be made that people that are installing software on their own server should know better – the argument could also be made that by simply pre-bundling one of the many caching plugins into the core codebase this issue would be all but solved.

Tons of traffic to any particular post shouldn’t be thought of as an edge case. If you’re a blogger it will happen. Even if you’ve been writing for 40 years and it has never happened to you. It will. You shouldn’t have to worry about whether or not your blogging product of choice will crumble under the pressure of today’s web. Ever.

I could go on about this topic all day. The rest of the discussion is fantastic and I suggest that anyone with even a passing curiosity about the world of blogging – where it has been and where it is going – should give it a read at your next opportunity.

WordPress Post formats Admin UI

October 27th, 2011

WordPress 3.1 exhibited an underlying feature that didn’t reveal itself in the UI in much of any way. Post formats. Post formats are sort of like categories of posts but are used to “handle” different post types in different ways. You can read more about Post formats over on the WordPress Codex.

Crowd Favorite has released an open source WordPress plugin * that changes the Admin UI and sets up standards for a few different post formats. Here, their description is better:

“The plugin is a completely additive solution that leverages the default WordPress functionality, while improving the UI and standardizing the names and presentation of custom fields that support the various post formats.”

Post formats has limitless possibilities as you extend WordPress from a simple blogging tool to a much more powerful CMS… but this plugin seems to focus on the modern day blogger.

This interests me in that I use categories to handle my different post formats. Which is how everyone that has ever used WordPress had to do it. I’ve got mobile photos, links, videos, and longer posts I call notes, and larger photos. It would be great to start using post formats to post different types of formats – I’m looking forward to digging into this.

* Side note: So glad Crowd Favorite switched to Github. I hope other WordPress developers quickly follow suit. In fact, I think WordPress.org should change the way they host WordPress plugins to git.

WordPress for iOS 2.9

September 26th, 2011

A very, very nice update of WordPress for iOS was been released. The application for iPhone and iPad now has a simple content editor and the QuickPhoto feature can now post images from your Library instead of going straight to the camera.

Although I wish the app supported Markdown format (rather than just HTML) I’ll take it.

Just in time for our trip to Ireland too.

Update: A small, yet very welcomed update, is that the Posts tab is now the default tab rather than the Comments tab. This makes things so much quicker. Again, a very, very nice update to WordPress for iOS.

The blog format is ready for disruption

May 16th, 2011

The recent chatter about pagination on blog home pages has reminded me of the days when blogging was just getting underway. Back then there were a few pioneers that were testing the waters, experimenting with the designs and layouts of their sites, constantly trying to find the right set of features that a blog needed.

And for the past few years I think this has settled down a little. The standards those few pioneers set in the beginning are still around. Most blogs today have a fairly similar feature-set and layout. Even when the layout is dramatically different than the status quo the feature-set is still just about the same.

I believe the blog format is ready for disruption. Perhaps there doesn’t need to be “the next” WordPress, Tumblr, or Blogger for this to happen. Maybe all we really need is a few pioneers to spearhead an effort to change the way blogs are laid-out on the screen. There are still so many problems to solve; how new readers and also long-time subscribers consume the stream of posts, how people identify with the content of the blog on the home page, how to see what the blog is all about, how to make money, how to share, and how interact and provide feedback on the content.

Several rather new trends are appearing in the pro blogosphere that started only a few years ago but are now becoming the new pro blog recipe. These trends simply weren’t there 7 or even 5 years ago. Disabling comments is seems to be the main dish (though 4 years ago it was debated). Having a podcast on-the-side is the side-dish. Add to that some sponsorship opportunities in RSS feeds, and a sprinkling of an ad network to taste, and you’ve got yourself the modern day pro blog recipe. Actually, all you really have is a direct mirror of what John Gruber has put together with Daring Fireball – but, nonetheless, these are the trends among pro bloggers and these must be taken into consideration when coming up with a brand new blog format that could set the trend for the next few years.

Syndication has also changed. It seems just yesterday that people thought full-content RSS feeds would destroy their ability to make money blogging. It turns out that could possibly be the most profitable part of their blog’s business model.

Having a Twitter account for your blog, or simply being selective with what is tweeted from your blog (which is my current model), is where things may very well be shifting. Today it would be unthinkable to see sponsored tweets in amongst the links to posts but give it a few years. Today’s Twitter feed is yesterday’s RSS feed. I imagine there will be sponsored tweets too and, in the near future, people will be just fine with that.

Exclusive, paid-for email newsletters had a spike earlier this year with a few services launching and some key figures in the industry taking a stab at them. I have no inside information on how those are turning out – but there is reason to believe that the blog could also do with some exclusive, paid-for content. It may not work for your blog about Hobbit-lore but perhaps it’d work for an incredibly good cooking, investing advice, design-and-code-tutorial, or architecture exam review blog.

Something I’ve always had issue with is that there aren’t enough “home pages” on blogs. That is why the home page for my site is my about page rather than a reverse chronological list of posts as most blogs are. I have that page too but people landing directly on cdevroe.com should not be introduced to my website by only seeing the latest few posts I’ve written. It wouldn’t be a very good introduction and, very well, may not even represent what my blog is about. Because this is a personal blog and not a blog about any one topic, the latest few blog posts would be a very bad representation about what this site really is – a personal blog.

Most blogs that try to earn a buck want to put as many clickable items on their home pages as possible. They probably feel that if they didn’t you’d never go anywhere besides the home page. I can say, after pouring over the stastics of my home page, that isn’t true. A fair percentage of the people that have come to my home page have stayed on that page for a few moments (presumably reading the page) and subsequently clicked on the blog or diet page(s), done a search, or gone to my Twitter account. All good things. I hope that someone solves this issue in a much better way than I have because I really do believe there is a lot of room for improvement here.

Advertising on blogs has simply never worked well. Yes, publishers have made money. Yes, advertisers have increased sales by purchasing ad space on blogs. However, for the core-subscribers to a blog the ads are just noise. Ad networks like The Deck do a very good job at striving to keep a higher quality product by controlling the ads and how they are displayed. But, arguably, even at that level of curation we still just end up with an ad in a sidebar on a blog. I wish there was a better answer for making content “free” to blog subscribers but – at present – advertising is our mule.

Some people claim the trackback is dead. I don’t believe that to be true. In fact, I rather like trackbacks. I like when blogs show me what others have written about a particular blog post. I like them even better than comments. Perhaps if blog software, and the theme of a blog, used the optional excerpt of the trackback standard better they’d work much more like comments (and be much more valueable) than they do now.

Reblogging, Retweeting, Sharing/Liking on Facebook, etc. are all ways to have a post be spread outside of a blog’s audience. The modern day word of mouth. There is no doubt that these tools work very well for some blogs while on others they do nothing. I have these options on my blog and, while I do get a few people using them per day, they serve little purpose then to remind people that if they’d like to share the post they can do it quickly and easily. But in reality, if a post is simply too good not to pass on it will be passed on whether you have a big Facebook button on your blog or not. These tools aren’t going anywhere in fact they are going to become even more ubiquitous – but it’d be nice if someone with an ounce of taste figured out a way to make these options pretty as well as easy to use and, as a hat-trick, much more valuable to all parties involved.

I know, I know, I’m going on and on about this but all of the above is just the tip of the iceberg as to why I believe that the blog format is ripe for someone to really begin innovating again. We have all of the tools and over a decade’s worth of content – all we need are some pioneers.

How I write on iPad

April 1st, 2011

I’m often asked how I write my posts on iPad. What applications do I use? Do I use an external keyboard? How do I get images onto iPad to include in posts?

All good questions. Here is how I write on iPad.

First, I use an application called iA Writer. This application gives me a distraction free writing environment that has just the right amount of features to make writing easy.

I do not use nor own an external keyboard for iPad. Never have. In fact, the on-screen keyboard in Writer has a custom keyboard with few shortcuts that I find very convenient.

I also edit within Writer. I read and re-read (unless I’m in a rush for some reason) the post until I’m happy with it. At this point there is no HTML, no links, no images, no videos in the post.

I then copy and paste the text from Writer into WordPress for iOS. I immediately save the post as a Draft (just in case). At this point I’ll either add the links, images, or video. If there is a lot of media to add to the post I may wait until I’m on my MacBook Pro to finish the rest. Sometimes adding a lot of HTML to a post using iPad can be cumbersome. I’m hoping that WordPress for iOS, at some point, adds a custom keyboard for written HTML quicker.

When the post is finished I’ll then schedule it to be published, usually sometime in the morning the next day since I typically write at night or very early in the morning. This gives the post time to stew a bit and gives me a chance to yank it if I end up not feeling good about the post. It also gives my blog a feeling of consistent publishing rather than a sporadic schedule.

And that is how this post was written.

WordPress for iOS 2.7.1. Two key updates.

March 25th, 2011

Even though there is yet to be an announcement on the WordPress for iOS blog, 2.7.1 has been released on the App Store and it comes with two key updates (at least from this blogger’s chair).

  • Photo and video uploads now work on iPad 2
  • Made the post status (such as “Draft”) more clear in the posts list

I use my iPad to write posts and, now that I have iPad 2, I hope to do it a lot more often while on the go. WordPress for iOS has been making very steady progress lately and this update is a very timely one.

Why are these updates key for me? Because iPad 2 would instantly crash when trying to add a photo to a blog post. I was able to work around it by using iPhone but it was pretty frustrating. Also, I write posts, save them as drafts, and then schedule them for publishing all from my iPad. This allows me to pick the time that a post gets published regardless of when I feel impelled to write it and also gives me time to edit them (which I did poorly on yesterday’s post). Being able to see which posts are in draft right in the posts list is a very welcomed update.

Thanks WordPress for iOS team.

How to test a WordPress Dashboard Widget

December 29th, 2010

I’m working on a relatively big update to Viddler’s WordPress plugin and something that doesn’t seem to be documented anywhere is how to test a Dashboard Widget if your plugin supports one.

It is fairly easy to add just a bit of code to make it pretty simple to test your widget. First, rather than only loading your WordPress Admin URL (ie. yoursite.com/wp-admin) you simply prepend the appropriate information to the end of the URL. Like this: yousite.com/wp-admin/index.php?page=viddler&noheader.

Then, somewhere within your plugin’s code, you add something like the following:
function viddler_page() {
if ( isset( $_GET['noheader'] ) )
return viddler_dashboard_content();
}

Obviously viddler_dashboard_content() is the function that I use to build the HTML for the Dashboard Widget. This will return the HTML you’re creating for your WordPress Admin Dashboard Widget sans JavaScript and CSS. But at least you’re able to test your output.

The GPL is a speed limit sign

July 16th, 2010

For those that haven’t already heard or read the transcript of Chris Pearson’s arguments against using the GPL I’ll sum it up for you. Chris has three main problems with the GPL. He didn’t itemize them very well on the podcast but this is what I was able to extract myself.

Chris feels…

  • as though the GPL is not conducive to good business practice,
  • that it is not an enforceable license,
  • and that Thesis, a WordPress theme and the main product of Chris’ company, somehow steps outside of the bounds of the GPL and so it shouldn’t apply.

Those three main arguments would be great to debate, to discuss and to figure out definitive answers to. However, the way Chris went about it – by simply not distributing his theme under the GPL – is definitely breaking the law.

It is sort of like speeding down a highway because you don’t agree with the speed limit in that area and your arguments are that speed limits aren’t good for highway safety, that there are no cops around to write out tickets and that you are somehow exempt from the speed limit laws because you’re a remarkable driver.

Bringing up problems with a license or even saying that a license doesn’t feel right and you’d like to discuss it at large is always a valuable thing to do. Deliberately distributing software without the GPL on top of software that is protected by it is not a valuable thing to do.

Is the GPL good for business? Is it enforceable? Is Thesis somehow exempt from the terms inside of the GPL due to its complexity? I don’t know the answers to those questions but it’d be fascinating to find out.

If this goes to court it would set a precedent but I hope it doesn’t for everyone involved.

From the NFL to WordPress themes

July 6th, 2010

Drew Strojny, former NFL player for the Eagles, Giants and Rams, had been moonlighting as a designer and open-source WordPress theme developer for years. The theme business, which is supported via support-membership-subscriptions (great business plan) is really taking off.  So much so that he and his wife are doing that full time via The Theme Foundry.

Recently Drew wrote up the backstory to how this all happened and it is a fantastic read.

Email comment replies to commenters using the CommentMailer plugin for WordPress

April 8th, 2010

Sorry for the long title but I’m guessing that this post will be found by people searching for this more than those of you that subscribe to my blog.

For a long time, actually ever since I got an email from Marisa McClellan stating that she replied to a comment I left on her blog, I’ve wanted to be able to reply to a comment on my blog and have it automatically sent to the person that I’m replying to via email without changing the workflow for me. In other words, I didn’t want to have to copy/paste my reply and email the commenter or reply to the default WordPress comment notification email. I wanted to simply click reply on the comment, type in my message, select who I would like to email (or not) and click send.

With CommentMailer I can do just that. Although it is only at version 0.1 (so it is a little bit rough) it works great and I am happy I can finally let people that are kind enough to comment on my blog know that I’ve replied via email.

Update: Prompted by Katy Widrick asking me, via Twitter, how to set up Comment Mailer I’ve decided to post my response email syntax here.

%previousmessage%

My reply:
%currentreply%

%signature%

%notes%

– end –

The %notes% keyword is the one that will ultimately put a link in the email back to the original blog post. It would be nice to have %link% available though.