The issue with this is that this is a global setting. If you would like to set a different number of posts to display on the front page than on the category page, you can do it by adding this code to functions.php in your theme.

The following code displays 20 posts per page on all pages that are not the front page (index). This includes search results, categories, tag pages, archives, and author listings.

function change_number_of_posts($query) {
	if ( ! is_front_page()) // Make sure it is not the front page
	$query->query_vars['posts_per_page'] = 20; // Change 20 to the number of posts you would like to show
	return $query; // Return our modified query variables
}
add_filter('pre_get_posts', 'change_number_of_posts'); // Hook our custom function onto the request filter

You can change this only for category pages for example with this code.

function change_number_of_posts($query) {
	if ( $query->is_category ) // Make sure it is a category page
	$query->query_vars['posts_per_page'] = 20; // Change 20 to the number of posts you would like to show
	return $query; // Return our modified query variables
}
add_filter('pre_get_posts', 'change_number_of_posts'); // Hook our custom function onto the request filter

The result is that you can set the global setting in the WordPress admin page to 10 posts, which affects the front page (index). You can then insert this code into functions.php and all other pages will display 20 posts.

Note: You do not have to modify your theme other than functions.php for this to work.

If you use any third party WordPress themes, you should check your server for the presence of timthumb.php or thumb.php. It is reported that several theme marketplace websites host common legitimate themes that utilize this library.

The fix is to remove any allowed sites from the thumb.php or timthumb.php files as recommended below.

BEFORE:

$allowedSites = array (
	'flickr.com',
	'picasa.com',
	'blogger.com',
	'wordpress.com',
	'img.youtube.com',
	'upload.wikimedia.org',
	'photobucket.com',
);

AFTER:

$allowedSites = array ();

Please read the full technical details at Mark’s blog in the link above.

One downside to this is that there are several redundant WordPress plugins for common tasks, and their plugin search mechanism which is located at http://wordpress.org/extend/plugins/ is somewhat difficult to use.

I tend to search for the most installed or popular plugins and use the hive mind’s collective research to choose which plugin is the best, most robust, and best supported. Installing the most installed plugin does not always ensure that it is the best plugin, so I tend to test different WordPress plugins from time to time.

Recently, I installed Khang Minh’s XML Sitemap plugin called “Better WordPress Google XML Sitemaps (with sitemapindex and Multi-site support).” This creates a sitemapindex.xml file which references several other sub-sitemaps. This is the new trend in XML sitemaps because there is a 50,000 entry limit for a single sitemap file. By splitting the sitemaps into sub-sitemaps, you can broaden the number of items that you can index.

You can get the plugin from the WordPress plugin project page here. You can also visit Khang Minh’s website at http://betterwp.net/ which also showcases his several other WordPress plugins.

I also want to note that I had a problem with the plugin. The category sitemap wouldn’t generate. I posted a bug report to the issue queue, and he contacted me via Skype and did some testing on my WordPress installation. He found a bug with the code, fixed it, and created a new patch. The problem was with my database, there were several posts had been deleted, but were still categorized as “Uncategorized” which is the default WordPress category for new posts.

This is absolutely the best support I have ever received from a WordPress plugin or Drupal module developer. I have to say that he was a very nice guy, fixed the problem, and devoted his time to not only resolving my individual issue, but creating a patch to fix the particular scenario for the greater community as a whole.

I have not found any problems with any of the other WordPress XML sitemap plugins, but I will use the Better WordPress Google XML Sitemaps (with sitemapindex and Multi-site support) due to the high level of support that Khang Minh provides. His plugins seem solid and he has written and maintains several, so he has a high familiarity with the WordPress framework.

Other XML Sitemap Plugins of note are as follows:

• Google XML Sitemaps – this is the most popular XML Sitemap plugin, but it creates a single sitemap.xml file.
• Yoast’s SEO Ultimate also includes an XML sitemap generator, with very few options.

I found this list of 12 WordPress Plugins to Display and Highlight Code.

I researched a few of them and finally settled on SyntaxHighlighter Evolved, which was simple to install, easy to use with short codes, formats nicely, and seems to have a large existing user base.

In your posts, you can simply use [php] and [/php] shortcodes around your actual PHP code and it does it’s trick. You can review the plugin page for the many various types of languages/syntax that are available.

I will spare your eyes and use this for all embedded code from now on.

After the upgrade, the list price on the product pages had too many zeros. It looked like this.

MSRP $ 49.99000

After a bit of research, I learned that Ubercart has been updated to include more decimal places to accommodate more International currencies.

I took a look at the node-product.tpl.php template and found that the print statement for the list price was using the out of date print statement.

The old print statement looked like:

<?php print $node->list_price ?>

The new print statement looks like this:

<?php print uc_currency_format($node->list_price); ?>

Now all is fine.

MSRP $ 49.99

Setting up the placement of the buttons is pretty trivial. This guide shows you how to generate the widget code for the fan page like box, and this guide shows you how to generate the widget code for the like/recommend button.

Embedded the widget code into the WordPress or Drupal theme is pretty straightforward, and placing it so that it looks right is a matter of simple CSS.

Getting the like/recommend buttons to function properly so that the like action shows up on the user’s Facebook status, which then leads that user’s friends to your website is the difficult part. Additionally, what shows up in that link might not always be what you want.

