It currently supports the following url formats:

• http://localtime.at/14:23:00/PDT
• http://localtime.at/14:23/Europe/Berlin
• http://localtime.at/14:23:00/Los Angeles
• http://localtime.at/2012-12-31/14:23:00/Los-Angeles
• http://localtime.at/2012-12-31 14:23:00/London

It’s not much at the moment, but it does what I need and makes a good addition to Alfred.

Apart of all the little tweaks and fixes there are also a bunch of very useful feature coming along with this version:

Experienced users will appreciate the new drag-and-drop uploader, hover menus for the navigation, the new toolbar, improved co-editing support, and the new Tumblr importer. We’ve also been thinking a ton about what the WordPress experience is like for people completely new to the software. Version 3.3 has significant improvements there with pointer tips for new features included in each update, a friendly welcome message for first-time users, and revamped help tabs throughout the interface. Finally we’ve improved the dashboard experience on the iPad and other tablets with better touch support.
There is a ton of candy for developers as well. I’d recommend starting your exploration with the new editor API, new jQuery version, better ways to hook into the help screens, more performant post-slug-only permalinks, and of course the entire list of improvements on the Codex and in Trac.

Of course we updated our documentation to the newest version and also the WordPress Syntax Mode for Coda got an update.

Please have a look at our Function, Action and Filter index for a quick overview and see the list of some of the new and deprecated functions below.

New functions:
Theme related

• _wp_footer_scripts – Private, for use in *_footer_scripts hooks
• check_theme_switched – Checks if a theme has been changed and runs ‘after_switch_theme’ hook on the next WP load
• print_late_styles – Prints the styles that were queued too late for the HTML head.

Meta data related

• delete_metadata_by_mid – Delete meta data by meta ID
• delete_post_thumbnail – Removes a post thumbnail.
• get_metadata_by_mid – Get meta data by meta ID
• metadata_exists – Determine if a meta key is set for a given object
• register_meta – Register meta key
• update_metadata_by_mid – Update meta data by meta ID

Admin bar related

• wp_admin_bar_add_secondary_groups – Add secondary menus.
• wp_admin_bar_my_account_item – Add the "My Account" item.
• wp_admin_bar_search_menu – Add search form.
• wp_admin_bar_site_menu – Add the "Site Name" menu.
• wp_admin_bar_wp_menu – Add the WordPress logo menu.

Other functions

• is_main_query – Is the query the main query?
• wp_cache_decr – Decrement numeric cache item’s value
• wp_cache_incr – Increment numeric cache item’s value
• wp_editor – Renders an editor.
• wp_no_robots – Display a noindex meta tag.
• wp_trim_words – Trims text to a certain number of words.

Deprecated functions:

• _wp_admin_html_begin
• _ipad_meta
• wp_tiny_mce
• wp_quicktags
• wp_print_editor_js
• wp_preload_dialogs
• wp_admin_bar_dashboard_view_site_menu
• wpmu_admin_redirect_add_updated_param
• wpmu_admin_do_redirect
• type_url_form_video
• type_url_form_image
• type_url_form_file
• type_url_form_audio
• the_editor
• start_post_rel_link
• screen_options
• screen_meta
• screen_layout
• sanitize_user_object
• parent_post_rel_link
• media_upload_video
• media_upload_image
• media_upload_file
• media_upload_audio
• is_blog_user
• index_rel_link
• get_user_metavalues
• get_user_by_email
• get_userdatabylogin
• get_parent_post_rel_link
• get_index_rel_link
• get_boundary_post_rel_link
• favorite_actions
• add_contextual_help

But if you really live in WordPress code all day long you might sometimes wish that you can just log into it and do your thing without the need of leaving test scripts all over the place.

You can do this with wpshell, a tool written by my fellow Automattician Apokalyptik. Although this is a fairly unknown and well hidden piece of code it’s worthy to install it on your local development environment in order to dive right into WordPress. After adjusting some basic configurations wpshell gives you a command shell that accepts native PHP code as well as all the functionality your regular WordPress install would give you. And there is even more, it also parses all the tokens and lets you grab information about function definitions, their parameters and the like.

If this got you excited go ahead and watch this video showing wpshell in action and how it is installed.

Before we get started, there are some requirements and warnings:

• This is intended for advanced developers. If you don’t know what you’re doing you can easily mess up your WordPress install
• Although possible, I would not run this on production, but only in a local development environment
• You need to have a working installation of WordPress that will be utilized by wpshell

Here’s a quick walkthrough of the installation procedure:

• svn co http://code.svn.wordpress.org/wpshell wpshell

  (check out the wpshell repository)

• cd wpshell

  (get in the folder)

• vi wpshell

  (adjust shell variable and 2 occurences of the PHP path to your needs )

• vi wpshell-config.php

  (adjust HTTP_HOST, REQUEST_URI and other $_SERVER variables that might need adjustments to fit your WordPress install. You can easily check those values in your current WordPress installation. Adjust require statement to point to the wp-config.php of your WordPress install.)

If you did everything right you should now be able to use the shell. Here are some basics.

Invoking the shell:

• wpshell

  will get you a command prompt. Here you can enter native PHP code or WordPress functions or functions defined elsewhere in your project

