WordPress version 3.0 will make creating custom post types extremely simple. But, the techniques I’ll point out in this tutorial can be used with previous versions of WordPress.

Changing the post type on the home page

By default, WordPress shows the post post type on your home page. Let’s suppose we want to show several post types in addition to posts:

• page (yes, regular pages)
• album
• movie
• quote

To add these, open your theme’s functions.php file and paste this PHP code into it:

add_filter( 'pre_get_posts', 'my_get_posts' );

function my_get_posts( $query ) {

	if ( is_home() )
		$query->set( 'post_type', array( 'post', 'page', 'album', 'movie', 'quote', 'attachment' ) );

	return $query;
}

That’s all there is to it.

You may have noticed the addition of the attachment post type even though I didn’t mention adding it. This is something I highly recommend adding if you’ll be showing any attachment images on your home page For example, if you have a gallery on your home page, the images won’t appear without adding the attachment post type.

Showing the post types in your feed

Realizing that many of you might want to also add these post types to your feed to match your blog, a small change in the code is required. All you need to do is change this line:

if ( is_home() )

We’ll use the is_feed() conditional tag:

if ( is_home() || is_feed() )

Now, you can have custom post types in your regular blog post rotation and your feed. Enjoy and look for more custom post type tutorials soon.

If you’ve ever used a theme of mine, you know I love adding widget areas everywhere. And, I know this can be confusing for some people.

Fortunately, WordPress 2.9 will allow theme developers to add a description for each widget area. This should help end users figure out what the heck is going on.

Widget descriptions from a user’s view

If you’re an end user and your theme author has added descriptions, you’ll see the description near the top of the widget area on the Widgets admin screen.

Adding descriptions to widget areas

If you’re a theme developer, adding descriptions to your widget areas is as simple as adding an extra argument to the register_sidebar() function. Use the below PHP code as a guide.

add_action( 'init', 'register_my_widget_areas' );

function register_my_widget_areas() {

	register_sidebar( array(
		'name' => __('Primary', 'example'),
		'id' => 'primary',
		'description' => __('The main widget area, most often used as a sidebar.', 'example'),
		'before_widget' => '<div id="%1$s" class="widget %2$s widget-%2$s">',
		'after_widget' => '</div>',
		'before_title' => '<h3 class="widget-title">',
		'after_title' => '</h3>'
	) );
}

The new code allowed in 2.9 is the description argument.

'description' => __('The main widget area, most often used as a sidebar.', 'example'),

Theme authors, it’s time to implement this new feature for your users. It will take less than five minutes to add to your theme and should at least cut back on a few support queries.

In this tutorial, I’ll be covering the various things you can do with the post image feature. Some things will be specific to end users while others will be useful for theme and plugin developers.

One important thing to note is that this new feature is an image-based representation of a post. The image itself is directly tied to your post. You shouldn’t think of it as something different than that.

How does an end user make use of this feature?

First, your theme must add support for it. Otherwise, you won’t be able to use it. At this point, let’s assume that your theme does support it. I’ll go over instructions for theme authors later.

To use this feature, you must be within the post editing screen of your WordPress admin. On this screen, you’ll see a new meta box labeled “Post thumbnail” (or “Page thumbnail” for pages). There’ll be a link to “Set thumbnail,” which will allow you to use the media uploader to load a new image.

It’s not just for thumbnails

Even though it is called “post thumbnails,” we can technically use the feature for all sorts of things (e.g., feature images, medium-sized images for the front page, etc.).

By default, WordPress gives you several image sizes each time you upload an image. These image sizes are:

• Thumbnail
• Medium
• Large
• Full (the image you uploaded)

Some plugins even extend this by allowing more intermediate sizes. The important thing is that you understand that more than thumbnails can be used here.

How to add support for the post image feature in a theme

Theme authors, I’m going to make this simple for you. You only need one line of code to turn this feature on for your users. Add this to your theme’s functions.php file:

add_theme_support( 'post-thumbnails' );

Or, you can register support for specific post types. For example, let’s suppose you wanted to add thumbnail support for both the post and movie post type but not for the page post type. You’d use this instead:

add_theme_support( 'post-thumbnails', array( 'post', 'page' ) );

Of course, that one line doesn’t actually add anything to the front end for you. You’ll need to call the image somewhere within The Loop in your template files. For example, you might want to add thumbnails to your category archives. You’d do this by adding this line of code:

