BE Stats is the plugin for you. It asks for the 100 most popular posts over the past 30 days. I filter this list down to just posts and then store its ranking as post meta (‘be_stats’).

See it in use here: http://www.billerickson.net/popular/

Download BE-Stats from WordPress.rog

You can then write custom queries using that metadata, or use the Display Posts Shortcode which makes it even easier.

Here’s some examples using the shortcode:

[display-posts orderby="popular"]
Lists the 10 most popular posts
[display-posts orderby="popular" posts_per_page="4"]
Lists the 4 most popular posts
[display-posts orderby="popular" posts_per_page="4" tag="basic"]
Lists the 4 most popular posts tagged “basic”

I developed this for a recent client project (still under development, will share link once it is live). The website is a news site that releases a lot of content. On the home and category archives they wanted to display recent posts and popular posts from that section. Here’s what I placed where I want popular posts:

There’s also some filters for you to customize how the plugin works.

be_stats_args – Controls what arguments are passed to WordPress.com Stats API. Example:

be_stats_update – Conditional for determining if stats data should be saved Examples:

Hopefully some other developers will find a use for this.

The post Displaying Popular Posts using BE-Stats appeared first on Bill Erickson.

I’d like to do more blog posts and conference talks on business/freelancing, but not sure exactly what I should talk about.

Do you have any topics or questions you’d like covered?

The post Any Business Questions? appeared first on Bill Erickson.

As a successful service provider with no plans to shift business models, I’d like to explain my reasoning and start a discussion. I’m not criticizing those who choose to make this shift – there’s many successful people I know who have, and I’ll highlight a few of them below. But I feel like everyone knows the reasons for making the shift and not many of the reasons for not making the shift.

There’s more than two business models

You can never be rich trading your time for money. You need to shift to selling products, so increases in revenue do not result in increases in time spent working.

Avoiding the obvious response to the first line (keep raising your rate until you ARE rich trading time for money), let’s focus on the second. Some people believe the decision is binary – you are a service provider or a product provider; small businesses are at one end, and startups are at the other.

I like to think of it as a spectrum. On the left you literally are trading time for money. For every X increase in revenue, it requires an equivalent increase in time. These are the people who work on an hourly basis. On the right, every X increase in revenue requires absolutely no increase in time (or other costs). This is the ideal, but is for the most part unobtainable. All businesses fall somewhere in the middle.

Brian Gardner has built a hugely successful business with StudioPress. He builds a theme once and can sell it an unlimited amount of times without increasing the time spent developing it. BUT, each new customer does result in a marginal increase in his support costs. The theme development aspect of his business is perfectly scalable, but the support business is not (X number of customers results in Y number of support staff). StudioPress is on the right side of the spectrum, but not all the way.

I’m a WordPress developer that converts designs to themes. Rather than working on an hourly basis, I charge on a per-project basis. While still on the left side of the spectrum, I’m able to lean towards the right for the following reasons:

1. The more projects I work on, the faster I can develop a site through experience and reusing code written earlier. This increases my effective hourly rate.
2. The more projects I work on, the greater value I can provide to my clients through my experience. A site I built in 2012 is substantially better than the one I built in 2010 (even though that one was pretty good too ). This increases the rates I can charge, most evident through my project minimum. For the past three years, every January my minimum for a standard project has gone up. But I personally believe the value I’m providing to my clients goes up even more than my rate has.

For these reasons, even though I’m putting in about the same amount of time of work each year, my revenue for 2012 is much higher than 2011, and I expect the same for 2013.

As a service provider, find the more scalable aspects of your business and focus on them. Likewise, find the aspects that are less scalable and decrease your focus on them. Here’s a few examples.

I’m able to increase my efficiency at developing simple sites more than I can complex sites. Complex sites usually involve more site-specific features that you can’t leverage across projects. Clients can see a huge value in a site built at my $2,500 project minimum, but as the price increases the value I provide approaches a linear trend. The higher the project cost, the more of the project is non-reusable “time-for-money” work. For this reason, I try to focus on the smaller sites where I can deliver more value.

I can increase my efficiency at coding, but I have a hard time increasing my efficiency on the phone. An hour long call I have with a client two years ago will still take an hour today. For this reason, I try minimize phone calls and other one-on-one communication.