• echo 'echo $blog_id' | wpshell

  will take the command(s) you pipe to the shell and execute them

• wpshell < /path/to/a/php/script

  will use the php script as source for the commands

wpshell also comes with a bunch of built-in commands to make your life easier. Here are some of them

Database queries:

• get_results $query

  returns the result of $wpdb->get_results

• get_var $query

  returns the result of $wpdb->get_var

• get_col $query

  returns the result of $wpdb->get_col

• get_row $query

  returns the result of $wpdb->get_row

Filesystem:

• ls [path]

  list the content of the current directory

• cd [path]

  change current working directory

• quit

  quit the shell

Reference:

• d $function_name

  displays the function definition

• f $function_name

  displays the function source

• fsearch $search_string

  search for a function matching the search string in the current working directory

• c $class_name

  returns the class source

• csearch $search_string

  search for a class matching the search string in the current working directory

That’s all nice, but what can I do with it? – The sky is the limit.

I personally use it like this; I wrote a small Coda Plugin that takes selected content and executes it in wpshell and throws the result back to a new tab in my editor. In this way I can just mark code fragments or queries and run them against wpshell right away.
I also created a small PHP script together with an AppleScript that allows me to search for a function and open the file it’s defined in directly in Coda and jump to the correct line or alternatively perform a php.net manual lookup and display the result in Coda.
If there is any interest I can make these scripts public as well. They are still very edgy though.
I also have a wpshell running inside a screen session and keep it always accessable via TotalTerminal.

Plans:

I did not have much time to look into it, but the code is so awesome that I hope to integrate it better in my IDE. I’m planning to setup the parameters in wpshell-config.php automatically when I fire up a wpshell from within Coda. It would traverse upwards from the opened file until it finds a wp-config.php and setup HTTP_HOST and path accordingly. It could also work by simply entering a URL and Coda would fire up a preview window in Chrome along with the wpshell adjusted to exactly this url.

If that’s the case then you might want to take wp-cron-control for a spin.

This small plugin allows you to disable the normal wp-cron processing that is usually hooked into the sanitize_comment_cookies filter and setup a regular system cron job that calls wp-cron.php with a customizable secret string instead.

The focus for this release was making WordPress faster and lighter,  it comes with  the fully HTML5 new Twenty Eleven theme and an improved full-screen button in the editing toolbar which lets you enter the new distraction-free writing or zen mode, where the widgets, menus, buttons, and interface elements get out of your way for a Zen like editing experience.

PHP-HTML-WP mode

The mode is based on the PHP-HTML mode that comes with Coda 1.7 and WordPress 3.3.

Requirements:

Tested on Coda 1.7, might work on previous versions.

Installation:

1. Download the packed mode file and unpack it.
2. Copy the PHP-HTML-WP.mode the Coda Modes folder. ~/Library/Application Support/Coda/Modes/
3. Open a WordPress or PHP file and load the syntax mode in Coda by visiting Text -> Syntax Mode -> PHP-HTML-WP in the toolbar.
4. Optional: To make this mode the default visit the Editor pane in the Preferences window and select the ‘PHP-HTML-WP’ mode as default file type

Please note that this is an early version and is most likely still buggy. If you encounter any issues don’t hesitate to leave us a note.

We love to help you. As we’re all passionate WordPress users we are happy to help you get your open WordPress related questions answered and problems solved.

Fill out the form below and we will publish it after a quick review or get back to you.

This security release is required if you have any untrusted user accounts, but it also comes with important security enhancements and hardening. All WordPress users are strongly encouraged to update.

Three point oh point five

Enhances security

Three point one comes soon

The release addresses a number of issues and provides two additional enhancements:

Two moderate security issues were fixed that could have allowed a Contributor- or Author-level user to gain further access to the site.

One information disclosure issue was addressed that could have allowed an Author-level user to view contents of posts they should not be able to see, such as draft or private posts.

Two security enhancements were added. One improved the security of any plugins which were not properly leveraging our security API. The other offers additional defense in depth against a vulnerability that was fixed in previous release.

Thanks to Nils Jueneman and Saddy for their private and responsible disclosures to security@wordpress.org for two of the issues. The others were reported or repaired by our security team.

Download 3.0.5 or update automatically from the Dashboard > Updates menu in your site’s admin area. Please update immediately.

WordPress 3.1 Release Candidate 4 is also now available.

The Release Candidate 4 build includes the security fixes and enhancements included in 3.0.5 and addresses about two dozen additional bugs. This includes fixes for:

• Deleting a user and reassigning their posts to another user.
• Marking multiple users or sites as spam in multisite.
• PHP4 compatibility.

As outlined in previous RC posts, if you are testing the release candidate and think you’ve found a bug, there are a few ways to let us know:

• Post it to the Alpha/Beta area in the support forums
• Report it to the wp-testers mailing list
• Join the development IRC channel and tell us live at irc.freenode.net #wordpress-dev
• File a bug ticket on the WordPress Trac

To test WordPress 3.1, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can download the release candidate here (zip). If any new issues become known, you’ll be able to find them here.

After nearly five months of development and testing, we think we’re very close to a final release. Users and developers, please test your themes and plugins.

Download WordPress 3.1 RC4 or WordPress 3.0.5 now.