This video covers the answer to “Is WordPress easy to use?”

For more about using WordPress, its setup, and what you’ll need to get started, see our Getting Started with Web Hosting page.

For this, we will assume you have signed in at Inlinkz.com and upgraded to a premium account (only $19.99 per YEAR- amazing!)

Lets set up the situation: you have a website that accepts submissions of a Wordless Wednesday, or Menu Plan Monday, or any other theme.  Using Inlinkz, you can let your readers submit their own posts.  Here’s how to set it up:

1.  Sign into Inlinkz.com.

2.  Click on “Create new collection”

3.  Give your new collection a name (no one but you will see it).

4.  Enter a description that will be displayed on your post/page.  Here is where you can welcome them, provide a link to any rules and instructions for your readers to link back to you(covered below).

5.  Then set a description for others at Inlinkz to find your ‘meme’/collection.

6.  How long will this collection be open?  And will you be repeating this every week or month?

7.  Select “Thumbs” for the image linkies, or “Links” for plain link collection.

8.  Select number of columns (3 works well)

9.  Select size of images (150px works well for larger images, 3 across)

10.  Show just a clickable image, or also a name & image.

11. Select whether the most recent (last) link should be at the top or bottom of the list.

12.  Check for email notifications whenever anyone posts a new link. This will automatically go to the account holder.

13.  Here you also decide if users will be emailed a notification of the new link, and if they will be allowed to delete the link once submitted.

14.  Then click Submit.

15.  Return to the dashboard, and click on “Advanced Options” under the new collection.

16.  Allow permalinks (1): this means the link may NOT go to a main site like desperatelyseekingwp.com, instead it has to link to the real post, like: desperatelyseekingwp.com/2012/01/how-to-use-inlinkz

17.  Require Link Back (2): this means the new link will not live until Inlinkz detects a link back to your site in the linked post.  It will specifically look for the link you put in the next box (3).

18.  Moderation on new entries: new links will NOT go live, until you visit inlinkz, and approve them.

19.  Go back to dashboard (via link at top of page), and click “get script” link under the new collection.

20.  Copy this box (Code n.1)

21.  Open your post or page in your WordPress dashboard.  Open the html tab:

22.  Paste your code where you’d like the collection & submission form to be displayed.

23.  Update, and view the page/post to view the submission form.  Test the form by uploading a new image.

Step Zero:  Prepare Blogger

Have blogger feeds at Full.  And comment feeds at Full.

Step One: Download Atom Files

1. Download the Blogger Backup Utility that comes with a nice easy setup wizard.
2. Settings: Save Comments [Y], Save posts as:  [Atom, all posts in single file]  Max Posts: [100 Posts per file]  Get only recent Posts: [No Limit - Get them All].
3. Download your backups to a memorable folder ( “Transfer” in the Downloads folder for ease of use – for me, it looks like C:\Users\Sony\Downloads\Transfer ).

Step Two: Download a Conversion Utility

Because there are NO import tools to import Atom to WordPress, we have to convert it to RSS and then we can use the RSS upload utility.  But you’re gonna have to use the command line (if you dont know what that is, I’ll show you in a moment).  This tutorial is for Windows Users.

1. First you have to have the Microsoft XML utility.  (I’m not sure if thats built in or not.  Just download this to be sure.)  Select the first one and set it up on your computer (has set up wizard)
2. Download the MSXSL utility and save it to the Downloads\Transfer folder.

Step Three: Download Atom 2 Rss Transformation Stylesheet. 

Another thing that I’ve just become aware of, is that you can take an Atom XML file and convert it to an RSS XML (both types of XML formatting) using an XML stylesheet.  Thank heavens we dont have to learn how to create these, as the work was done for us by geekhood.net.

1. Navigate to Atom2Rss.xsl
2. Click on “View Source”
3. Copy that and paste into a text editor (not Word Processor).
4. Save as atom2rss.xsl into our Downloads/transfer folder

There should now be the XML (atom) files from the backup, the msxsl.exe file, and the atom2rss.xsl file in the downloads/transfer folder.

Step Four: Executing the Conversion

Now you have to use the dreaded “command line”.  It will bring back the days of the TRS-80 and give you nightmares of blinking cursors, but it is the only way that I found to do this.

