WordPress Version 2.9 New Features
New Features
User Features
* Trash status for posts, pages, and comments (includes restore and
permanent delete)
* Add support for ‘include’ and ‘exclude’ to
(Gallery
Shortcode)
* Allow user registration to be enabled by an XMLRPC client
* Add support for sticky posts to the WXR exporter and importer
* ‘rel=canonical’ for singular pages
* Scroll back to the same location after saving a file in the Plugin
and Theme editors
* Correct comments and remove unnecessary echos from the default
themes sidebar template file
* Enable the APP (Atom) attachment file download to work correctly
* Support location of category templates based on ‘category-slug’ as
well as ‘category-id’ (Ticket 10614)
* Support location of tag templates based on ‘tag-id’ as well as
‘tag-slug’ (Ticket 10868)
* Support location of page templates based on ‘page-slug’ and ‘page-id’
* Set “Allow my blog to appear in search engines” to checked in
installation
* Don’t offer to make a category its own parent
* Remove Sphere from search list
* Minify admin CSS
* Show correct max upload filesize error message
* Add ‘rel’ attribute to next/previous post links
* Make the default and classic themes comment textareas valid XHTML
* Clean up ‘.button’ and ‘.button[disabled]‘ CSS classes, add
‘spinner’ and ‘gray-out’ buttons after clicking Publish or Update post
* Fix race condition with autosave when clicking Publish immediately
after entering post title
* Add Comments for Pages in the WordPress Default theme
* Define ‘$content_width’ for Kubrick
* Better feedback on publishing of future posts and pages
* Display comments in descending date order, consistently
* Add means of automatically repairing tables
* Press This bookmarklet fixes
* Give plugins and themes simple control over the text displayed at
the end of an autogenerated Excerpt
* Don’t show “Change Permalinks” button when editing the page set as
“Front page”
* Image editing
* Retire BunnyTags importer
* Retire Jerome’s keywords importer
* Explain that the permalink is temporary for autosave generated
permalinks
* Update SimplePie to 1.2
* Eliminate the redundant and confusing comment threading depth of 1
* Easier Embeds with oEmbed support (see Ticket #10337) (oEmbed
discovery disabled by default, use plugin to enable it)
* TinyMCE 3.2.7
* Remove rel=’tag’ on links in Tag Clouds
* Add a title to the Home link output by wp_page_menu()
* Adjust comment moderation keyboard shortcut keys ‘d = trash’ or
delete depending on the screen
* Show “Draft updated” instead of “Post updated” when saving draft
* Show the login form in a popup when autosave hits the login grace
period
* Open View/Preview post in a new window from the link in the
Saved/Updated message
* Separate fields for ‘image alt’ and ‘image caption’ in Media uploader
* Display better information about broken themes when there is no
stylesheet
* Improve situation when tables such as wp_options table were
‘corrupt’ new installation message was offered. Add means of
automatically repairing tables
* Export and import custom taxonomies
* Admin copy improvements
* Don’t show page templates in the drop down if they are in a
subdirectory
* Make codex link open in a new window
* Change ‘Remove’ link on widgets to ‘Delete’ because it doesn’t
just remove it, it deletes the settings for that widget instance.
Development, Themes, Plugins
* Added ‘excerpt_more’ filter to wp_trim_excerpt() function, which
allow developers to change excerpt ‘[...]‘ more string (Ticket 10395)
* Add ‘smilies_src’ filter so plugins can better add smilies
* Canonical redirects for post name queries
* Allow _wp_get_comment_list() to handle custom comment types
* Return an empty array instead of false for get_children() when no
children found
* Add some filters so that HTTP requests can be filtered
* Move plugin update notice output to the plugin specific hook
* Limit wp-mail ‘blog by email’ checks to every 5 minutes
* Make it much easier to filter contact methods from user profiles
* Allow filtering of get_edit_post_link for custom post_type
* ‘get_sample_permalink_html’ filter
* Enforce activation key to be a string, reject activation keys that
are arrays
* Support for new post types
* Respect custom post_type in queries
* Send Retry-After header when in maintenance mode
* Various WP Filesystem related fixes and documentation
* Add constants for ftp connections timeouts
* Increase timeout on cron-based requests when checking for upgrades
* Don’t use has_action() before do_action() in http.php
* Speed up jQuery based scripts
* Use the current user as author for autosave
* Show My Posts as default view on the Edit Posts screen for users
without ‘edit_others_posts’ cap
* Ensure that drafts viewed over XMLRPC have a correct gmt date set
* Pass user id to ‘get_’ the_author_meta filters
* Move _wp_get_user_contactmethods() into the registrations
functions file
* Machine parseable db error codes
* Add global JS vars and actions to the media uploader iframe
* Add JSON compat for PHP < 5.2
* Make option_name the primary key for the options table
* Allow a plugin to do a complete takeover of Post by Email
* Logarithmic scale for tag cloud
* Pass Post ID to the ‘get_comments_number’ filter
* Always filter the url in the media upload form
* Add a ‘the_terms’ filter
* is_blog_installed() improvements
* Allow force_ssl_admin() to properly accept false as a value
* Pass logged_in cookie to async-upload and filter the cookie scheme
in auth_redirect()
* Add more actions around database add/delete/update operations
* phpDoc for wp_”check|set”_post_lock functions
* Use the old strings which are more translator friendly and add a
generic default string to aid re-use by plugins adding post_types
* Filter fields through kses upon display and introduce
sanitize_user_object() and sanitize_user_field()
* Use null instead of 0 when setting content length
* Include ‘hidden’ directories in filesystem dirlist by default
* Pass args array to ‘wp_list_pages’ filter
* Actions for taxonomy updates
* Key should be ‘comment_id’ not ‘post_id’ in comments table
* Add get_delete_post_link () to retrieve delete posts link for post
* Add ‘separator’ parameter to wp_tag_cloud() and
wp_generate_tag_cloud() functions (Ticket 10315)
* Added add_comment_meta() family of functions
* Use a post_parent of 0 instead of -1 to indicate unattached posts
* Improve get_page_hierarchy() function
* Deprecate the_content_rss(), add the_content_feed() and
get_the_content_feed(). Convert places that called the_content_rss()
with an excerpt length to the_excerpt_rss(). Remove the
rss_excerpt_length option. Use the_content_feed() where the_content()
was previously used in feeds.
* Add ‘pad_counts’ argument to wp_dropdown_categories()
* Remove codepress
* Remove the php-gettext library
* Canonical post thumbanils
* Add a filter to the_author_posts_link()
* Merge post.js with page.js and slug.js, optimize categories and
tags JS, standardize postboxes IDs and JS
* Introduce register_theme_directory() which takes a
wp-content-relative path and will additionally scan it for themes.
Plugins can use this to add themes without requiring copying by the user
* Add set_user_role action hook
* Allow theme devs to change attrs (like CSS class) of thumbnail images
* Add wp-post-image CSS class to post images
* Allow for plugins to enhance the number of metadata fields
captured from plugin and theme headers
* Merge updated pomo code
* Switch to using NOOP_Translations for untranslated sites
* Improve wptexturize performance
* Provide context to the strings in the Plugin and Theme installers
to allow for different grammatical gender
* Fixes for theme subdir support
* Introduce wp_kses_post() and wp_kses_data() for filtering
unescaped data
* Add ‘orderby=comment_count’ argument to query_posts()
* Honor Post Type for Sticky Posts
* Allow querying multiple post types
* Introduce add_theme_support(feature) and
current_theme_supports(feature) for announcing and checking theme
support for various features
* Introduce require_if_theme_supports()
* Add number of Embed related filters
* Add ‘IMAGE_EDIT_OVERWRITE’ constant to control edited image save
or replace, most useful for setups that have dynamic image resizing
* Add load_child_theme_textdomain() to allow child themes to have
their own translation files
* Add sidebar descriptions to sidebar settings and widget admin screen
* Make option_id primary. Add uniques for option_name and autoload
* Allow plugins to override the behaviour of load_textdomain() in a
variety of flexible ways
* Mark _c() as deprecated. The new _x() function should be used instead.
* Allow plugins to change the redirect on post/page
publishing/submitting
* Standardize on ‘user_id’ instead of ‘user_ID’ when passing comment
data. Accept either ‘user_id’ or ‘user_ID’. Remove ‘user_id’ global.
* Filter imported comments
* Introducing set_post_image_size(w, h, crop) so themes can register
their special size/crop for canonical post images
* Standardize around “post image” instead of “post thumbnail”
* Allow registering post image support per post type
* Return false from is_paged() if on the first page.
* Check MySQL and PHP versions when auto upgrading
* Add required php and mysql versions to version.php
* Hard code required version in update-core.php
–
Dwayne Myers
(386)307-4289
Http://www.DreamDrivenDesigns.com
Chinese Characters in WordPress
Chinese characters do not work in WordPress by default if you didn’t
originally setup your WordPress to handle Chinese.
However, it is pretty easy to get it working. I didn’t see it
documented elsewhere, so I thought I’d post instructions on configuring
WordPress to allow posting Chinese.
* Using a program (like phpMyAdmin) to administer your database,
select the WordPress database.
* Find the wp_posts table, and click on the “structure” icon (it is
the second from the left under Actions)
* Click the “pencil” icon on the wp_content table.
* Change the Collation option to utf8_unicode_ci (on mine, that’s
the option at the very bottom).
* Click Save.
* If you want to enable Chinese in titles, you can repeat the
procedure for the wp_posts.wp_title. You might also want to enable it
in comments by repeating on wp_comments.comment_content and
wp_comments.comment_author.
That’s it! You can now post 汉字 in WordPress!
-- Dwayne Myers (386)307-4289 Http://www.DreamDrivenDesigns.com
How to show your Skype status on the web
How do I get a Skype status button?
Edit your privacy options in Skype to show your status on the web.
Simply go to Tools > Options > Privacy to update your settings.
Tick the “Allow my status to be shown on the web” checkbox and “Save”.
Use the wizard to customise your button
What next?
You’ll be given a little snippet of code to paste into your blog, email signature, message board post — or anywhere else you want people to contact you online. Here’s our little guide to putting a Skype button in your email signature.
What will my buttons look like?
Your Skype buttons will show your actual Skype status. So, if you’re
online and in the mood for random conversation, you’ll set your status
to “Skype Me!” and “Skype Me!” will also show on the web, wherever
you’ve pasted your buttons.
(Please note that if you’re in “Invisible” mode, anyone viewing your buttons
will see that you’re “Offline”.)
Below is a link to the original posting on skype’s website.
http://www.skype.com/share/buttons/status.html
–
Dwayne Myers
(386)307-4289
Http://www.DreamDrivenDesigns.com
WordPress Template Files Heirachy & Stucture
Codex
Codex tools: Log in / create account
Template Hierarchy
Languages: English • Français • 日本語 • Русский • (Add your language)
Note: This article covers an advanced topic. See Stepping Into
Templates for an introduction to WordPress templates.
Contents
[hide]
* 1 Introduction
o 1.1 What this article is about
o 1.2 Who might find this useful
o 1.3 Using Conditional Tags
* 2 The Template File Hierarchy
o 2.1 The General Idea
o 2.2 Examples
o 2.3 Visual Overview
o 2.4 The Template Hierarchy In Detail
+ 2.4.1 Home Page display
+ 2.4.2 Single Post display
+ 2.4.3 Page display
+ 2.4.4 Category display
+ 2.4.5 Tag display
+ 2.4.6 Author display
+ 2.4.7 Date display
+ 2.4.8 Search Result display
+ 2.4.9 404 (Not Found) display
+ 2.4.10 Attachment display
* 3 Changelog
* 4 Source File
* 5 See also
* 6 External Resources
Introduction
WordPress Templates fit together like the pieces of a puzzle to
generate the web pages on your WordPress site. Some templates (the
header and footer template files for example) are used on all the web
pages, while others are used only under specific conditions.
What this article is about
This article seeks to answer the following question:
Which template file(s) will WordPress use when it displays a
certain type of page?
Who might find this useful
Since the introduction of Themes in WordPress v1.5, Templates have
become more and more configurable. In order to develop WP themes, a
proper understanding of the way WordPress selects template files to
display the various pages on your blog is essential. If you seek to
customize an existing WordPress theme, this article aims to help you
decide which template file needs editing.
Using Conditional Tags
WordPress provides more than one way to match templates to query types.
WordPress Theme developers can also use Conditional Tags to control
which templates will be used to generate a certain page. Some WordPress
Themes may not implement all of the template files described here. Some
Themes use conditional tags to load other template files. See the
Conditional Tags page and “Query Based” in Theme Development for more.
The Template File Hierarchy
The General Idea
WordPress uses the Query String — information contained within each
link on your web site — to decide which template or set of templates
will be used to display the page.
First, WordPress matches every Query String to query types — i.e. it
decides what type of page (a search page, a category page, the home
page etc.) is being requested.
Templates are then chosen — and web page content is generated — in the
order suggested by the WordPress Template hierarchy, depending upon
what templates are available in a particular WordPress Theme.
WordPress looks for template files with specific names in the current
Theme’s directory and uses the first matching template file listed
under the appropriate query section below.
With the exception of the basic index.php template file, Theme
developers can choose whether they want to implement a particular
template file or not. If WordPress cannot find a template file with a
matching name, it skips down to the next file name in the hierarchy. If
WordPress cannot find any matching template file, index.php (the
Theme’s home page template file) will be used.
Examples
If your blog is at <a class=”moz-txt-link-freetext”
href=”http://example.com/wp/”>http://example.com/wp/ and a visitor
clicks on a
link to a category page like <a class=”moz-txt-link-freetext”
href=”http://example.com/wp/category/your-cat/”>http://example.com/wp/category/your-cat/,
WordPress looks for a template file in the current Theme’s directory
that matches the category’s ID. If the category’s ID is 4, WordPress
looks for a template file named category-4.php. If it is missing,
WordPress next looks for a generic category template file,
category.php. If this file does not exist either, WordPress looks for a
generic archive template, archive.php. If it is missing as well,
WordPress falls back on the main Theme template file, index.php.
If a visitor goes to your home page at <a class=”moz-txt-link-freetext”
href=”http://example.com/wp/”>http://example.com/wp/,
WordPress first determines whether it has a static front page. If a
static front page has been set, then WordPress loads that page
according to the page template hierarchy. If a static front page has
not been set, then WordPress looks for a template file called home.php
and uses it to generate the requested page. If home.php is missing,
WordPress looks for a file called index.php in the active theme’s
directory, and uses that template to generate the page.
Visual Overview
The following diagram shows which template files are called to generate
a WordPress page based on the WordPress Template hierarchy.
Graphic Example of the WordPress Template Hierarchy Structure Full-Size
Image (png)
The Template Hierarchy In Detail
The following sections describe the order in which template files are
being called by WordPress for each query type.
Home Page display
1. home.php
2. index.php
Single Post display
1. single.php
2. index.php
Page display
WordPress Pages:
1. custom template – Where custom template is the Page Template
assigned to the Page.
2. page-slug.php – If the page slug is recent-news, WordPress
will look to use page-recent-news.php Note: not available until Version
2.9.
3. page-id.php – If the page ID is 6, WordPress will look to use
page-6.php Note: not available until Version 2.9.
4. page.php
5. index.php
Category display
Category Templates:
1. category-slug.php – If the category’s slug were news,
WordPress would look for category-news.php Note: not available until
Version 2.9.
2. category-id.php – If the category’s ID were 6, WordPress
would look for category-6.php
3. category.php
4. archive.php
5. index.php
Tag display
Tag Templates:
1. tag-slug.php – If the tag’s slug were sometag, WordPress
would look for tag-sometag.php
2. tag-id.php – If the tag’s ID were 6, WordPress would look for
tag-6.php Note: not available until Version 2.9.
3. tag.php
4. archive.php
5. index.php
Author display
Author Templates:
1. author.php
2. archive.php
3. index.php
Date display
Archive (Date) Templates:
1. date.php
2. archive.php
3. index.php
Search Result display
Creating a Search Page:
1. search.php
2. index.php
404 (Not Found) display
Creating an Error 404 Page:
1. 404.php
2. index.php
Attachment display
Attachment Templates:
1. MIME_type.php – it can be any MIME type (image.php,
video.php, audio.php, application.php or any other).
2. attachment.php
3. single.php
4. index.php
-- Dwayne Myers (386)307-4289 Http://www.DreamDrivenDesigns.com
In the case of categories, the hierarchy is fairly simple. For instance,
suppose the slug of the Category in question is default and the Category
ID is 6. The Template Hierarchy specifies that WordPress will use the
first Template file it finds in your current Theme’s directory from the
following list:
1. category-slug.php (Note: available with Version 2.9)
2. category-ID.php
3. category.php
4. archive.php
5. index.php
That is, if you do not have a category-slug.php (lets say
category-news.php), WordPress will check for a category-ID.php (like
category-6.php), and so on.
So, if you want to make the Category whose ID number is 6 look different
from what it is currently (and different from other Category pages), you
would want to create a category-6.php file. If you want to make all
Category pages look different from other archive pages (such as date and
author archives), then you would want to create or modify the
category.php file. If you want to make changes to the look of all
archive pages, you can create or modify the archive.php file. And if you
modify the index.php file, you will affect your entire blog.
If you need to create a new file, it is a good idea to copy it from the
next file in the hierarchy that exists. For instance, if you want a
special display for Category 6, begin by copying the category.php file,
or if you don’t have one, use archive.php, and so on.
–
Dwayne Myers
(386)307-4289
Http://www.DreamDrivenDesigns.com