PUBLIC MARKS from mozkart

echo date("l jS of F Y", get_post_meta($post->ID, 'date_value', true));

This is currently a limitation with our datepicker field type which we will be resolved by the inclusion of our timestamp field type in the new year. This field type is already available, if you'd prefer to add it manually using our custom woo_metaboxes_add() function. We have a tutorial on this here: http://www.woothemes.com/2010/07/customizing-theme-options-through-a-child-theme/ This field does, however, at present require the use of the PHP date() function, as it is new. Currently, the field stores the value as a UNIX timestamp which, when passed through to the date() function, can create a date in any format (while the date is visually still in the m/d/y format when added via this field, it is transposed into a timestamp). If you don't feel comfortable with this amount of PHP code, I'd recommend a simpler solution, which would be a text field with a description, explaining that the date is to be entered in, for example, the YYYY-MM-DD format, which would be suitable for sorting by date.

ORDER POSTS BY CUSTOM KEY REVISITED By BRANDON | Published: JANUARY 13, 2009 I’ve gotten quite a few questions about how to get this to work on a specific page, or only within a specific category. I actually had the same issue when building the script originally. The trick is that you can’t just use the conditional tags in the functions page. At that point, it’s already too late because the queries have already been run. You have to create a function and then run it as a filter on one of the early WordPress initializing functions. I chose the wp() function. Here is my revised code (nearly straight from the client’s site).

After 2 posts in series of creating meta box, I received many ideas and opinions that really helpful. I appreciate that, and I want to give big thanks to all our contributors. It has been a while since the last version of meta box script (2.4.1). Today I want to show you the next major version (3.0) with many improvements in the code, which supports better for OOP, gives big opportunity to developers to extend the class. And of course, some field types are added as well as some bugs are fixed.

After I wrote the article How To Create A Better Meta Box In WordPress Post Editing Page, I received some questions that asked me how to create multiple meta boxes for multiple post types (in WordPress 3.0). So I decide to improve the script to do that.

One thing we were trying to achieve was an Events listing solution that was fundamentally simple. Date, times, location and a description. Many of the events plugins out there seem to store their data in a database table specifically created for the plugin, something that won't play nice with MultiSite. The ideal solution would be a list of events that stores its data in each network site's unique database table structure. Therefore, we chose to set this up as a custom post type with a date picker attached to a custom meta box. We would store the date in a custom field. Simple enough. One thing that had us racking our brains for a while was how to sort the dates in a useful way.

Put this before the loop in archive.php to have posts in the archive for category '26' sorted by custom field 'date'. Assign sortable values like '090501' or '2009-05-01' to those fields when editing posts and your Upcoming Events will be sorted by the future date at which they will take place.

For some projects, it’s nice to output clean, well-formatted markup. Using theme template files enables great control over most of your (X)HTML formatting, but not so much for automated functionality involving stuff like widgets and custom menus. One of my current projects requires clean, semantic HTML markup for all web pages, but also takes advantage of WordPress’ custom-menu functionality to make things easy. In this DiW article, we’ll see how to enjoy both: WordPress custom menus and clean, well-formatted HTML markup.

WordPress 3.0 and up allow to manage new custom post type. Cool ! This plugin allow to build relation between 2 custom types, very useful for manage related content.

Efficient many-to-many connections between posts, pages, custom post types, users.