Sunday, 24 February 2013
|
Labels:
ajax
|
0
comments
|
|
Friday, 22 February 2013
functions.php file.primary, which will be the example sidebar used throughout the remainder of this tutorial.<?php
add_action( 'widgets_init', 'my_register_sidebars' );
function my_register_sidebars() {
/* Register the 'primary' sidebar. */
register_sidebar(
array(
'id' => 'primary',
'name' => __( 'Primary' ),
'description' => __( 'A short description of the sidebar.' ),
'before_widget' => '<div id="%1$s" class="widget %2$s">',
'after_widget' => '</div>',
'before_title' => '<h3 class="widget-title">',
'after_title' => '</h3>'
)
);
/* Repeat register_sidebar() code for additional sidebars. */
}
?>register_sidebar() function accepts a single parameter named $args, which is an array of arguments that define how the sidebar and its widgets should be handled. In the example above, each of these arguments were manually set.id argument is perhaps the most important argument you can set (see the “Bad sidebar code” section below on why you definitely need to set this). WordPress will use the ID to assign widgets to a specific sidebar, and you’ll use the ID to later load the sidebar.sidebar-$i (where $i is a count of the registered sidebars).'id' => 'primary',name argument is the human-readable label for your sidebar used in the WordPress admin. You can set this to anything you think best represents the name of your sidebar. Generally, sidebars are given a name that lets the user know where it’ll appear in the theme.Sidebar $i (where $i is a count of the registered sidebars).'name' => __( 'Primary' ),description argument was introduced in WordPress 2.9. It allows you to set a specific description for how the sidebar is used within your theme. This argument defaults to an empty string. It can also be internationalized.'description' => __( 'A short description of the sidebar.' ),before_widget argument is a wrapper element for widgets assigned to the sidebar. It should also be a block-level HTML element. This argument has a couple of things that you should always set with specific code so that plugins can properly use them, which is the id (%1$s) and class (%2$s) attributes.<li id="%1$s" class="widget %2$s">. I’m not a big fan of making sidebar widgets list items. I typically always go with a <div>.'before_widget' => '<div id="%1$s" class="widget %2$s">',after_widget argument is pretty simple. It’s used as the closing wrapper for widgets assigned to the sidebar. You just need to close off the element you set for the before_widget argument. By default, WordPress sets this to </li>.'after_widget' => '</div>',before_title argument is the opening wrapper element for the sidebar’s widget titles.<h2 class="widgettitle">. I don’t like using an<h2> in this scenario. An <h3> or <h4> seems more semantic. I’m also not sure about the non-hyphenated class name, which makes it nearly unreadable.'before_title' => '<h3 class="widget-title">',after_title argument is to close the wrapper element set in the before_titleargument. By default, WordPress will set this to </h2>. You just need to make sure you set it to properly match the value you gave to the before_title argument.'after_title' => '</h3>'dynamic_sidebar() function takes a single parameter of $index, which can either be the sidebar’s id or name argument (set when you registered the sidebar). While you can technically use either, it’s almost always safer to use the id you set.primarysidebar, which we registered in the previous section. Note that I also used a wrapper element so the sidebar can be easily styled.<div id="sidebar-primary" class="sidebar">
<?php dynamic_sidebar( 'primary' ); ?>
</div>sidebar-primary.php, which you’ll learn about in the “Sidebar templates” section later. However, dynamic_sidebar()can technically be called anywhere within your theme.dynamic_sidebar() function used to load the sidebar, is_active_sidebar()accepts a single parameter of $index, which should be the ID of the sidebar you want to check for active widgets.primary sidebar has widgets. If so, display the widgets. Else, display some custom content.<div id="sidebar-primary" class="sidebar">
<?php if ( is_active_sidebar( 'primary' ) ) : ?>
<?php dynamic_sidebar( 'primary' ); ?>
<?php else : ?>
<!-- Create some custom HTML or call the_widget(). It's up to you. -->
<?php endif; ?>
</div>is_active_sidebar() function to check if the primary sidebar has any widgets assigned to it.<?php if ( is_active_sidebar( 'primary' ) ) : ?>
<div id="sidebar-primary" class="sidebar">
<?php dynamic_sidebar( 'primary' ); ?>
</div>
<?php endif; ?>sidebar.php. If your theme has a single sidebar, this is all you’ll ever need.sidebar.php template:<?php get_sidebar(); ?>get_sidebar() also accepts a single parameter of $name, which allows you to load a more-specific sidebar template. For example, the code below would call thesidebar-primary.php template.<?php get_sidebar( 'primary' ); ?>primary and secondary. To best organize these, create both a sidebar-primary.php and sidebar-secondary.php template for handling those sidebars.<?php get_sidebar( 'primary' ); ?>
<?php get_sidebar( 'secondary' ); ?>get_sidebar() function when loading a sidebar template.functions.php. You should create a sidebar registration function and hook it to widgets_init. You can see an example of this in the “Registering a dynamic sidebar” section above.register_sidebar() orregister_sidebars() without setting individual sidebar IDs, WordPress auto-creates these IDs by counting the number of registered sidebars and assigning a number as the ID.dynamic_sidebar() and is_active_sidebar().function_exists() check is not needed. I’ve seen this in at least 80% of themes that I’ve looked at. As mentioned earlier in this post, dynamic sidebars have been around since 2007. The only reason to use this to check for sidebar functions is for backwards compability. However, most themes aren’t actually backwards compatible. And, backwards compatibility isn’t something I’d recommend beyond one version back.register_sidebar() function is present as shown below. Forget about this check and simply register the sidebar.if ( function_exists( 'register_sidebar' ) )dynamic_sidebar(). Rather than checking if this function exists, simply call the sidebar.if ( function_exists( 'dynamic_sidebar' ) )include( TEMPLATEPATH . '/sidebar.php' );get_sidebar() for handling this. Always use it as shown in the “Sidebar templates” section above. The reason you should use this function is because a specific hook (get_sidebar) is executed when this template is loaded, which plugins might use to handle specific features.get_sidebar() might not be appropriate for a specialized theme, but it’s something I’ve rarely seen.
|
Labels:
wordpress
|
0
comments
|
|
|
Labels:
wordpress
|
0
comments
|
|
<?php
/*
Template Name: [your page name here]*/
?>
This is a PHP comment. Leave the “Template Name:†in place, but you need to change the name of the page. Once you have done that, upload this new file to your blog theme’s folder.
|
Labels:
wordpress
|
0
comments
|
|
|
Labels:
wordpress
|
0
comments
|
|
Saturday, 9 February 2013
|
Labels:
phpmyadmin
|
0
comments
|
|
Sunday, 3 February 2013
|
Labels:
cakephp
|
0
comments
|
|