<?php the_post_thumbnail( 'thumbnail' ); ?>

Or, maybe you have a section on a special template that calls for medium-sized images:

<?php the_post_thumbnail( 'medium' ); ?>

Or, a huge sliding feature area on your front page and need the full-sized image:

<?php the_post_thumbnail( 'full' ); ?>

That’s all there is to it. As a theme author, you can hand over some powerful functionality to your users with just a couple of lines of code.

The rest of this tutorial will focus on developer features and some options for using older images.

Checking if the post has an image

Sometimes, you may need to check if a post has an image. There’s a function for that called has_post_thumbnail(), which will return true or false based on whether there’s an image.

In this example, we’ll check if there’s an image. If there’s not, we’ll show a default image instead.

<?php
	if ( has_post_thumbnail() )
		the_post_thumbnail( 'thumbnail' );
	else
		echo '<img src="default-image.png" alt="Example Image" title="Example" />';
?>

Getting the post image ID

Maybe you need to write your own custom script but still want to allow users to upload their own images. You can grab the post image ID and use it. This ID is saved as the meta value for the meta key _thumbnail_id. It is the ID of the attached file.

You only need to call the function in your code like so:

$image_id = get_post_thumbnail_id();

How to return the image instead of displaying it

In some scenarios, you might want to return the post image for use in your PHP code instead of displaying it.

Here’s an example of that functionality:

$image = get_the_post_thumbnail( $post->ID, 'thumbnail' );

How to filter the image size

Some plugin developers may want to filter the image size (or maybe even child theme authors). The post_thumbnail_size filter hook is available for that. The filter function below is for changing the thumbnail size to medium.

Add this PHP code to your theme’s functions.php file or your plugin file:

add_filter( 'post_thumbnail_size', 'my_post_image_size' );

function my_post_image_size( $size ) {
	$size = 'medium';
	return $size;
}

Changing the HTML output of the post image

There may be some scenarios where you’ll want to change the HTML markup of the displayed image. In this example, I’ll show you how to wrap the image with a link to the post.

Add this PHP code to your theme’s functions.php file or your plugin file:

add_filter( 'post_thumbnail_html', 'my_post_image_html', 10, 3 );

function my_post_image_html( $html, $post_id, $post_image_id ) {

	$html = '<a href="' . get_permalink( $post_id ) . '" title="' . esc_attr( get_post_field( 'post_title', $post_id ) ) . '">' . $html . '</a>';

	return $html;
}

What happens to my old images/thumbnails?

If you’re like me and many others, you may have been using custom fields to add images to your posts for years. If you switch to this new method, everything will be lost.

I’ve got a solution for this problem: The Get the Image plugin.

Version 0.4 will be released when WordPress 2.9 is out. Not only will support be added for the new WordPress post image feature, but you won’t lose all of the hard work you’ve put in. The plugin will have the ability to check for post images in five different ways (in the below order):

• Custom fields.
• New post image feature.
• Attached image.
• Scan the post for images.
• Default image.

For those of you already using this plugin or a theme of mine that includes the script, you’ll only have to upgrade the plugin or theme. The feature will be turned on for you by default, so you will be able to start using the new feature without touching anything but an upgrade button.

Have fun with your new post images

I hope this tutorial has given you an in-depth look at the post image feature. There are some limitations, but on the whole, this feature will make things much easier for end users compared to the currently-available methods.

If you’re a user of my Get the Image plugin or Hybrid theme, look out for an update within a few days of WordPress 2.9. You’ll be able to start using the post image functionality soon.

In this tutorial, you’ll learn how to utilize the add_meta_box() functionality to add two things to your pages:

1. Excerpt box.
2. Custom taxonomies boxes.

Being able to add these meta boxes to pages isn’t the limit. This tutorial should serve as a starting point. You could do the same for custom post types, links, or anything that fires the do_meta_boxes action hook.

Adding an excerpt box to your page editor

The first thing you should do is open your theme’s functions.php file in your favorite text editor. Paste the following PHP code into it:

add_action( 'admin_menu', 'my_page_excerpt_meta_box' );

function my_page_excerpt_meta_box() {
	add_meta_box( 'postexcerpt', __('Excerpt'), 'post_excerpt_meta_box', 'page', 'normal', 'core' );
}

