Archive for April, 2009
I just wanted to take a minute to highlight the fact that three WordPress related podcasts have all made it to their 50th episode in the last month.
The WordPress Podcast comes in first, releasing their fiftieth episode on March 2nd and it was entitled “WordPress 2.7.1 released, WordPress.tv, How much do YOU love WordPress?”
Charles Stricklin and Jonathan Bailey continue to bring out episodes of the WordPress related podcast that started it all. My favourite episodes will always be the ones that I was able to be on, as it was a real treat in my WordPress career to have been a temporary co-host, and even a guest co-host on the show.
The second one to make it to the big five-O was WordCast. On April 7th, the released “Our Semi-centennial!”. They had Lorelle VanFossen, Liz Strauss and Jonathan Bailey on the show to celebrate. I have yet to be invited as a guest on WordCast, and am shamed to admit that I don’t consistently listen to their great show, but they have a super strong, well deserved following even without me always listening in.
Lastly, on April 11th, Jeff Chandler and I released our episode, and while Jeff did give the episode a little bit of a special notice, the episode was more about our special guest, Cathy Perkins otherwise known as The WordPress Wizard and so the episode was named “Interview With Cathy Perkins”.
All three shows are continuing to bring information to the community in audio form, and all do it in their own special way. I am happy to see WordPress continue to bring people together beyond just using the same software. WordPress is a community.
Kudos to all those involved with these podcasts. I hope to see you all make it to 100 episodes strong and more.
Back, a long time ago, I remember a discussion surrounding Habari, and potentially using Trac as the way of organizing and overseeing the graphical concerns of the platform, much like they did the code, but quickly, they realized that graphics don’t always fit into a system like Trac.
Seems the same can’t be said for WordPress, as they look to allow the WordPress graphic design community a chance at submitting their work to the blogging platform.
From the WordPress blog:
First and most immediate is the creation of a new â€œcomponentâ€ in Trac for graphic design. Weâ€™ll use this component label to create tickets for things like making graphic buttons, such as making a new version of the favorites menu graphic or WordPress mark that looks better with the blue admin theme. In some cases graphic design tasks will overlap with CSS tasks, so designers interested in contributing can search for open tickets with either component label. In cases where a base PSD file is needed as a starting point, we will attach it to the ticket.
In this vein, if you notice a graphic that needs fixing (like the aforementioned favorites menu button needing a blue version), please use the graphic design component label to report it in Trac. Please donâ€™t create tickets for graphic you just donâ€™t likeâ€¦ keep it to things that look broken or overlooked.
What do you think? Will this be a success, or a misstep by the WordPress team?
As WordPress themes become more complex, they continue to add back-end features to their themes, but have to be judged on their front-end, as there is no easy way, that I know of, to lock down WordPress installations so that a back-end demo can be set up that won’t be “taken advantage of” by the darker people on the Internet.
This is a problem I’ve been having in marketing WPUnlimited, as I recently posted on the blog. I am trying to video all of the important features, but surely, there has to be some way of locking down WordPress, or showing a theme back end, without opening the door for all kinds of abuse. Anyone have any tips? Please let me know.
It has been a long while since I’ve covered Habari on this blog, and I am still interested in the developments of the blog platform. With the latest release, it doesn’t seem like they’ve put much “fanfare” into it, and here are some details from their dev blog.
We’re really happy to announce our 0.6 release, which brings in the Access Control List (ACL)-based permissions system we’ve been working so hard on, along with oh, about 1100 bug fixes and other improvements. See the release notes for details.
With the addition of the extensible ACL system, Habari is now ideal for creating a variety of websites. Whether a single blog or a corporate publishing hub, you have granular control over permissions for every author and visitor to the blog. You can decide who can modify what, and where. To show off the ACL system, we’ve included a new ‘private posts’ plugin that lets you limit the visibility of posts to a subset of registered users.
I think they need to work on their marketing text for releases, as the improvements are no small feat, and improve the software greatly. Check out Habari, if you are looking to try out a different blogging platform.
Often, an item comes up in the development mailing list, or elsewhere that should be addressed, but is told in a simple way that it won’t be changed. A great example of this is the post revisions issue. Many people, including myself, would like a simple user interface added to WordPress that allowed us to enable, disable, or set the number of saved revisions, but this idea has basically been closed on WordPress Trac without a fix.
Who decides what UI enhancements are worthwhile, and which ones are not? In a community project like WordPress, I would have liked a vote over such a thing, especially since there are multiple items in the WordPress administration panel, that probably don’t need to be there any longer.
Maybe it is time for WordPress and team to have a basic and advanced toggle for the UI, so that most options are hidden, unless an administrator otherwise needs them. Things like the post revisions selection and management could fall within the “advanced fine tuning options”.
What do you think? Has WordPress acted on all the community’s best needs and interests, or are they still missing crucial elements towards satisfying the die-hard WordPress user base? Let me know in the comments below.
Yesterday, Justin Shattuck sent out his first e-mail newsletter in a very long time, to let everyone know that an updated version of his popular Comment Relish plugin was out. The plugin allows you to set up an automated e-mail that gets sent out to first time commenters on your blog, enticing them to come back or subscribe to your RSS.
The newest release includes some obvious improvements over the previously neglected version uno and some major upgrades courtesy of Chris Bavota from tinkerpriestmedia.com. If you are currently using comment-relish and have not upgraded to WordPress 2.7 because of its hectic and horrible reaction to the new code, have no worries – you can now! However, if you are running WordPress 2.7 and you are upset that it was sending duplicate comments, endless comments to every commentor, or just flat-out broken – we fixed that too!
I am a huge fan of this plugin, and am going to be trying out version 2.0 as soon as I can.