• When you land on my homepage, you’ll see the services I focus on. If you don’t want those, you’ll leave.
• Once you’ve moved past that to my specific service pages or portfolio, you’ll see my project minimum. If that’s outside your budget, you’ll leave.
• If you’re interested in starting a discussion, you’ll send an email using my contact form. I’ll read it, see if I have any canned responses that address the questions you have, and modify it as needed (a lot of the initial emails ask the same types of questions).
• If you’re satisfied with our initial discussion, we’ll hop on the phone for 30 minutes to resolve any additional questions you have.

This is much better than my old process, which was to post a phone number and let everyone who lands on my website call me.

Products are an Investment

When you say you want to build a product that provides recurring revenue, you’re actually saying you want to invest your time (and possibly other resources) to establish an income producing asset.

The two factors that are most important to an investment are often not considered by freelancers turning to product development: risk and return. People want the recurring revenue, but don’t extend the thought process out to how much revenue they want, how much time they’re willing to invest, and how likely they are to hit their target.

Thomas Griffin committed months of work to the development of Soliloquy. It paid off, and he’s now able to scale back his consulting services as Soliloquy supplements the income.

But for every successful product released, there’s many that never made it this far, or made it to launch but didn’t generate enough revenue.

Before spending months or years developing your product, make sure there’s a healthy demand for it. Since you’re a freelancer already, maybe it’s something many of your clients have been wanting. You can decrease your risk by subsidizing the development cost through client work (a few clients hire you to develop this feature and you retain the rights to distribute it).

Make sure you can generate a reasonable return on your investment. If you can charge $200/hr for client work, and instead spend 1000 hours developing a plugin that sells for $20, make sure you can sell at least 10,000 of them. Also consider the time value of money. Yes, you might sell 10,000 of them over 10 years, but a dollar earned 10 years from now is worth less than a dollar earned today. It’s also a riskier dollar.

There are markets where you can trade your cash for income producing assets. Stocks, bonds, individual loans…. Building a product or scalable business is not the only way to have recurring revenue. These alternatives are less risky and don’t have a waiting period.

Consider the Long-Term Costs

Since WordPress is GPL, and all derivative, publicly distributed works are also GPL, many developers who sell themes and plugins are actually in the support business. You need to make sure your revenue per customer covers the lifetime cost of supporting that customer.

Let’s say you’re selling a theme for $50, and you’re getting 100 sales a month. You’re doing pretty good! At first the money is rolling in, and the support costs are low because you don’t have many users. Two years down the line, sales have dropped to a trickle, but now you have a customer base of 2000 that’s still requiring support.

Make sure that $50 you earned from the first customer can pay the cost to support that customer. Don’t build your business in a way that the current month’s sales pay the support costs of all the existing customers, and you need to keep growing sales in order to maintain your actual product: support.

Do as Gravity Forms does and limit your support to a defined period. Or, separate the cost of the scalable item (the product) and the non-scalable item (the support), and charge accordingly.

In Summary

Since even your consulting business has scalable, “startup-y” elements, it’s beneficial to think like a startup. This means your time is worth $1,000/hr, and read everything else Jason Cohen has written.

Before changing your business strategy from consulting to products, consider if there’s ways you can improve your consulting business to include some of the benefits of a scalable business.

The post In Defense of Consulting Businesses appeared first on Bill Erickson.

As a newcomer to the web world and genesis included, I’m attempting to learn from others and looking at great designs that inspire me. This brings me to my question. Would you be willing to share your experience or even go as far as sharing your code for your custom designed portfolio page here?

After writing out my response, I figured others might be interested as well. Here’s the code, followed by a description of what each function does below.

First, the functions.php file:

• be_portfolio_query() customizes the query on the portfolio pages. This must go in functions.php since it needs to run before main query, which happens before the template is determined. More information on customizing the query.

I specify the post type so the projects show up on the taxonomy archive pages AND so that the archive-projects.php file is used for the taxonomy archive pages. I could’ve also done this second part using the template_include filter.

