I live by console.app now; it’s perpetually running in the background.
Update (2010-01-09): So turns out wpengineer.com had this figured out a while back (i.e. October 2008). Regardless, it was a good opportunity for me to dig into the WordPress core and figure out what’s going on.
…or in “proper” English: Feed Killer.
Basically, a small plugin to disable all your feeds on your WordPress install, for whatever crazy reason; we don’t judge (much). This is a result of a question by @wesbos.
There’s also a non-plugin version if you don’t want to go the plugin route (for whatever crazy reason; again, we don’t judge (extensively)). Just add the code to your theme’s functions.php file.
See below or download from gisthub.
Here’s an idea that I thought might be a useful addition to Edit Flow especially once we add in User Group functionality. The main premise is to have a full-out User Directory accessible by logged in users that provides easy access to contact information for other users on the site. Would probably only be useful for larger groups using WordPress, but I’d imagine would still come in handy for newsrooms and such.
Ever look through your list of plugins and forget just exactly what one of them does? I know they have descriptions next to them, but that doesn‚Äôt always speak to exactly what you are using it for and why. This plugin would just put a text field in each plugin field you could type some notes in there, theoretically to keep information about why and how you are using this plugin.
And since I was bored (and thought this was a pretty useful idea), I delivered. Plugin Notes is exactly what it sounds like.
When a note is added, it shows up inside a little blue box and includes the name of the user that added the note as well as the date and time when the note was added. You also get handy dandy options to “Edit” or “Delete” notes.
Each plugin can only have one note. I can imagine there would be cases where multiple notes may come in handy, but those would be rare so I’m passing on that functionality.
The plugin is pretty simplistic, and unlikely to see any future feature additions (unless someone really, really wants one). I’ll keep a watch for compatibility with future versions of WordPress though, so rest easy.
Excited, enough? Grab Plugin Notes (from the WordPress Plugin Directory) or download it from within WordPress.
Note: this is cross-posted from a post that I wrote on the CoPress blog.
This past weekend, we released the beta version of Stage 1 (Custom Post Statuses) of the Edit Flow Project, a plugin aiming to improve the WordPress Admin Interface for a multi-user newsroom’s editorial workflow.
The main goal of this stage was to “improve posts statuses by allowing custom statuses.” WordPress, by default, only allows for two statuses for posts during the editing process: “Draft” and “Pending Review”. These statuses are not very descriptive nor do they make it easy to track a story as it moves through a newsroom’s often complex, multi-level workflow.
With the release of Stage 1 of Edit Flow, WordPress users can now assign custom statuses to posts, giving them more control over the state of their content.
I released a new update for Co-Authors Plus today. The version number gets bumped to v1.2 and includes mostly fixes, the major one being compatibility with WordPress 2.8. Details about changes below. To upgrade, click the upgrade link in your WordPress Admin dashboard, under Plugins, or download the latest version here.
Any issues, leave a comment, or send me a message.
- FIX: Added compatibility for WordPress 2.8
- FIX: Added new template tags (getthecoauthormeta & thecoauthor_meta) to fix issues related to displaying author info on author archive pages. See Other Notes for details.
- FIX: Plugin should now work for plugins not using the ‘wp_’ DB prefix
- FIX: Coauthors should no longer be alphabetically reordered when the post is updated
- FIX: Plugin now used WordPress native AJAX calls to tighten security
- DOCS: Added details about the new template tags
Today, I released the first public version of the Co-Authors Plus plug-in for WordPress, which allows multiple authors to be added to Posts and Pages. The plug-in is an extension of the Co-Authors plug-in created by Weston Ruter.
The plug-in is a result of a this conversation, namely how to deal with users as your userbase grows, a genuine problem facing newspapers, magazines, and community sites using WordPress, and a problem I’ve been toying with for a while now while working on website for The Boar.
Currently, WordPress allows only a single author per Post/Page. Weston’s plugin fixed that problem. However, the other design problem it failed to overcome was the usage of drop-downs to assign users to Posts/Pages. Once you scale up to 10+ users, this starts to become unmanageable (and when you start pushing 100+ it really becomes a problem).¬† Granted, the typical blog would not deal with this problem. Granted, the design is only a problem when you dealing with a large number of users, and therefore not something the average blog would worry about.
So, what’s the main difference between Co-Authors and Co-Authors Plus?
Find it here: http://wordpress.org/extend/plugins/co-authors-plus/