To open a command line window, navigate to the start button, in the search box at the bottom, type “cmd” no quotes.  It will show one option with the scary black box icon.  Click it.

Remember our old commands?  dir will give you a list of the contents of the directory;  cd will let you change directory?  My default location is c:\Users\Sony.  So to get to our new transfer folder, I type:

cd downloads/transfer

To execute the conversion for each file, where my first backup file is backupfile1.xml, I typed this:

msxsl.exe -o newbackup1.rss backupfile1.xml atom2rss.xsl

And voila, the new file in rss format – newbackup1.rss is created in the transfer directory!

*props to Darren for the commands here!

Step Five: Import to WordPress

Then the easy part – navigate to Tools> Import > RSS and follow the steps to download the importer and run the plugin.  Select each of your new files in turn to upload into WP.

If you’ve been thinking about purchasing the StudioPress / Genesis package, and humming and hawing over it – now is the time!  The price is going up next month!  We are not usually early adopters into software – I like to play it safe for a little while – see how it does, if support is going to wane, what the reviews are going to be like.

Mashable calls Genesis the “best of the best” among premium frameworks.

Adopting early into StudioPress has been one of the best decisions of my career!

Here’s what you get for $299 at the moment:

• incredible support!! Way beyond the normal support in forums – these developers expect that Genesis will be taken and twisted to our clients’ needs and are ready to help.
• 44 professionally designed themes (with PSDs)
• unlimited upgrades to each and every one (they tend to keep the child themes updated before adding new ones – so the child themes are always up to date both design-wise and code-wise)
• Search Engine Optimized by Greg Boser (we still use SEO for WP by Yoast plugin)
• Secured code by Mark Jaquith
• small selection of custom widgets, we add some more of our own
• Free upgrades for life (Genesis 1.8 came out with built-in responsiveness)
• Free themes for life (see #2) & any additional ones
• Over 65,000 installations so far, so people like Bill Erickson and Nick the Geek are developing awesome advanced tutorials

Get 10% off Genesis

Before the price increases January 31!  

Use discount code TEN to get 10% off between now and then.  If you can edit php, and you are a WordPress developer – this is a must!

1.  Step One: Log into Flickr

2.  Step Two: Click on Share

When you click on Share – > More share options, get the BBcode – and it will look something like this:

[url=http://www.flickr.com/photos/27186552@N08/3991626682/][img]http://farm3.staticflickr.com/2592/3991626682_d372402407.jpg[/img][/url]
[url=http://www.flickr.com/photos/27186552@N08/3991626682/]blue rose[/url] by [url=http://www.flickr.com/people/27186552@N08/]o2cathy[/url], on Flickr 

3.  Step Three: Paste into Post

You have two options.  If you want to place the image (as is), you can use the regular flickr link:

http://www.flickr.com/photos/27186552@N08/3991626682/ 

 Paste this link into the visual editor where you want the image to show up.

If you’d like to use the image with the built-in WordPress capabilities – to align it in the text, add borders, titles, and captions, then you need the actual image – not the flickr link.  The image link is the one that ends in …..jpg.

Like this: http://farm3.staticflickr.com/2592/3991626682_d372402407.jpg  

Because this is an actual IMAGE link, you can use the “add an image” button in your post editor, found here:

And click on the “From URL” tab here:

Add your URL, a title (for good SEO), alternate text – for voice browsers, a caption (optional), alignment, and a link.  Then click Insert into Post.

Questions?

Then use Batch Cat by Lenin Lee to add /edit / remove the appropriate terms from the posts in bulk.

I just edited several hundred categories and 1,700 posts in about 30 minutes.

We heart plugin authors!

Version 3.0 of the Google Analytics API 3.0 implements the OAuth 2.0 protocol. Among the benefits of OAuth are the fact that applications don’t have to store user credential information, and that users can revoke an application’s permissions at any time. However, the OAuth authorization process can be a bit more involved compared to some other API approaches. Also, the Google documentation is a bit light in terms of summarizing the process for server-side data access.

This how-to will use PHP to make the server-side calls to the Google Analytics API, which returns information in the JSON format. The code examples assume that you have cURL for PHP installed, and that you are using PHP 5.2.0 or later in order to use the json_decode function to parse the Google responses.

The setup steps are as follows: We will first set up the application in the Google API console. Then we’ll authorize the application with a Google account that has access to your site’s data. Using the resulting authorization code, we’ll request a refresh token from Google.

From there, you can build the application part: The refresh token is used to get access tokens that are finally used to actually read the data from Google. The details of implementing the data for the widget will be left up to you.

Google API console setup

Log in to the Google API console with a Google account. Note that the account that you log in with here does not need to be the same account that has access to your site’s data.

At the top of the left menu, create a new API project in the dropdown list:

Once your new project is created, select the “Services” page from the left menu, and turn on the Google Analytics API:

Note that there are per-day query limits for each API service.

Select the “API Access” page from the left menu, then create a web application client.

The name of the web application client will be displayed to the user (you) later when you authorize the application.

You will need both the client ID and client secret later, used in a PHP script accessible at the redirect URI, which you can rename to add the “.php” suffix as necessary.

If you need to access data server-side when an authorized user is not logged in, the web application client is not sufficient. You also have to create a server API key, limited to the IP address(es) of your server(s):

Authorize the application

Next, you’ll have to authorize the application to access your Google Analytics data. Remember that the account that created the API application does not have to be the same account that has access to your site’s data.

To prompt the user (you) to authorize your application, you have to build the authorization URL. First, however, we should build a very basic script at the configured redirect URI. The first iteration of the script has this code at http://www.theblog.ca/oauth2callback.php:

<?php
    var_dump( $_REQUEST );
?>

This is simply going to output to your screen the raw data that is being sent to the script via either POST or GET parameters. It is not the complete script yet, but will be used for illustrative purposes.

To build the authorization URL (which is a set of GET parameters at the URL https://accounts.google.com/o/oauth2/auth), you’ll need the following information, which is as follows for our example application:

• Callback URL: http://www.theblog.ca/oauth2callback.php
• Client ID: 63311316168.apps.googleusercontent.com
• Client secret: _iXNRZ5zMj1beMTab0wA4lXC

You will also need to specify a response type (always “code”), the type of access you are requesting (“offline” since we are accessing the data in the background without user intervention), and a “scope” specific to Google Analytics. See the Google API OAuth 2.0 documentation for information on the URL parameters and the resulting response.

For our example application, the authorization URL is:

https://accounts.google.com/o/oauth2/auth?response_type=code&client_id=63311316168.apps.googleusercontent.com
&redirect_uri=http://www.theblog.ca/oauth2callback.php&access_type=offline
&scope=https://www.googleapis.com/auth/analytics.readonly

Get the permanent refresh token

When you access the authorization URL, it should prompt the user (you) to allow the application to access the site data. Once you click the authorization button, you should be redirected to your authorization URL, which you will discover has the “code” GET parameter. You will have to use the value of that GET parameter to ask Google for the refresh token.

Our example uses cURL to build the refresh token request, whose URL uses a similar format to the authorization URL, posting a set of fields to https://accounts.google.com/o/oauth2/auth. According to the Google API OAuth 2.0 documentation, you’ll need the client ID, client secret, and redirect URI information from before, as well as the “code” and an extra field “grant_type”, which is always “authorization_code”.

In oauth2callback.php, use the following code:

<?php
if( isset( $_GET['code'] ) )
{
    $ch = curl_init();
    $timeout = 5;
    curl_setopt( $ch, CURLOPT_URL, 'https://accounts.google.com/o/oauth2/token' );
    curl_setopt( $ch, CURLOPT_POST, 1);
    curl_setopt( $ch, CURLOPT_POSTFIELDS, 'code=' . $_GET['code']. '&client_id=63311316168.apps.googleusercontent.com&client_secret=_iXNRZ5zMj1beMTab0wA4lXC&redirect_uri=http://www.theblog.ca/oauth2callback.php&grant_type=authorization_code');
    curl_setopt( $ch, CURLOPT_RETURNTRANSFER,1 );
    curl_setopt( $ch, CURLOPT_CONNECTTIMEOUT, $timeout );
    $data = curl_exec( $ch );
    curl_close( $ch );
    $result = json_decode( $data, true );
    var_dump( $result );
}
else
{
    var_dump( $_REQUEST, true );
}
?>

Note that we are once again using a quick and dirty “var_dump” to output the returned information on the screen. If you visit the same authorization URL in your browser once again, you should get redirected to the same URL as before, but this time showing the response from the extra request for the refresh token. This response should, of course, contain the refresh token.

One extra note: to see which applications you’ve authorized under a Google account, you can go to this URL: https://accounts.google.com/IssuedAuthSubTokens, where you can also revoke access, forcing the application(s) to ask for your authorization again.

Use the refresh token and access the data

The refresh token is the most important piece of information, as it is essentially the permanent key that you need to access the Google Analytics data. (It is permanent as long as the user account that authorized the application does not revoke access.) The more accurate description is that the refresh token is used to get a time-limited access token, and that the access token is used along with the API key you had set up, valid only for specific IP addresses, to access the data.

In our example, the refresh token is:
1/7DRzjcqm-ypH9By1FrY3T-l_oSW3KdklC0LJuZLk5Q0

The following example script is a framework for what you would use with your website, and assumes that you are running it periodically, about once an hour, and therefore you need to ask for a new access token every time. A Google Analytics access token typically has an expiry of just over 1 hour, and thus you can use it for more than 1 request within that hour.

The script gets the top 10 pages based on pageviews for the past 1 day.

<?php

// First, ask for an access token using the refresh token
$ch = curl_init();
$timeout = 5;
curl_setopt( $ch, CURLOPT_URL, 'https://accounts.google.com/o/oauth2/token' );
curl_setopt( $ch, CURLOPT_POST, 1);
curl_setopt( $ch, CURLOPT_POSTFIELDS, 'refresh_token=1/7DRzjcqm-ypH9By1FrY3T-l_oSW3KdklC0LJuZLk5Q0&client_id=63311316168.apps.googleusercontent.com&client_secret=_iXNRZ5zMj1beMTab0wA4lXC&grant_type=refresh_token');
curl_setopt( $ch, CURLOPT_RETURNTRANSFER,1 );
curl_setopt( $ch, CURLOPT_CONNECTTIMEOUT, $timeout );
$data = curl_exec( $ch );
curl_close( $ch );
$result = json_decode( $data, true );

/*
You should get a response like this in the result:
{
  "access_token":"1/fFBGRNJru1FQd44AzqT3Zg",
  "expires_in":3920,
  "token_type":"Bearer",
}

Then, you can use that access token to build queries (see http://code.google.com/apis/analytics/docs/gdata/gdataExplorer.html or http://code.google.com/apis/explorer/#_s=analytics&_v=v3 for examples):
*/

if( isset( $result['access_token'] ) )
{
    // Look up only the last day of visits
    $endDate = date( 'Y-m-d' );
    $startDate = date( 'Y-m-d', strtotime( '-1 day' ) );
    /*
        "ids" value comes from this URL in the last portion of the URL, after the "p": https://www.google.com/analytics/web/#dashboard/default/a381759w192893p9122283/
        Or use http://code.google.com/apis/analytics/docs/gdata/gdataExplorer.html to show the GA ID for each your Analytics accounts
        "key" is the API key that you'd set up in the Google APIs console, restricted to certain IP addresses
    */
    $url = 'https://www.googleapis.com/analytics/v3/data/ga?' . 'key=AIzaSyDyWgfb45VYfVYdVnmpH4JZCCRNas5P0SE&ids=ga:9122283&start-date=' . $startDate . '&end-date=' . $endDate . '&metrics=ga:pageviews&sort=-ga:pageviews&dimensions=ga:pagePath&max-results=10';
    $ch = curl_init();
    $timeout = 5;
    curl_setopt( $ch, CURLOPT_URL, $url );
    curl_setopt( $ch, CURLOPT_HTTPHEADER, array( 'Authorization: Bearer ' . $result['access_token'] ) );
    curl_setopt( $ch, CURLOPT_RETURNTRANSFER,1 );
    curl_setopt( $ch, CURLOPT_CONNECTTIMEOUT, $timeout );
    $data = curl_exec( $ch );
    curl_close( $ch );
    $mostViewedRaw = json_decode( $data, true );
    var_dump( $mostViewedRaw );
}
?>

From here, it is up to you to use the returned data in ways that best suit your needs and application. For example, for performance reasons and API call limitations, you might want to run the script only about once an hour, and store the results in a database table or a data structure specific to your content management system. You might also want to do some extra filtering on the Google Analytics results to only display certain types of pages (omitting the front page, for example). Note that the resulting Google Analytics data is simply output to the screen in our example so that you can see its structure and determine how to use it to suit your needs.

… how to remove the website section when leaving a reply/comment …

The solution may be obvious to some and can be readily derived from the information found on the WordPress codex page for the `comment_form` function, but if you are new to WordPress and/or not familiar with writing a function to use with `add_filter`, here is a very simple and working snippet to use in your theme:

function wpfa_remove_comment_website_section(){
    $commenter = wp_get_current_commenter();
    $req = get_option( 'require_name_email' );
    $aria_req = ( $req ? " aria-required='true'" : '' );
    $fields =  array(
        'author' => '<p class="comment-form-author">' . '<label for="author">' . __( 'Name' ) . '</label> ' . ( $req ? '<span class="required">*</span>' : '' ) .
                    '<input id="author" name="author" type="text" value="' . esc_attr( $commenter['comment_author'] ) . '" size="30"' . $aria_req . ' /></p>',
        'email'  => '<p class="comment-form-email"><label for="email">' . __( 'Email' ) . '</label> ' . ( $req ? '<span class="required">*</span>' : '' ) .
                    '<input id="email" name="email" type="text" value="' . esc_attr(  $commenter['comment_author_email'] ) . '" size="30"' . $aria_req . ' /></p>',
        'url'    => '' /** removes website section */,
    );
    return $fields;
}
add_filter( 'comment_form_default_fields', 'wpfa_remove_comment_website_section' );

Ideally, this will be placed in the ‘functions.php’ file of your theme, but better yet this should be included in the Child-Theme you created of the theme you want to modify.

function wps_set_content_type(){
    return "text/html";
}
add_filter( 'wp_mail_content_type','wps_set_content_type' );

Visit wpsnipp.com for details on how to setup this WordPress snippet.

Share this post.

add_action( 'admin_init', 'wps_cpt_support' );
function wps_cpt_support() {
	remove_post_type_support( 'post', 'title' );
	remove_post_type_support( 'post', 'comments' );
}

Visit wpsnipp.com for details on how to setup this WordPress snippet.

Share this post.

It’s not so much that 2.0 is any sort of milestone, per se, as I generally follow a similar version numbering system as WordPress; although I must admit there was definitely a push to do something significant because it is a point-zero release after all.

That being said, I added the functionality of some of the core supported post-formats (aside, quote, and status), which was the big push for this release, as well as improving the overall typography.

For a full list of the changes, please have a look at the changelog below.

© 2012, BuyNowShop. All rights reserved.

Related posts:

1. Desk Mess Mirrored 1.8.3 is Live
2. Desk Mess Mirrored 1.9.1
3. Desk Mess Mirrored 1.4.5

function top_comment_authors($amount = 5) {
global $wpdb;
$results = $wpdb->get_results('
    SELECT
    COUNT(comment_author_email) AS comments_count, comment_author_email, comment_author, comment_author_url
    FROM '.$wpdb->comments.'
    WHERE comment_author_email != "" AND comment_type = "" AND comment_approved = 1
    GROUP BY comment_author_email
    ORDER BY comments_count DESC, comment_author ASC
    LIMIT '.$amount
);
$output = "<ul>";
foreach($results as $result) {
    $output .= "<li>".$result->comment_author."</li>";
}
$output .= "</ul>";
echo $output;
}

<? top_comment_authors(); ?>

Visit wpsnipp.com for details on how to setup this WordPress snippet.

Share this post.

check out our list of the 12 Essential Plugins for 2012!

Button

And then don’t forget to follow the conversation on twitter at #savvyblogging.  A lot of great questions & answers are posted there daily.

How do you set this up?

Easy-peasy – just install multisite.

Sure, there’s a few little extras, but that’s the bulk of the work. You can choose to change your main site into a network, or you can install multisite off in a subfolder or subdomain so it’s separate from your main site, and pick the subfolder install for ease of use and so it looks like just pages off the main install. Your visitors will not really notice a difference, especially if the main site in the network has a theme that matches your original single site. With it separate, you can also let some clients in the whole install without letting them in to your main (separated) site. Access to sub sites can be controlled on a per user basis (this is built in to multisite remember).

So now you have multisite set up – let’s say on a subdomain. Just install all the themes you want to demo. I usually do it in bulk using FTP, then I go network enable all the themes.

Now, create your sub sites. I give each site the name of the theme – that makes it easy to remember and almost painfully obvious. WordPress.com even does the same thing for its theme demos. (click the “See it in action” button on any theme there.)

Visit the admin area of each site, activate the required theme, import the demo content, drag some widgets around, do some menus – whatever you like. The good part is here you can have generic text for all or use special demo text on each site, listing the theme’s features.

For navigating between the sub sites, you can use Diamond multisite widgets and use the blog listing widget on every site to go back and forth between them. Or use custom links on your custom menu and type in each blog link.

But hey – that also sounds like work. You could set up one demo site and assuming you want to use most of the same content, use a plugin like the Replicator to make a copy of that template site every time you create a new site. Our Network Home pages ebook also has a section on how to include a site listing that updates itself.

Another use-case for this same setup is if you are developing several themes at once. Why use separate installs? Slap up multisite somewhere, close off registration – even lock it down via privacy plugins and work away in happiness. The admin bar makes it super easy to switch between sub sites.

So – who is going to try this first?

© andrea for WordPress "Must-Use" Tutorials, 2012. | Permalink | 5 comments | Add to del.icio.us
Post tags: client, customers, demo, paid, premium, shop, Themes, white label

Check out WPeBooks.com for multisite plugins & ebooks.

Feed enhanced by Better Feed from Ozh

function add_custom_types_archive( $query ) {
if( is_category() || is_tag() && empty( $query->query_vars['suppress_filters'] ) ) {
$query->set( 'post_type', array(
 'post', 'your-custom-post-type-here'
            ));
      return $query;
    }
}
add_filter( 'pre_get_posts', 'add_custom_types_archive' );

Visit wpsnipp.com for details on how to setup this WordPress snippet.

Share this post.

function wps_admin_bar() {
    global $wp_admin_bar;
    $wp_admin_bar->remove_menu('wp-logo');
    $wp_admin_bar->remove_menu('about');
    $wp_admin_bar->remove_menu('wporg');
    $wp_admin_bar->remove_menu('documentation');
    $wp_admin_bar->remove_menu('support-forums');
    $wp_admin_bar->remove_menu('feedback');
    $wp_admin_bar->remove_menu('view-site');
}
add_action( 'wp_before_admin_bar_render', 'wps_admin_bar' );

Visit wpsnipp.com for details on how to setup this WordPress snippet.

Share this post.

<?php
/************* SHORTCODES ****************/
//
function showBlogPosts( $atts ) {
	extract( shortcode_atts( array(
	// what categories to show, default = all.
		'cat' => '',
	// number of posts
		'num' => 5,
		'p' => '',
	// The following variables work on an "on/off" switch, 1 to allow, 0 to disallow
	// excerpt or content. default = excerpt
		'excerpt' => 1,
	// show meta or not. default = yes
		'meta' => 1,
		'meta2' => 1,
	//paged. default on no. Determines if page should be paginated or not
		'pnavi' => 0
	), $atts ) );
	global $loopMeta, $loopExcerpt, $loopMeta2;
	$loopMeta = $meta;
	$loopExcerpt = $excerpt;
	$loopMeta2 = $meta2;
	if ($p != ''){
	$posts_per_page = '';
	}
 wp_reset_query();
global $paged;
$args = array( 'posts_per_page' => $num, 'cat'=> $cat, 'p' => $p );
if($pnavi == 1){
$args['paged'] = get_query_var('page');
}
query_posts($args );
 while ( have_posts() ) : the_post();
/* for the loop part, use your own loop.php that contains only the post format.
** See my "micrLoopPart.php" to see how all the options play out
*/
include(locate_template('microLoopPart.php'));
   endwhile;
if($pnavi == 1){
echo'<div id="blogNav">';
posts_nav_link( ' ', '&raquo;', '&laquo;' );
echo '</div>';
}
 wp_reset_query();
}
add_shortcode( 'blogPosts', 'showBlogPosts' );
?>

Create a new template file called microLoopPart.php and add the following micro formatted loop.

<article id="post-<?php the_ID();?>" <?php post_class($classes);?> ><!-- START OF POST -->
      <h1 class="entry-title"><a href="<?php the_permalink() ?>" rel="bookmark" title="<?php the_title_attribute(); ?>" class="url">
        <?php the_title(); ?>
        </a></h1>
      <span class="meta vcard" style=" <?php if($loopMeta == 0){ echo "display:none"; }?> ">
      <time class="updated" datetime="<?php
$postDate = get_the_date('c');
$postDate2 = get_the_date('d.m.Y');
echo $postDate ?>" pubdate> <?php echo $postDate2; ?></time>
      | <span class="byline fn author">
      <?php the_author_posts_link(); ?>
      </span> | <a href="mailto:<?php the_author_meta('email'); ?>" class="email author">email</a> |
      <?php the_category(', '); ?>
      </span></span>
      <div class="postContent entry-content">
         <?php
		if($loopExcerpt == 0){
		the_content();
		}
		else{
			if ( has_post_thumbnail() ) {
			 the_post_thumbnail('thumbnail', array('class' => 'alignleft'));
			}
		the_excerpt();
	   	echo '<div class="clearfix"></div>';
		}
		?>
        <p class="postmetadata" style=" <?php if($loopMeta2 == 0){ echo "display:none"; }?> ">Posted in
          <?php the_category(', '); ?>
          <br />
          <?php the_tags(); ?>
          <br />
          Source: <span class="vcard"><span class="source-org copyright">
          <?php bloginfo('name'); ?>
          </span></span></p>
      </div>
    </article>

Place the following shortcode within your blog posts to display a micro formatted list of posts.

[blogPosts cat=3 excerpt=0 meta=1 meta1=0 num=2]

Visit wpsnipp.com for details on how to setup this WordPress snippet.

Share this post.

function add_theme_caps() {
   $role = get_role( 'author' );
   $role->add_cap( 'edit_others_posts' );
}
add_action( 'admin_init', 'add_theme_caps');

Visit wpsnipp.com for details on how to setup this WordPress snippet.

Share this post.

add_filter('widget_title', 'change_widget_title', 10, 3);
function change_widget_title($title, $instance, $wid){
    return $title = str_replace('Widget Title', '<span style="color: red">Custom</span>', $title);
}

Visit wpsnipp.com for details on how to setup this WordPress snippet.

Share this post.

function commentCount($type = 'comments'){
	if($type == 'trackbacks'):
		$typeSql = 'comment_type = "trackback"';
		$oneText = 'One :trackback';
		$moreText = '% :trackbacks';
		$noneText = 'No :trackbacks';
	elseif($type == 'pingbacks'):
		$typeSql = 'comment_type = "pingback"';
		$oneText = 'One :pingback';
		$moreText = '% :pingbacks';
		$noneText = 'No :pingbacks';
	endif;
	global $wpdb;
    $result = $wpdb->get_var('
        SELECT
            COUNT(comment_ID)
        FROM
            '.$wpdb->comments.'
        WHERE
            '.$typeSql.' AND
            comment_approved="1" AND
            comment_post_ID= '.get_the_ID()
    );
	if($result == 0):
		echo str_replace('%', $result, $noneText);
	elseif($result == 1):
		echo str_replace('%', $result, $oneText);
	elseif($result > 1):
		echo str_replace('%', $result, $moreText);
	endif;
}
add_filter('manage_posts_columns', 'posts_columns_counts', 1);
add_action('manage_posts_custom_column', 'posts_custom_columns_counts', 1, 2);
function posts_columns_counts($defaults){
    $defaults['wps_post_counts'] = __('Counts');
    return $defaults;
}
function posts_custom_columns_counts($column_name, $id){
	if($column_name === 'wps_post_counts'){
		commentCount('trackbacks'); echo "<br />";
		commentCount('pingbacks');
          }
}

Visit wpsnipp.com for details on how to setup this WordPress snippet.

Share this post.