When I created the navigation menu at the top of my site using the menu feature in WordPress (Appearance → Menus), I didn’t want to have to maintain anything but the top-level menu items. When I released a new plugin and created a page for it, I didn’t want to have to go into my menu UI and add it there too. So instead I wrote this plugin.
Add Descendants As Submenu Items adds a checkbox to each menu item that is of a hierarchical post type (i.e. pages). Checking this box will automatically display all descendants as submenu items on the front end of your site. You can see it in action at the top of my site — I only configured the top level menu items and everything that shows up when you hover over them has been added by my plugin rather than manually by me.
An example menu and the checkbox this plugin adds
These submenu items have been added by the plugin
For more details and to download the plugin, check out the plugin’s homepage.
I’ve released a major update to my popular Regenerate Thumbnails plugin. From the changelog:
- Thanks to a lot of jQuery help from Boris Schapira, a failed image regeneration will no longer stop the whole process.
- The results of each image regeneration is now outputted. You can easily see which images were successfully regenerated and which failed. Was inspired by a concept by Boris.
- There is now a button on the regeneration page that will allow you to abort resizing images for any reason. Based on code by Boris.
- You can now regenerate single images from the Media page. The link to do so will show up in the actions list when you hover over the row.
- You can now bulk regenerate multiple from the Media page. Check the boxes and then select “Regenerate Thumbnails” form the “Bulk Actions” dropdown. WordPress 3.1+ only.
- The total time that the regeneration process took is now displayed in the final status message.
- jQuery UI Progressbar version upgraded.
The main plugin interface.
Regenerating in progress.
Interface for regenerating a single attachment.
Individual images can be regenerated from the media library in list view.
They can also be regenerated from the edit attachment screen.
As you can see, lots of great new stuff. I hope you all enjoy it. 🙂
Not everyone was happy with the new highlighting package featured in SyntaxHighlighter v3.0.0 and using old versions of plugins is a bad idea (you miss out on features, bug fixes, etc.) so I’ve added the ability to toggle between v2 and v3 of Alex G’s SyntaxHighlighting package. I’ve also fixed a few bugs that were discovered post-release (such as HTML entities being broken in the Visual editor).
Everyone, including those who downgraded to v2.x of my plugin, should upgrade to v3.1.0 of my plugin.
One thing to note by the way: I would stay far, far away from TinyMCE (the Visual editor/tab) when blogging about code. It has the nasty little habit of attempting to “clean up” your code (namely HTML) for you and in the process with mess up your code. If you’re writing code, what are you doing using a WYSIWYG editor anyway? 😉
I finally found some time to work on my SyntaxHighlighter Evolved plugin and upgrade it use the latest version of Alex Gorbatchev’s highlighter.
- The new version of Alex G.’s script makes it easier to select and copy code. You can just drag your mouse to highlight and you will no longer get line numbers or you can double-click the code to highlight it all (in plain text to avoid getting the colors). Click off of the code to get it to go back to the colorized version.
- You can specify a range of line numbers to highlight. Instead of having to do
highlight="5,6,7,8,9,10,14" you can now just do
- BuddyPress support.
- A few new custom brushes (Clojure and the R language) and a Ukrainian translation.
Upgrade or download it now! 🙂
I’ve released a new plugin that switches WordPress’s language setting based on the user’s browser language preferences. More details on the plugin’s homepage.
If you’re living in a cave, WordPress 3.0 has been released.
For security reasons, the UI to enable oEmbed’s discovery ability was removed from WordPress today. It’d be too easy for a novice to accidentally embed some bad HTML into their blog if they posted the URL to a malicious website.
However if you know what you’re doing, feel free to install my Enable oEmbed Discovery plugin which will re-enable the feature. 🙂