Now, you’ll be able to add excerpts to your pages, just like posts. This can come in handy with themes that display search results in excerpt form.

Adding custom taxonomies to your page editor

This one will be a bit trickier. I’ll have to assume you’ve created a custom taxonomy specifically for pages. If you’re unfamiliar with this process, you need to familiarize yourself with creating custom taxonomies.

Let’s assume you’ve created a “People” taxonomy for pages. Your custom taxonomy code should look a little like this.

register_taxonomy( 'people', 'page', array( 'hierarchical' => false, 'label' => 'People', 'query_var' => true, 'rewrite' => true ) );

The important thing in that line is page. We’ll be adding meta boxes for all taxonomies that have been registered for pages.

Again, we’ll go to our theme’s functions.php file. Paste this PHP code in:

add_action( 'admin_menu', 'my_page_taxonomy_meta_boxes' );

function my_page_taxonomy_meta_boxes() {
	foreach ( get_object_taxonomies( 'page' ) as $tax_name ) {
		if ( !is_taxonomy_hierarchical( $tax_name ) ) {
			$tax = get_taxonomy( $tax_name );
			add_meta_box( "tagsdiv-{$tax_name}", $tax->label, 'post_tags_meta_box', 'page', 'side', 'core' );
		}
	}
}

Once that’s done, you’ll be able to use your page-based custom taxonomies.

Please note that hierarchical taxonomies aren’t going to be available yet. Maybe in WordPress 3.0?

A good move by WordPress

I’m glad WordPress is moving in this direction with some of its functionality. Average Joe might not realize the implications of something as simple as moving code to another file, but developers should rejoice. The reuse of code is a cornerstone of good development practice. By making things more modular, it becomes easier to create new things without rewriting a lot of code.

I’ve shown you how to do these things with pages. Just imagine being able to make these simple and quick changes for custom post types (i.e., content types), essentially having the ability to create any type of site you want with WordPress.

One of the features I feel that’s lacking in most plugins and themes is the ability to define custom capabilities to access certain content. This is one of the reasons I’ve developed this plugin.

If you’re a plugin or theme developer and add admin menus, this tutorial should be helpful. What I’ll be showing you is a way to give users of your plugin smarter control over its settings.

Adding an admin menu page the normal way

There are several functions for adding admin menus, which all work basically the same way. I’ll use add_submenu_page() as an example since it’s fairly common.

When adding a page, you’ll use the function like this:

add_submenu_page( $parent_page, $page_title, $menu_title, $capability, $file, $function );

What we’ll be focusing on here is the $capability variable. Typically, this is hardcoded, but we need to be able to change this. So, when writing that code, you should replace $capability with a filter hook:

add_submenu_page( $parent_page, $page_title, $menu_title, apply_filters( 'plugin_name_capability', $capability ), $file, $function );

plugin_name_capability should be something unique to your plugin. Just leave $capability as whatever capability you would normally use. It can now be changed.

Making this change does two important things:

1. Allows users to change the capability if they want to with a filter.
2. Allows you to integrate your plugin with the Members plugin.

You can stop reading here and will have done your part in making your plugin more flexible. However, you can offer integration with my Members plugin, which will make it even easier for users to use.

Integrating your plugin/theme with the Members plugin

Here’s where the real neat stuff comes into play. You can run a check to see if the Members plugin is installed. If the plugin is indeed installed, you can create a custom capability just for your plugin’s settings page.

Let’s assume that filter hook was something like this:

apply_filters( 'plugin_name_capability', 'manage_options' );

People without the Members plugin would need the manage_options capability to change the settings for your plugin. To me, that doesn’t sound like a great solution, and it definitely doesn’t offer the site owner much flexibility.

If the Members plugin is installed, we’ll change that capability to something like edit_my_plugin_settings (change to something unique):

if ( function_exists( 'members_plugin_init' ) )
	add_filter( 'plugin_name_capability', 'plugin_name_unique_capability' );

function plugin_name_unique_capability( $cap ) {
	return 'edit_my_plugin_settings';
}

Now, only users of a role with the edit_my_plugin_settings capability will be able to access that plugin’s page.

Adding the capability to the role edit page

You can offer even more integration with the Members plugin if you like. You can add a checkbox to the Edit Role page that allows users to easily select this capability rather than typing it in.

if ( function_exists( 'members_get_capabilities' ) )
	add_filter( 'members_get_capabilities', 'plugin_name_extra_caps' );

function plugin_name_extra_caps( $caps ) {
	$caps[] = 'edit_my_plugin_settings';
	return $caps;
}

Why is all this important?

Imagine running a site with 20 different writers, publishers, administrators, and so on. Some people of that site need specific access to certain things but no access to other things.

For example, a friend and I are both running this site with all these people. The friend doesn’t need access to the WordPress options, but he does need access to your plugin’s options. Those should be controlled by two separate capabilities rather than one.

I created Members to allow site owners to have as much flexibility as possible. But, the plugin itself can only do so much on its own. As developers in the WordPress community, we can make WordPress infinitely flexible by working together, and I’m definitely trying to make it as easy as possible to integrate other plugins with my own.

Management of these fields will be coming in a later version of my user management plugin, but some of you may want to do this now.

In this tutorial, I’ll show you how to add an input box for a Twitter username and how to display it on your site, which will look a little something like this:

My profile and Twitter link

If you want to see a live example, check out one of my latests posts on Pop Critics.

Adding custom user fields

Open your theme’s functions.php file and drop this PHP code in:

add_action( 'show_user_profile', 'my_show_extra_profile_fields' );
add_action( 'edit_user_profile', 'my_show_extra_profile_fields' );

function my_show_extra_profile_fields( $user ) { ?>

	<h3>Extra profile information</h3>

	<table class="form-table">

		<tr>
			<th><label for="twitter">Twitter</label></th>

			<td>
				<input type="text" name="twitter" id="twitter" value="<?php echo esc_attr( get_the_author_meta( 'twitter', $user->ID ) ); ?>" class="regular-text" /><br />
				<span class="description">Please enter your Twitter username.</span>
			</td>
		</tr>

	</table>
<?php }

This will create a new area in the user edit screen that looks like this:

Additional profile fields

The custom part of the code is this bit:

<tr>
	<th><label for="twitter">Twitter</label></th>

	<td>
		<input type="text" name="twitter" id="twitter" value="<?php echo esc_attr( get_the_author_meta( 'twitter', $user->ID ) ); ?>" class="regular-text" /><br />
		<span class="description">Please enter your Twitter username.</span>
	</td>
</tr>

Note that if you want to add more fields, copy that and change twitter to something unique for each additional field. Just make sure you change each instance of twitter.

Saving the custom user fields

Just because we’re displaying these extra fields, doesn’t mean they’ll be saved when the user profile is updated. So, we need one more function to handle this. Drop this PHP code in your theme’s functions.php file.

add_action( 'personal_options_update', 'my_save_extra_profile_fields' );
add_action( 'edit_user_profile_update', 'my_save_extra_profile_fields' );

function my_save_extra_profile_fields( $user_id ) {

	if ( !current_user_can( 'edit_user', $user_id ) )
		return false;

	/* Copy and paste this line for additional fields. Make sure to change 'twitter' to the field ID. */
	update_usermeta( $user_id, 'twitter', $_POST['twitter'] );
}

Now, your information will be saved.

Displaying custom user fields on the site

For getting these additional fields, WordPress has two nifty functions: the_author_meta() and get_the_author_meta(). The former displays the meta information, and the latter returns it for use in PHP. Each takes in two parameters:

the_author_meta( $meta_key, $user_id );

You can use this to grab the information from any of the fields you’ve created. For example, the $meta_key for our Twitter field is twitter. We just need to call it up somewhere in our theme.

So, what we’re going to do is build an author box to add to the end of our single posts. Once again, we visit our theme’s functions.php file and drop some PHP code in:

function my_author_box() { ?>
	<div class="author-profile vcard">
		<?php echo get_avatar( get_the_author_meta( 'user_email' ), '96' ); ?>

		<h4 class="author-name fn n">Article written by <?php the_author_posts_link(); ?></h4>

		<p class="author-description author-bio">
			<?php the_author_meta( 'description' ); ?>
		</p>

		<?php if ( get_the_author_meta( 'twitter' ) ) { ?>
			<p class="twitter clear">
				<a href="http://twitter.com/<?php the_author_meta( 'twitter' ); ?>" title="Follow <?php the_author_meta( 'display_name' ); ?> on Twitter">Follow <?php the_author_meta( 'display_name' ); ?> on Twitter</a>
			</p>
		<?php } // End check for twitter ?>
	</div><?php
}

Now, all you need to do call the function in your theme’s single.php file somewhere after the post has been displayed:

<?php my_author_box(); ?>

If you’re using a child theme, your theme author can probably tell you a more appropriate action hook to add this function to so you don’t mess up your theme’s template files.

What other custom user field uses can you think of?

This is just another one of those powerful features of WordPress that I don’t see used much. I have several things in mind that I could use this technique for, but I’d like to hear what you’d do with it.

Surely we can do some cooler stuff than just displaying a link to Twitter?

The good news is that WordPress has a built-in system that allows us to deregister these scripts and styles.

Wait, don’t the plugins require this code? Probably. But, we want to take control of these files and make our sites run faster. Disabling these scripts and styles will allow us to do a few things:

1. Combine multiple files into single files (mileage may vary with JavaScript here).
2. Load the files only on the pages we’re using the script or style.
3. Stop having to use !important in our style.css file to make simple CSS adjustments.

For this exercise, I’ve chosen two popular plugins from the plugin repository: Contact Form 7 and WP-PageNavi.

The dirty truth

Not all plugins use the appropriate methods for loading scripts and styles. Some developers just drop stuff right in the header. This is usually because they’re not familar with two important WordPress functions: wp_enqueue_script() and wp_enqueue_style(). If your plugin/theme author isn’t using these functions, please encourage them to do so. It allows the rest of us to work with their code using the methods WordPress provides.

While figuring out what scripts or styles you want to disable, you might have to get your hands dirty. This means looking in code. Unless your plugin author has documented the script or style handle, you’ll need to find it.

Disabling JavaScript

For this example, we’ll be disabling the Contact Form 7 plugin’s JavaScript. The first thing you need to do is find the handle for the script. Open the wp-contact-form-7.php file in your favorite text editor and do a search for wp_enqueue_script. Doing so will turn up this bit of code:

wp_enqueue_script( 'contact-form-7', wpcf7_plugin_url( 'contact-form-7.js' ), array('jquery', 'jquery-form'), WPCF7_VERSION, $in_footer );

The handle for this plugin’s JavaScript is contact-form-7. Now, you can close this file and move on.

Open your theme’s functions.php file and add this PHP in:

add_action( 'wp_print_scripts', 'my_deregister_javascript', 100 );

function my_deregister_javascript() {
	wp_deregister_script( 'contact-form-7' );
}

Once saved, the script will no longer load. You can deregister as many scripts as you want within this function.

Disabling styles

In this example, we’ll be disabling WP-PageNavi’s stylesheet. This is something I almost always do because I add the style rules to my theme’s style.css file.

The first thing you should do is open wp-pagenavi.php in a text editor and search for wp_enqueue_style. This will turn up this code:

wp_enqueue_style('wp-pagenavi', get_stylesheet_directory_uri().'/pagenavi-css.css', false, '2.50', 'all');

And this:

wp_enqueue_style('wp-pagenavi', plugins_url('wp-pagenavi/pagenavi-css.css'), false, '2.50', 'all');

What we’re looking for is wp-pagenavi, which is the handle for the style. Once you’ve found that, close the file and add this to your theme’s functions.php file.

add_action( 'wp_print_styles', 'my_deregister_styles', 100 );

function my_deregister_styles() {
	wp_deregister_style( 'wp-pagenavi' );
}

That’ll disable the stylesheet for this plugin. Feel free to deregister as many styles as you want within this function.

Tips on making this work better

You’ve disabled several scripts and styles, but you need to do something with them. Here’s a list of tips on how to make use of the methods described in this tutorial:

• Append styles that you’ve disabled to the end of your theme’s style.css file and edit them from there to get the look you want.
• Combine several scripts into a single file and load it yourself. I would only do this for things that use the same JavaScript library. For example, I often combine scripts that are built on jQuery.
• Use conditional tags for fine-grained control over when a script or style is loaded.

If you disable something, it may cause the plugin/theme not to work correctly. Most styles can easily be added to your theme’s stylesheet so that you’re not loading a ton of stylesheets on your site. JavaScript is a different beast altogether, and I only recommend combining multiple files into one if you know what you’re doing.

Have fun with this. Experiment. Share your experience with others in the comments.

While it’s cool to be able to style a particular post or page (or tons of other things) with a simple CSS selector in a single stylesheet, it’s not always enough. Sometimes, you may need to drastically change the appearance of a page. To do this, you’d need to load a different stylesheet.

Many tutorials will tell you to dive directly into your theme’s header.php file. Of course, you know I’m more interested in doing things the smart way by taking advantage of a theme’s functions.php file. This technique will allow you to easily transfer your custom code from theme to theme, use within a plugin, and it’s the best method when working from a child theme.

Dynamically changing your theme’s stylesheet

For this example, we have two pages we want use separate stylesheets on: About and Portfolio. The first thing you should do is create your stylesheets. Drop them into your theme (or child theme) folder and name them style-about.css and style-portfolio.css.

Once that’s done, add this code to your functions.php file:

<?php

add_filter( 'stylesheet_uri', 'my_stylesheet', 10, 2 );

function my_stylesheet( $stylesheet_uri, $stylesheet_dir_uri ) {

	if ( is_page( 'about' ) )
		$stylesheet_uri = $stylesheet_dir_uri . '/style-about.css';
	elseif ( is_page( 'portfolio' ) )
		$stylesheet_uri = $stylesheet_dir_uri . '/style-portfolio.css';

	return $stylesheet_uri;
}

?>

Just save and check out your new styles.

The code explained

What we’ve done with the few lines of code above is filter stylesheet_uri, which is a hook that returns your currently active theme’s stylesheet. This hook gives us two parameters we can use:

• $stylesheet_uri
  The URI to the current theme’s stylesheet, which needs to be returned.
• $stylesheet_dir_uri
  The URI of the current theme’s directory, which we can use in our own function and not have to figure out where our styleheets are.

The is_page() function is one of many conditional tags at your disposal for determining what page a visitor is currently viewing.

I’ve seen some themes add their own more link filter hook, but this is unnecessary because WordPress 2.8 introduced the_content_more_link filter hook. Maybe this post will help those theme authors cut back on an extra filter hook when it’s not needed.

This will allow us to easily overwrite the default.

What is the more link?

When writing a WordPress post, you can cut the text off at any point by adding in this code:

<!--more-->

If you’re using a theme that shows the standard full post on the home/blog page of your site, this will cut the article short at the point you added the code. It will also add a link to the single-post view where the reader can continue reading the post.

Using the_content_more_link filter hook

What we want to do is change our theme’s more link text, but we need to do this the appropriate way, and the appropriate way means not hacking up your theme author’s code.

Let’s assume our theme’s more link outputs “(more…)” when we add the <!--more--> link within the post editor. Maybe we don’t like that message too much. We’d like to change it to read “Continue reading →” instead.

Open your theme’s (or child theme’s) functions.php file and paste this code in:

<?php

add_filter( 'the_content_more_link', 'my_more_link', 10, 2 );

function my_more_link( $more_link, $more_link_text ) {
	return str_replace( $more_link_text, 'Continue reading &rarr;', $more_link );
}

?>

That’s all there is to it. Enjoy your custom more link text.

There is no excerpt because this is a protected post.

While this is fine for many scenarios, it may not be the most helpful piece of text for the average Internet user. Instead of showing the message, we’ll replace it with a password form.

Replacing the no excerpt text with a password form

WordPress comes packaged with a neat function called get_the_password_form() that handles most of the work for us. It generates the entire form. All we need to do is load it at the appropriate time.

Open your theme’s functions.php file and drop this code in:

<?php

add_filter( 'the_excerpt', 'excerpt_protected' );

function excerpt_protected( $content ) {
	if ( post_password_required() )
		$content = get_the_password_form();

	return $content;
}

?>

This will give us a new message:

This post is password protected. To view it please enter your password below:

Followed by that message is an input field for the post password.

Writing shorter tutorials

For those of you that follow this blog regularly, you know that I typically write long, in-depth tutorials. Many times, these are advanced techniques that not everyone will use. My plan is to start mixing in some quick tutorials that only take a few minutes to implement and maybe help out the average user more. This way, I can write more often. The longer tutorials tend to take a few days of work.

If you have any ideas for WordPress or bbPress tutorials, feel free to let me know in the comments or through my contact form.