• be_portfolio_body_class() adds a consistent body class to all the pages using this template, for styling (if I didn’t use this, I’d have to write styles with body.post-type-archive-projects and body.tax-type )
• be_collect_testimonials(), I wanted to display a testimonial between certain projects, and wanted that testimonial to be from one of the projects featured on this page. So before the projects are listed, I loop through them all and pull out all the testimonials. I can then use this in a function lower down in the page
• be_sort_projects() adds the links before the project listing that lets you go from the main portfolio (all projects) to one of the taxonomy archives
• be_project_post_classes() – This looks at the loop counter and adds column classes to the posts, breaking it into multiple columns. See this tutorial for more information.
• be_outer_wrap() and be_outer_wrap_close() add a wrapping div around all the posts and testimonials so they can be cleared with CSS
• be_project_archive_content() is the content of each project. It has the image and then displays the taxonomy terms (Project Type) below it
• be_project_divider() adds a dividing line after every 3 posts, except after the 6th one (where a testimonial is the divider)
• be_project_quote() adds a testimonial after the 6th project (it’s #5 since it starts counting at 0) OR after the last project if there are less than 6. I also have it choosing different testimonials for different taxonomies so the same testimonial isn’t used on every page

The post Building my Portfolio appeared first on Bill Erickson.

This article was originally published in January 2011.
I rewrote the article in November 2012 to take advantage of new features developed since then.

If you have a magazine-like website, you might need to specify multiple authors for a single post. There’s a great plugin called Co-Authors Plus that will let you do this.

Once installed, you can use many template tags, or you can use the get_coauthors() function to retrieve all the author data and use it however you like.

Authors Shortcode

The Post Info area of Genesis can be customized using a filter. We could drop the coauthors_posts_links() function in there to list authors and link to their archive pages, but it would be even better to create a shortcode to be used in the post info section. If that function isn’t available (ex: someone disabled the plugin), it will use the standard get_author_posts_url() instead.

We will create a shortcode called [post_authors_post_link] with the following parameters:

• between – what to display between authors, default is a comma
• between_last – what to display between the last two authors, default is “and”
• before – what to display before the list of authors, default is empty
• after – what to display after the list of authors, default is empty

To set up the shortcode, add the following to your functions.php file or core functionality plugin:

Now if we want to update the Genesis Post Info to display all post authors (with “by” right before the listing), we’d add this to functions.php:

Author Boxes

Genesis also has a feature called the Author Box that displays the author information at the bottom of the post. But this doesn’t use Co-Authors Plus, so if you have multiple authors only one will show up at the bottom.

First we’ll remove the Genesis Author Box. Then we’ll copy the code into our own function, but this one will accept an author ID field so we can render any author with it. Finally, we’ll create a function that checks to see if Co-Authors Plus is in use, and if it is, display author boxes for all authors; if it isn’t, display the author box for the normal post author.

The post Multiple Authors for a Post appeared first on Bill Erickson.

One of my favorite “under-the-hood” features of WordPress and Genesis is the ability to override almost any kind of option/meta: site options, post meta, user meta, term meta….

Make sure you are careful with these filters though. Themes and plugins will expect certain options/meta to be returned when they call a core function, and if you’re not careful you could break them. Make sure you only return your changes in the very specific instances in which you want them.

Here’s a few common use cases:

1. Change the admin email on certain pages (site option)
2. Change the default layout of the homepage (site option)
3. Force a layout on the homepage (post meta)
4. Turn the Genesis Author Box on automatically for author archives (user meta)
5. Specify a default title for term archives (term meta)

Site Options

Site options are anything stored in the wp_options database, and you typically access them using the get_option() function.

WordPress provides a filter for these options, called pre_option_($key) (see wp-includes/option.php, line 36 in WP 3.4.1).

Example 1: Change the admin email on certain pages

As a simple example, let’s say you had an email link in your footer, and you wanted to modify the ‘admin_email’ option on blog posts to use the blog post’s author email (I probably wouldn’t use this approach, but it shows you how to use the filter).

Genesis has a lot of options, but instead of storing them all as individual entries in the database, it stores them as a single serialized array. This is great for performance, but it makes using the above filter difficult. So Genesis provides a filter for Genesis options and any other options that use the Genesis Settings API.

Example 2: Change the default layout of the homepage

You can set the site-wide default layout in Genesis > Theme Settings, which sets the Genesis option ‘site_layout’. But on the homepage you might want to have a different default layout. We’ll set this using the genesis_pre_get_option_($key) filter (see lib/functions/options, line 57 in Genesis 1.8.2).

Since this is such a popular use, Genesis has already made functions that return all the built-in layouts, and you can see a list of them at the end of this post. We can replace the code above with this:

Please note that both the above code snippets are to be placed in front-page.php or home.php — whichever template file is responsible for your homepage.

Post Meta

WordPress provides a filter called get_post_metadata (see wp-includes/meta.php, line 274 in WP 3.4.1) for modifying post meta.

Example 3: Force a layout on the homepage

The Genesis function that determines the page layout first checks the post’s meta field ‘_genesis_layout’, and if none is specified it uses the sitewide default (which is what we overwrote in the previous example). The code below overrides the post meta, so the user can’t change the layout on this page:

Again, this code is running in front-page.php or home.php — whatever is responsible for your homepage. Since the filter passes the $post_id, we could also run this in functions.php like so:

We’re now making sure the $meta_key matches the one we want AND we’re making sure $post_id is the page set to the front page in General > Reading. If you wanted this on your blog page instead, you could check $post_id against get_option( 'page_for_posts' ).

User Meta

WordPress provides a filter called get_the_author_($key) (see wp-includes/author-template.php, line 112 in WP 3.4.1) for modifying author meta. You can use this to override any of the author meta from WP Core, and also any author meta added by themes and plugins.

Example 4: Turn the Genesis Author Box on automatically for author archives

If you have the Genesis theme installed and go to Users > Your Profile, there’s a checkbox that lets you specify if an author box should show up on your author profile and/or at the bottom of all your posts. These update the user meta fields genesis_author_box_archive and genesis_author_box_single, respectively.

This code will make genesis_author_box_archive always return true, so the author box it automatically shows up on all author archive pages:

You’ll notice I’m using a function called __return_true(), but that I didn’t create that function. This is one of the WordPress core helper functions. See the end of this post for a list of more helper functions.

Term Meta

WordPress doesn’t have term meta, which is one of the few things it is lacking as a CMS. Genesis needed term meta for all its SEO and layout options, so it created term meta using the options table.

Genesis also added a filter, genesis_term_meta_($key) (see lib/functions/options.php, line 228 in Genesis 1.8.2), used for modifying this meta.

Example 5: Specify a default title for term archives

On my photography blog, I have a taxonomy called “people” that I use for tagging people in photos. For taxonomy archives, Genesis has term meta for an Archive Headline and Description. I wanted to display a headline at the top of all the term archive pages, but didn’t want to manually create them.

Here’s a simple function I wrote that first checks to see if a headline has been provided, and if it hasn’t it uses “Photos of [person's name]“.

Relevant filters:

• WP: pre_option_($key) in wp-includes/option.php, line 36
• WP: get_the_author_($key) in wp-includes/author-template.php, line 112
• WP: get_post_metadata in wp-includes/meta.php, line 274
• Genesis: genesis_pre_get_option_($key) in lib/functions/options.php, line 57
• Genesis: genesis_term_meta_($key) in lib/functions/options.php, line 228

Helper Functions:

• WP: __return_true() – returns the Boolean state of true
• WP: __return_false() – returns the Boolean state of false
• WP: __return_zero() – returns a value of zero (0)
• WP: __return_empty_array() – returns an empty array, as in array()
• WP: __return_null() – returns null (or void)
• Genesis: __genesis_return_full_width_content() – returns ‘full-width-content’
• Genesis: __genesis_return_content_sidebar() – returns ‘content-sidebar’
• Genesis: __genesis_return_sidebar_content() – returns ‘sidebar-content’
• Genesis: __genesis_return_content_sidebar_sidebar() – returns ‘content-sidebar-sidebar’
• Genesis: __genesis_return_sidebar_content_sidebar() – returns ‘sidebar-content-sidebar’
• Genesis: __genesis_return_sidebar_sidebar_content() – returns ‘sidebar-sidebar-content’

The post Overriding Options and Meta appeared first on Bill Erickson.

In the screenshot above, you’ll see the Plays dropdown lists three subpages. And on the right side, those same subpages are listed because we’re currently in the Plays section.

There’s a few popular approaches:

• Use wp_list_pages() to dynamically list all subpages to the current section. The downside here is you can’t easily hide items from this list, and you have to keep the page order in sync with the custom menu’s page order (so they appear in the same order). You also can’t provide custom lables for menu items. In the above example, “Current Season” is really a page called “2011-2012 Season”, and they’ll have older seasons they do not want displayed in this menu.
• Create a custom menu for each section. It’s a lot of work maintaining all these menus, and the end user can’t easily add a new section to the site since someone will need to create a menu for that section.

Assuming your main menu has all your site’s sections and their desired subpages, we can use wp_get_nav_menu_items() to pull only the relevant subpages.

The post Custom Secondary Menu appeared first on Bill Erickson.

Over the past two years I’ve found some improvements to my process, most notably around serialized arrays.

Before Migrating, Custom Table Prefix

When building a new website, make sure to use a custom table prefix (you define this in wp-config.php). If you started with an existing database, use this process to change the prefix.

I like to make mine [clientname][date]_. So if my client was Automattic and I built the website today, the prefix would be automattic05232012_.

This is so that there’s no risk you upload your tables to a database with the same named tables. When working on an existing site, it’s important to have both sets of tables in the database so that if there’s any issues with the migration, you can quickly switch back to the old site while you figure out the issue.

Migration Process

1. Backup the database tables. I like to use Sequel Pro to connect to my database and export them, but you can also use the Adminer WordPress plugin or phpMyAdmin through your server’s cPanel. The default export will the a .sql file, but you might want to use one of the compressed formats. Many hosts only allow you a small file upload (like 2MB), and compressing it can help you stay under that limit.
2. Backup the wp-content directory. This can be as easy as FTP’ing onto your server and dragging a copy of wp-content/ to your computer. If you have SSH access and are comfortable with command line, I like to make a tarball because it is much faster to download than a lot of small files. Use a command like this: tar -pvczf wp-content.tar.gz wp-content/.
3. Upload the database to the new server. If WordPress is already installed, use the Adminer plugin to add the database. If not, you might use phpMyAdmin provided by the host.
4. Upload searchreplacedb2.php to the top level of your server (wherever wp-config.php is). This is used to find all the uses of the old domain and replace them with the new domain. The reason we’re using this tool instead of simply doing it in the database is that it will work with serialized arrays. Click the above link to read more about the problem and solution. If you’re really worried about security, do this locally or on your development server so that this file never has to be on the production server.
5. Load the the search and replace tool at http://www.yoursite.com/searchreplacedb2.php. It will auto-populate the database information from wp-config.php. Click “Next”, select the applicable tables, then on the find/replace screen type the old and new domain. Make sure you do not include a trailing slash (correct = http://www.yoursite.com | incorrect = http://www.yoursite.com/). Do the find and replace, then remove this file from your server.
6. If a brand new website, upload copy of WordPress along with your custom wp-content directory. If there’s already a WordPress website live, follow the rest of the steps below.
7. On your computer, unpackage the wp-content tarball (if you tarballed it), and then rename the folder wp-content.new. The name doesn’t matter, it just has to be different than wp-content. Upload the folder to the same directory that has the old wp-content/ .
8. Open wp-config.php. Find the line that starts with $table_prefix. Comment it out, and create a new $table_prefix line with your custom table prefix. It will look something like this.
9. Save wp-config.php, and then immediately rename wp-content/ to wp-content.old/, and wp-content.new to wp-content/
10. Check the website’s homepage. If anything looks wrong, switch to the old site while you figure it out. Go into wp-config.php, comment out the new table prefix and remove the commenting on the old table prefix. Rename the wp-content directories back to how they were.
11. If the site is working, log in and go to Settings > Permalinks, then click Save. This will update the permalink structure and ensure all URLs work.
12. Go to Settings > Privacy and make sure you have the site visible to search engines. I use the WordPress SEO plugin which has a big red nag on the backend if you’re privacy settings aren’t set correctly. Since I don’t want that nag showing up on my dev environment, I include this snippet in my functionality plugin (line 150-159) to hide it under certain conditions (localhost or master-wp in the domain, since those are where I develop).
13. On the old site, install the Migration Notice plugin. I’ve had a lot of clients get confused about which backend they are supposed to post new content to, so if you aren’t deleting the dev environment immediately this prevents that issue.
14. Make sure you’ve removed searchreplacedb2.php. This was mentioned in #4, but deserves reiterating (thanks WPExplorer).
15. Update file permissions of wp-content directory. If you’re using WPEngine, they’ve added a super useful button “Reset File Permissions” in their WPEngine page of your WordPress backend.

The post Migrating WordPress Websites appeared first on Bill Erickson.

Don’t feel like coding? I built a plugin that does this for you.
See the Genesis Grid Loop plugin.

Note: This technique can be used by all WordPress themes. I’m proposing it as a replacement for the Genesis-specific grid loop, so aspects of this post might be Genesis-specific.

A popular request is to list posts in multiple columns. I do it on my blog, and do it often on my clients’ sites.

Genesis developed a Grid Loop, which you can utilize inside your Genesis themes for this effect, and is how this blog does it. While very useful, it can be difficult to set up. I believe this is because they combined two separate functions: what content to display (your query) and how to display it.

By breaking those two functions we can use another feature of Genesis, the column classes, to build grid loops easier. You can also copy that CSS to any WordPress theme and make it work too.

For this example I’ll be using a Gallery theme I recently built. On the archive pages, it displays posts in three columns. See the screenshot above, or click here) for an example.

Step 1: Multiple columns using post_class

The post_class filter lets us customize the classes applied to each post in the loop. Since I want this to only apply to archive pages, I’m placing it in archive.php.

The first line adds a class of ‘one-third’ to all posts. Then I grab the current post counter out of $wp_query, and if this is the first post ( 0 == $wp_query->current_post ) or if the remainder of the current post divided by 3 is zero (this tells us the current post is the first in a row), apply a class of “first” as well.

That’s it! You now have your content broken into multiple columns. If you want two columns, use ‘one-half’ and divide the current post by 2. If you want four columns, use ‘one-fourth’ and divide the current post by 4.

Step 2: Customize the Query

When I view the archive page now, it’s in three columns but it’s only displaying 10 posts. The last post sits by itself in its own row. I’m going to modify the main query to show 27 posts per page. You could use any number you want, just make sure it’s a multiple of columns. For more information on customizing the main query, see this post.

This code must go in functions.php, since the main query runs before it reaches archive.php (it checks the query to figure out what template to load).

Even easier sitewide

If you’re using this for all listings of posts (home, archive, search…), it is even easier to set up. Put the post_class filter in functions.php so it runs sitewide, and add a conditional to check if it isn’t singular:

And instead of the function to customize the number of posts, go to Settings > Reading and tweak it there.

Advanced Example

The code snippet below (added to functions.php), modifies the blog’s homepage and archive pages to display 5 features and 6 teasers (in three columns) on the first page. On inner pages, it displays 0 features and 12 teasers (in three columns). It also updates the post image to use image sizes specifically created for features and teasers.

The first function, be_grid_loop_pagination(), is where we control the grid loop. Under the comment that says “Sections of site that should use grid loop”, you can modify that list to specify where you want the grid loop displayed. Right now it is running when is_home() or is_archive() is true. The second part, under the comment that says “Specify pagination”, is where you specify how many features and teasers to show on the homepage and subsequent pages.

The second function, be_grid_loop_query_args(), doesn’t require any customization from you. It uses the pagination information you added to the previous function to tell WordPress how many posts show up on each page.

The third function, be_grid_loop_post_classes(), applies relevant classes to each post. It’s adding a class of ‘feature’ to each feature post, and column classes to the teasers. The only thing that you’d need to change is the teasers sections if you want something other than three columns. Here’s what you’d need to change if you wanted two columns.

The fourth function, be_grid_image_sizes(), specifies the two image sizes. Change these to whatever size you’d like. If you don’t want images, you can leave out this function and the last one, be_grid_loop_image(). Also note that you need to have “Include Featured Image” checked in Genesis > Theme Settings > Content Archives.

The fifth function, be_grid_loop_image(), overrides the image size set in Genesis > Theme Settings > Content Archives with the image sizes we created in the previous function. No changes need to be made to this function.

The sixth function, be_fix_posts_nav() does as its name implies. The post navigation (Older/Newer, numerical links to posts pages…) uses $wp_query->max_num_pages to know how many pages there are, and this is based on the current page’s posts_per_page. So if you have less posts on your homepage than inner pages, the post navigation on the homepage will be off (this is noticeable if you’re using numerical links). This code changes the max_num_pages based on the grid args.

The post A better, and easier, grid loop appeared first on Bill Erickson.

Read the full article here.

The post Genesis Grid Loop Advanced appeared first on Bill Erickson.