Ideally, you want the proper page title, a short description under the page title, and a little image to the left of the title and description which is indicative of what the page is about.

You must add Facebook Opengraph meta tags to the pages header for this to work right. This is done by adding the meta tags to the header.php file in your WordPress theme.

That’s easy to do if you just want to set a static image, title, and description for all pages on your site. I’m going to show you how to do that dynamically.

First, let’s assume that we want to have something for the front page, something for pages that have featured images, and something for pages/posts that do not have a featured image. This is done with a PHP if statement and few WordPress short codes.

The first thing that happens is that we set two tags that are always going to be the same no matter what – the fb:admin tag, which is the profile ID of one of the admins of the Facebook Fan Page. The second tag is the URL of the link.

Next, if the front page is liked, then specify the title, default description, and logo.

The next part of the statement says that if the post is a page, and the page has a featured image attached, then use the post title, and featured image. The description is taken from the body field.

The else statement says that for all other pages, use the post title, but use the site’s default logo and description.

You may want to play with these a little bit, but for my project this is what I needed. I’m sure this will get you started and you can figure out the rest in getting the proper look you want on the user’s Facebook status.

See this example below:

<!-- Facebook Opengraph Meta Tags -->
<?php if (have_posts()):while(have_posts()):the_post();endwhile;endif;?>
<meta property="fb:admins" content="#ninedigitprofileidnumber#" />
<meta property="og:url" content="<?php the_permalink() ?>" />
<?php if (is_front_page()){ ?> 
<meta property="og:site_name" content="Your Site's Title" />
<meta property="og:description" content="This is where the description of your site goes, which shows up to the right of the image." />
<meta property="og:type" content="website" />
<meta property="og:image" content="http://www.yourdomain.com/logo.jpg" />
<?php } elseif (is_page() && has_post_thumbnail( $post_id ))  { ?>
<meta property="og:title" content="<?php single_post_title(''); ?>" />
<meta property="og:type" content="article" />
<meta property="og:image" content="<?php echo wp_get_attachment_thumb_url( get_post_thumbnail_id( $post->ID ) ) ?>" />
<?php } else { ?>
<!-- For pages that do not have a thumbnail / featured image, set site's main logo image and default description -->
<meta property="og:title" content="<?php single_post_title(''); ?>" />
<meta property="og:description" content="This is where the description of your site goes, which shows up to the right of the image." />
<meta property="og:type" content="article" />
<meta property="og:image" content="http://www.yourdomain.com/logo.jpg" />
<?php } ?>

I was able to input my URL, such as http://www.symetrikdesign.com with no problem, and the CCK display options are pretty good. However, I wanted to strip the “http://” part on the output display, but have the link remain the legitimate link of http://www.symetrikdesign.com

Though, there are several options for outputting the display in the Admin/Content Type/<content name>/Display fields, there is nothing that handles stripping some characters from the title.

So I figured that I needed to theme the custom field. I searched drupal.org and google.com far and wide and found that though the documentation was present, there wasn’t much of it and it wasn’t that clear.

Here’s what I did.

My field name was called artistwebsite, so I needed to make sure that there was a standard content-field.tpl.php in my theme’s directory and then copy/clone that and call the new file content-field-field_artistwebsite.tpl.php. This works like other types of Drupal entity template files, but the tricky part is that you need to find content-field.tpl.php into your theme’s directory, because it probably isn’t there by default, depending on your theme.

I now have the following in my theme directory, and a field called field_artistwebsite in my content type.
content-field.tpl.php
content-field-field_artistwebsite.tpl.php

I was able to re-write the output of a CCK Link field so that it removes the “http://” on the display title on the node.

I did this by adding the following lines of code in place of the commented out print statement below:

<?php $item['display_title'] = str_replace("http://","",$item['display_title']);
          echo "<a href=\"".$item['url']."\">".$item['display_title']."</a>";
         
/* Here is the original PHP print statement line in the stock/default content-field.tpl.php
*  file that I commented out and replaced with what is above.
* <?php print $item['view'] ?>
*/
?>

This assumes that you previously had the Delicious bookmarks add-on working in Firefox 3.6.x and you have just upgraded to Firefox 5.0 – which disables the add-on and states that it is incompatible with Firefox 5.0

• Open Firefox
• Goto “Help” in the Menu, then “Troubleshooting Information”
• Click on the “Open Containing Folder” or “Show in Finder” button (within the box “Application Basics” on top of the page)
• Close Firefox
• Goto into directory “extensions\{2fa4ed95-0317-4c6a-a74c-5f3e3912c1f9}”
• Edit install.rdf and change the following from the first line to the second line

• Restart Firefox

I had this working fine for two fields called price and dimensions. The issues was that the output is a line of text, so all of the items were being displayed on one line and then wrapping to the next line even though there were page breaks in the fields themselves.

For the price field.
$159.99 for two nights.
Add one more night for $49.99

The output looked like:
$159.99 for two nights. Add one more night for $49.99

I fixed this in the page template file by adding the following code around the get statement.

wpautop

So my statement looked like:

<div class="price"><?php echo wpautop(get_post_meta($post->ID, 'Price', true)); ?></div>

Now the output looks like I want:
$159.99 for two nights.
Add one more night for $49.99