While manually upgrading a bunch of old WordPress sites, I realized that the WordPress htaccess rules for permalinks had changed. For many years and versions, the htaccess code that enables WordPress permalinks went unchanged, resulting in an almost sacred set of htaccess directives. Here are the original permalink rules as currently provided at the WordPress Codex:
The default URL for logging into your WordPress powered site is:
http://example.com/wp-login.php. Or if you've installed in a subdirectory, something like
http://example.com/wp/wp-login.php. I've wished that was a little cleaner, especially when you are doing something explaining to a client where to log in over the phone. Fortunately changing this can be very easy.
In this DigWP post, we transform three slices of code into a clean & stylish tabbed menu that visitors can use to login, register, and recover passwords from anywhere on your site.
There are too many features and details to explain up front, so take a moment to check out the working demo to see the finished product.
Have you ever wanted to close a comment thread, but leave a note to communicate why the thread is closed? Many blogs will just update the content of the blog post to say that comments are closed and why. That's better than nothing, but that puts the message in a bit of an awkward place.
The ideal place for that custom messaging is after the comment thread, where the comment form would normally be. After all, that's where it makes the most sense.
I think WP Candy is really killing it lately being a great source of breaking quality WordPress news, interviews, and other articles. Now they have an iPhone app they developed in-house to bring all the content to you that way. They are rolling it out "reverse" style, where for two weeks it's $5.99 then later it drops to $0.99, so it's an opportunity for the community to opt-in to paying more to support the site, which is neat, especially considering their crazy no advertising policy.
MediaElements.js is an open source jQuery-based project (which I use and like) which allows you to use HTML5 video and audio in any browser all the way back to IE 6. It tests if the browser supports HTML5. If yes, it uses that. If no, it falls back to displaying the media through Silverlight or Flash. Regardless of what it uses, the UI is always consistant.
Now available as a WordPress plugin to make it even easier. Just use simple shortcodes to link up the video and specify what options you want (e.g. autoplay, fullscreen, etc).
In otherwords, match what you see when creating/editing a Post or Page in the WordPress visual editor to what you get when you actually publish it. It's easier than you might think! Basically you can declare a special CSS file that the visual editor will use to render itself while you are editing it. If the styles in that CSS file match the styles in your live theme's CSS file, you are straight up WYSIWYG (What You See Is What You Get).
To celebrate this magical time of year, we’re giving away FREE copies of Digging Into WordPress and throwing a HUGE Holiday Sale! PLUS we’re selling a limited number of slightly damaged books (scratch-&-dent) for $15 OFF.
Without touching a line of code, you can harness the power of Ajax to boost performance, improve usability, and fill your site with win.
One of the themes that is an exclusive download to all you good-looking people that purchased The Book is the All AJAX theme. The idea behind it is that the page never1 reloads. Whenever an "internal" link is clicked, the main content area replaces itself with content that is fetched via Ajax. So posts, pages, search results, and everything else loads right there on the same page. This gives your visitors a smooth, "app-like" experience.
As part of our ongoing mission to always find new ways to improve our operation, we’ve set up a new system for downloading DigWP book updates.
The new system is much more user-friendly and is designed to simplify things and make the upgrade process easier for everyone.
Are you hosting your WordPress sites on one of those hosts where WordPress asks you to provide FTP details before upgrading itself or upgrading plugins? So when you click to do an upgrade, instead of just launching into the update process, you get a screen that looks like this instead: