Step 1: Initial Setup with Acorn

First, in your theme directory, initialize Sage 10 with Acorn by running these commands:

wp acorn acorn:init
wp acorn vendor:publish --tag=acorn

These commands create a /config directory in your theme with all the necessary Acorn configuration files, which were part of Sage 9 but removed in Sage 10.

Step 2: Configuring the View Compilation Path

Next, update the config/view.php file to set the ‘compiled’ path for Blade templates so that they are stored in a writable location for WordPress on Pantheon:

'compiled' => wp_upload_dir()['basedir'].'/storage/framework/views'

Step 3: Creating a Symlink for the Storage Directory

Next, we need to create a symbolic link from the theme directory to the storage/ folder within wp-content/uploads. From our theme directory, run the following command:

ln -sfn ../../uploads/storage

This keeps your theme files separate from uploaded content, making deployments and version control easier.

Step 4: Updating the Pantheon .gitignore File

Pantheon’s default .gitignore file excludes the /wp-content/cache directory, which we need to change. Comment out this line in the .gitignore file:

# /wp-content/cache

This prevents errors from the Acorn package, which requires this directory to exist. If you are working with a repository that you’ve already pushed to Pantheon, you may need to set your Pantheon environment to SFTP and manually upload the /wp-content/cache directory.

Step 5: Updating the Sage .gitignore File

Make sure the /vendor and /public directories are included in your repository, as they contain crucial files for Sage 10. Modify the Sage .gitignore file by commenting out these lines:

# /vendor
# /public

Additional Resources

For more insights, tips, and troubleshooting advice, visit the Roots Discourse. The community there is a great resource for developers working with Sage 10 on Pantheon.

Check out the primary source for this guide on Roots Discourse: Sage 10 on Pantheon.

Conclusion

Integrating Sage 10 into Pantheon takes some careful setup, but following this guide will help you get everything running smoothly. For the latest information and best practices, always refer to the official Sage documentation and Pantheon’s developer resources.

The post Integrating Sage 10 with Pantheon: A Step-by-Step Guide appeared first on Adam Balée Designs, LLC.

Understanding the Login Forms

The wp-login.php page handles four different forms, each of which can be customized:

1. Login Form
2. Lost Password Form
3. Reset Password Form
4. Register Form

Leveraging WordPress Hooks & Filters

WordPress offers a variety of hooks, functions, and filters that allow you to customize the login screen extensively. You can explore a comprehensive list of these tools here.

Adding Custom CSS & JavaScript

To change the appearance and behavior of the login page, you can add custom CSS and JavaScript using the login_enqueue_scripts hook. This will enable you to style the login page to match your site’s theme and add any interactive features you need.

add_action('login_enqueue_scripts', function () {
    wp_enqueue_style('custom-login', get_stylesheet_directory_uri() . '/css/custom-login.css');
    wp_enqueue_script('custom-login', get_stylesheet_directory_uri() . '/js/custom-login.js');
});

Changing the Login Url

By default, the logo on the login page redirects to wordpress.org. You can change this URL to redirect users to your homepage or any other URL that fits your needs.

add_filter('login_headerurl', function () {
    return home_url();
});

Customizing the Login Text

To modify the text that appears when users hover over the login logo, use the login_headertext filter. This is a great way to add a personal touch or include a call to action.

add_filter('login_headertext', function () {
    return 'Welcome to My Website';
});

Modifying the Login Page Title

You can also customize the meta title of the login page to better reflect your brand. This can be done using the ‘login_title’ filter.

add_filter('login_title', function ($login_title) {
    return 'Login to My Awesome Site';
});

Securing Login Error Messages

Default login form error messages can reveal whether a username exists in the system, which poses a security risk. To improve security, you can make the error messages more generic, preventing potential attackers from gathering information about your users.

/**
 * Customizing the login error message
 * 
 * @link https://developer.wordpress.org/reference/hooks/login_errors/
 * 
 * @return string
 */
add_filter('login_errors', function ($error) {
    $error = 'Invalid username or password.';
    return $error;
});

Additional Customizations

Beyond the basics, there are numerous other customizations you can implement to enhance the login experience:

Custom Background and Logo

Add a custom background and logo to the login page to align it with your site’s branding.

add_action('login_enqueue_scripts', function () {
    echo '
    <style type="text/css">
        body.login {
            background-image: url(' . get_stylesheet_directory_uri() . '/images/custom-background.jpg);
            background-size: cover;
        }
        .login h1 a {
            background-image: url(' . get_stylesheet_directory_uri() . '/images/custom-logo.png);
            background-size: contain;
            width: 320px;
            height: 80px;
        }
    </style>';
});

Custom Login Button

Style the login button to match your site’s theme.

add_action('login_enqueue_scripts', function () {
    echo '
    <style type="text/css">
        .login .button-primary {
            background-color: #0073aa;
            border-color: #006799;
            color: #fff;
            text-shadow: none;
            box-shadow: none;
        }
        .login .button-primary:hover {
            background-color: #005a8e;
            border-color: #004f7a;
        }
    </style>';
});

Custom Footer Text

Add a custom message or copyright notice in the footer of the login page.

add_action('login_footer', function () {
    echo '<div style="text-align: center; margin-top: 20px;">© ' . date('Y') . ' Your Website. All rights reserved.</div>';
});

Conclusion

Customizing the WordPress login page is a powerful way to enhance your site’s branding and improve security. By leveraging WordPress hooks and filters, you can modify the login page without relying on external plugins. Start customizing your login page today to create a more personalized and secure experience for your users.

Whether you’re adding custom styles, modifying error messages, or changing the login URL, these tweaks will help your site make a great first impression from the moment users log in. Embrace these customizations to ensure your WordPress site is as unique and professional as your brand.

The post How To Customize the WordPress Login Page Without a Plugin appeared first on Adam Balée Designs, LLC.

As always, when it comes to WordPress, there are multiple ways to achieve the same goal.

Method 1: register_post_type

First, let’s suppose you have registered a custom post type in your theme or plugin. If that is the case, you can simply update the menu_icon parameter in the register_post_type arguments.

Pass a base64-encoded SVG using a data URI, which will be colored to match the color scheme — this should begin with ‘data:image/svg+xml;base64,’.

I’m using a free FontAwesome icon in this case, and you can copy the svg code directly from their website. That said, not all icons are created equal, and you may have to tweak them a bit to get it to display correctly. In the case of FontAwesome icons, I had to add a fill="currentColor" to the icon to make it work.

/**
 * Register custom post type
 *
 * @see https://developer.wordpress.org/reference/functions/register_post_type/
 *
 * @return void
 */
register_post_type( 'people', array(
    'labels' => array(
	'name' => 'People',
	'singular_name' => 'People',
	'all_items' => 'All People',
    ),
    'menu_icon' => 'data:image/svg+xml;base64,' . base64_encode('<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 640 512" fill="currentColor"><!--!Font Awesome Free 6.5.2 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free Copyright 2024 Fonticons, Inc.--><path d="M72 88a56 56 0 1 1 112 0A56 56 0 1 1 72 88zM64 245.7C54 256.9 48 271.8 48 288s6 31.1 16 42.3V245.7zm144.4-49.3C178.7 222.7 160 261.2 160 304c0 34.3 12 65.8 32 90.5V416c0 17.7-14.3 32-32 32H96c-17.7 0-32-14.3-32-32V389.2C26.2 371.2 0 332.7 0 288c0-61.9 50.1-112 112-112h32c24 0 46.2 7.5 64.4 20.3zM448 416V394.5c20-24.7 32-56.2 32-90.5c0-42.8-18.7-81.3-48.4-107.7C449.8 183.5 472 176 496 176h32c61.9 0 112 50.1 112 112c0 44.7-26.2 83.2-64 101.2V416c0 17.7-14.3 32-32 32H480c-17.7 0-32-14.3-32-32zm8-328a56 56 0 1 1 112 0A56 56 0 1 1 456 88zM576 245.7v84.7c10-11.3 16-26.1 16-42.3s-6-31.1-16-42.3zM320 32a64 64 0 1 1 0 128 64 64 0 1 1 0-128zM240 304c0 16.2 6 31 16 42.3V261.7c-10 11.3-16 26.1-16 42.3zm144-42.3v84.7c10-11.3 16-26.1 16-42.3s-6-31.1-16-42.3zM448 304c0 44.7-26.2 83.2-64 101.2V448c0 17.7-14.3 32-32 32H288c-17.7 0-32-14.3-32-32V405.2c-37.8-18-64-56.5-64-101.2c0-61.9 50.1-112 112-112h32c61.9 0 112 50.1 112 112z"/></svg>'),
    'public' => true,
    'show_in_rest' => true,
    'supports' => array(
	0 => 'title',
	1 => 'editor',
	2 => 'thumbnail',
    ),
    'delete_with_user' => false,
));

Method 2: registered_post_type

In the case where your custom post type has been registered by a third-party plugin, and you don’t want to alter the code, you can use the registered_post_type hook to update the menu_icon parameter like so. Keep in mind, this method can also be used to replace any of the default registered post types as well (ie. Posts, Media, Pages, etc…)

/**
 * Add custom post type icon
 * 
 * @see https://developer.wordpress.org/reference/hooks/registered_post_type/
 * 
 * @param string $post_type
 * @param object $post_type_object
 * 
 * @return void
 */
add_action('registered_post_type', function ($post_type, $post_type_object) {
    if ($post_type === 'people') {
        $post_type_object->menu_icon = 'data:image/svg+xml;base64,' . base64_encode('<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 640 512" fill="currentColor"><!--!Font Awesome Free 6.5.2 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free Copyright 2024 Fonticons, Inc.--><path d="M72 88a56 56 0 1 1 112 0A56 56 0 1 1 72 88zM64 245.7C54 256.9 48 271.8 48 288s6 31.1 16 42.3V245.7zm144.4-49.3C178.7 222.7 160 261.2 160 304c0 34.3 12 65.8 32 90.5V416c0 17.7-14.3 32-32 32H96c-17.7 0-32-14.3-32-32V389.2C26.2 371.2 0 332.7 0 288c0-61.9 50.1-112 112-112h32c24 0 46.2 7.5 64.4 20.3zM448 416V394.5c20-24.7 32-56.2 32-90.5c0-42.8-18.7-81.3-48.4-107.7C449.8 183.5 472 176 496 176h32c61.9 0 112 50.1 112 112c0 44.7-26.2 83.2-64 101.2V416c0 17.7-14.3 32-32 32H480c-17.7 0-32-14.3-32-32zm8-328a56 56 0 1 1 112 0A56 56 0 1 1 456 88zM576 245.7v84.7c10-11.3 16-26.1 16-42.3s-6-31.1-16-42.3zM320 32a64 64 0 1 1 0 128 64 64 0 1 1 0-128zM240 304c0 16.2 6 31 16 42.3V261.7c-10 11.3-16 26.1-16 42.3zm144-42.3v84.7c10-11.3 16-26.1 16-42.3s-6-31.1-16-42.3zM448 304c0 44.7-26.2 83.2-64 101.2V448c0 17.7-14.3 32-32 32H288c-17.7 0-32-14.3-32-32V405.2c-37.8-18-64-56.5-64-101.2c0-61.9 50.1-112 112-112h32c61.9 0 112 50.1 112 112z"/></svg>');
    }
}, 10, 2);

Method 3: Using CSS

Instead of adding an inline svg, we have a third option available to us. We can simply leave the menu_icon parameter empty, and then add our own with CSS. This method requires two steps.

1. Make sure the menu_icon parameter is empty in the register_post_type or registered_post_type functions respectively.
2. Add custom CSS to the WordPress admin with the following code.

We can either create our own stylesheet and enqueue it in the admin.

/**
 * Add styles to admin
 * 
 * @see https://developer.wordpress.org/reference/hooks/admin_enqueue_scripts/
 * 
 * @return void
 */
add_action( 'admin_enqueue_scripts', function () {
    wp_enqueue_style( 'admin-custom', get_stylesheet_directory_uri() . '/admin-custom.css');
});

Or, we can add inline styles directly to the admin_head. Emojis are still , right?

/**
 * Add styles to admin menu
 * 
 * @see https://developer.wordpress.org/reference/hooks/admin_head/
 * 
 * @return void
 */
add_action( 'admin_head', function () {
    echo '
        <style>
		#adminmenu #menu-posts-people div.wp-menu-image:before {
			content: "👽";
		}
	</style>
    ';
});

The post How To Add Inline SVG Menu Icons to WordPress Custom Post Types appeared first on Adam Balée Designs, LLC.

Fortunately, the WordPress REST API provides us with the register_rest_field function, which we can use to add custom properties to the JSON response. Let’s add a formatted date to the post object response by hooking into the rest_api_init function and registering our new field.

/**
 * Add a Formatted Date to the WordPress REST API JSON Post Object
 *
 * https://adambalee.com/?p=1547
 */
add_action('rest_api_init', function() {
    register_rest_field(
        array('post'),
        'formatted_date',
        array(
            'get_callback'    => function() {
                return get_the_date();
            },
            'update_callback' => null,
            'schema'          => null,
        )
    );
});

Adding the code above to functions.php will return the following result in the JSON post object returned by the WordPress REST API.

{
    "formatted_date": "December 24, 2019"
}

The post Add a Formatted Date to the WordPress REST API JSON Response appeared first on Adam Balée Designs, LLC.

Lazy loading is a technique used to defer the downloading of resources by the browser before they are needed. As a user scrolls down the page, images will come into view as they enter the window. Not only will lazy loading images improve the performance of your site, it also helps to create a smoother experience for your users.

The Javascript

In this example, we’ll be using lazysizes to handle the javascript. Check out the Github repo for detailed installation and usage instructions.

The PHP

Assuming you have lazysizes installed, let’s get to the code we need to start lazy loading our images in WordPress.

The wp_get_attachment_image function is how we create an HTML img element representing an image attachment in WordPress. It provides us with a number of properties that allow us to modify the output we need to start lazy loading our images.

// getting the featured image id as an example
$attachment_id = get_post_thumbnail_id( $post->ID );
$size = 'large';
echo wp_get_attachment_image( $attachment_id, $size, false, [
    'class' => 'lazyload',
    'src' => '#',
    'srcset' => '#',
    'data-src' => wp_get_attachment_image_url( $attachment_id, $size ),
    'data-srcset' => wp_get_attachment_image_srcset( $attachment_id, $size )
]);

Now you could just place the code above in your templates and call it a day, but we can do better. Let’s wrap our code in a neat little function that we can call instead.

function lazy_attachment($attachment_id, $size)
{
    echo wp_get_attachment_image( $attachment_id, $size, false, [
        'class' => 'lazyload',
        'src' => '#',
        'srcset' => '#',
        'data-src' => wp_get_attachment_image_url( $attachment_id, $size ),
        'data-srcset' => wp_get_attachment_image_srcset( $attachment_id, $size )
    ]);
}

Place the code above in your functions.php file and you can now call your lazy loading images with a single line of code.

lazy_attachment($attachment_id, $size);

Remember to replace $attachment_id and $size with the their appropriate values. The following example pulls in the ‘large’ version of a featured image.

lazy_attachment(get_the_post_thumbnail($post->ID, 'large');

The post Lazy Loading Responsive Images in WordPress Without a Plugin appeared first on Adam Balée Designs, LLC.

cat ~/.ssh/id_rsa.pub | pbcopy

The post Copy SSH Public Key to Clipboard appeared first on Adam Balée Designs, LLC.

The Problem

Apparently, this is a really common issue, and there is some fantastic documentation in the WordPress Codex that deals with this exact problem. The following is a direct quote that explains the problem in a nutshell.

… the offset argument is actually the value WordPress uses to handle pagination itself. If a developer sets a manual offset value, pagination will not function because that value will override WordPress’s automatic adjustment of the offset for a given page.

I’m not going to go over everything in the Codex, but I highly suggest you give it a read. Basically, it outlines how to use the pre_get_posts hook, in combination with the found_posts filter, to offset a specific page and/or query, and then adjust the found_posts calculation needed to fix our pagination problem. Unfortunately, the suggested code wasn’t working for me, and I needed to make a minor adjustment to the conditional statements in order for it to work.

The Codex suggests the following conditional statement in the pre_get_posts hook.

// Before anything else, make sure this is the right query...
if ( ! $query->is_home() ) {
    return;
}

This conditional merely checks whether or not the query object is on the home page. In my case, additional calls to the WP_Query object were causing this code to fail. The pre_get_posts hook was being applied to every query on the page and the results were less than desirable.

The Solution

It’s highly likely that you have more than one query on your blog’s home page. If that’s the case, we need to be a bit more explicit with our conditional statements. We need to make sure that the query is not only on our blog’s home page, but that we’re only targeting the main query on that page.

<?php   
/**
 *
 * Offset the main query on our blog's home page
 *
 */
function myprefix_query_offset(&$query) {

    // Before anything else, make sure this query is on our
    // blog's home page, and that it's the main query...
    if ( $query->is_home() && $query->is_main_query() ) {

        // First, define your desired offset...
        $offset = 1;

        // Next, determine how many posts per page you want (we'll use WordPress's settings)
        $ppp = get_option('posts_per_page');

        // Next, detect and handle pagination...
        if ( $query->is_paged ) {

            // Manually determine page query offset (offset + current page (minus one) x posts per page)
            $page_offset = $offset + ( ($query->query_vars['paged']-1) * $ppp );

            // Apply adjust page offset
            $query->set('offset', $page_offset );

        }
        else {

            // This is the first page. Just use the offset...
            $query->set('offset',$offset);

        }

    } else {

        return;

    }
}
add_action('pre_get_posts', 'myprefix_query_offset', 1 );

/**
 *
 * Adjust the found_posts according to our offset.
 * Used for our pagination calculation.
 *
 */
function myprefix_adjust_offset_pagination($found_posts, $query) {

    // Define our offset again...
    $offset = 1;

    // Ensure we're modifying the right query object...
    if ( $query->is_home() && $query->is_main_query() ) {
        // Reduce WordPress's found_posts count by the offset... 
        return $found_posts - $offset;
    }
    return $found_posts;
}
add_filter('found_posts', 'myprefix_adjust_offset_pagination', 1, 2 );

The post How to Offset WordPress Queries without Breaking Pagination appeared first on Adam Balée Designs, LLC.

Create a Custom Widget

First we need to create a new file for our custom widget. Let’s name it acf-custom-widget.php and add it in a new directory to keep things nice and tidy. I recommend the following directory structure, but feel free to place the file anywhere you like:

-- theme
---- inc
------ plugins
-------- acf
---------- acf-custom-widget.php

Next let’s include our new file in our functions.php file. Open up functions.php and add the following code:

include_once( get_stylesheet_directory() . '/inc/plugins/acf/acf-custom-widget.php');

Now we’re ready to add the custom widget code to our new file. Open acf-custom-widget.php and add the following code:

<?php

/**
 * A custom ACF widget.
 */
class ACF_Custom_Widget extends WP_Widget {

    /**
    * Register widget with WordPress.
    */
    function __construct() {
        parent::__construct(
            'acf_custom_widget', // Base ID
            __('ACF Custom Widget', 'text_domain'), // Name
            array( 'description' => __( 'A custom ACF widget', 'text_domain' ), 'classname' => 'acf-custom-widget' ) // Args
        );
    }

    /**
    * Front-end display of widget.
    *
    * @see WP_Widget::widget()
    *
    * @param array $args     Widget arguments.
    * @param array $instance Saved values from database.
    */
    public function widget( $args, $instance ) {
        echo $args['before_widget'];
        if ( !empty($instance['title']) ) {
            echo $args['before_title'] . apply_filters( 'widget_title', $instance['title'] ). $args['after_title'];
        }

        echo get_field('title', 'widget_' . $args['widget_id']);


        // Place your ACF code here


        echo $args['after_widget'];
    }

    /**
    * Back-end widget form.
    *
    * @see WP_Widget::form()
    *
    * @param array $instance Previously saved values from database.
    */
    public function form( $instance ) {
        if ( isset($instance['title']) ) {
            $title = $instance['title'];
        }
    ?>
    <p>
      <label for="<?php echo $this->get_field_id( 'title' ); ?>"><?php _e( 'Title' ); ?></label>
      <input class="widefat" id="<?php echo $this->get_field_id( 'title' ); ?>" name="<?php echo $this->get_field_name( 'title' ); ?>" type="text" value="<?php echo esc_attr( $title ); ?>">
    </p>
    <?php
    }

    /**
    * Sanitize widget form values as they are saved.
    *
    * @see WP_Widget::update()
    *
    * @param array $new_instance Values just sent to be saved.
    * @param array $old_instance Previously saved values from database.
    *
    * @return array Updated safe values to be saved.
    */
    public function update( $new_instance, $old_instance ) {
        $instance = array();
        $instance['title'] = ( ! empty( $new_instance['title'] ) ) ? strip_tags( $new_instance['title'] ) : '';

        return $instance;
    }

} // class ACF_Custom_Widget

// register ACF_Custom_Widget widget
add_action( 'widgets_init', function(){
  register_widget( 'ACF_Custom_Widget' );
});

Let’s make sure everything is working properly. Log in to your dashboard and navigate to Appearance > Widgets. You should now see our new ACF Custom Widget listed among the available widgets.

Create an ACF Field Group

Now it’s time to create a new field group for our widget using Advanced Custom Fields. I’m going to name mine ‘Custom Widget’ and add a simple ‘textarea’ field to the group. Make sure to select ‘Widget’ in the locations menu and then set it equal to our new custom widget.

All custom fields that you add to this new group should now appear in your widget. The last thing we need to do is add the custom field code to our widget.

Add Custom Fields Code

It’s time for the good part. Open up the acf-custom-widget.php file we created earlier and add the custom field code.

<?php

/**
 * A custom ACF widget.
 */
class ACF_Custom_Widget extends WP_Widget {

    /**
    * Register widget with WordPress.
    */
    function __construct() {
        parent::__construct(
            'acf_custom_widget', // Base ID
            __('ACF Custom Widget', 'text_domain'), // Name
            array( 'description' => __( 'A custom ACF widget', 'text_domain' ), 'classname' => 'acf-custom-widget' ) // Args
        );
    }

    /**
    * Front-end display of widget.
    *
    * @see WP_Widget::widget()
    *
    * @param array $args     Widget arguments.
    * @param array $instance Saved values from database.
    */
    public function widget( $args, $instance ) {
        echo $args['before_widget'];
        if ( !empty($instance['title']) ) {
            echo $args['before_title'] . apply_filters( 'widget_title', $instance['title'] ). $args['after_title'];
        }

        echo get_field('title', 'widget_' . $args['widget_id']);


        // BEGIN ACF CODE
        if ( get_field('content') ) {
            echo '<div class="content">'
                . get_field('content') . 
            '</div>';
        }
        // END ACF CODE


        echo $args['after_widget'];
    }

    /**
    * Back-end widget form.
    *
    * @see WP_Widget::form()
    *
    * @param array $instance Previously saved values from database.
    */
    public function form( $instance ) {
        if ( isset($instance['title']) ) {
            $title = $instance['title'];
        }
    ?>
    <p>
      <label for="<?php echo $this->get_field_id( 'title' ); ?>"><?php _e( 'Title' ); ?></label>
      <input class="widefat" id="<?php echo $this->get_field_id( 'title' ); ?>" name="<?php echo $this->get_field_name( 'title' ); ?>" type="text" value="<?php echo esc_attr( $title ); ?>">
    </p>
    <?php
    }

    /**
    * Sanitize widget form values as they are saved.
    *
    * @see WP_Widget::update()
    *
    * @param array $new_instance Values just sent to be saved.
    * @param array $old_instance Previously saved values from database.
    *
    * @return array Updated safe values to be saved.
    */
    public function update( $new_instance, $old_instance ) {
        $instance = array();
        $instance['title'] = ( ! empty( $new_instance['title'] ) ) ? strip_tags( $new_instance['title'] ) : '';

        return $instance;
    }

} // class ACF_Custom_Widget

// register ACF_Custom_Widget widget
add_action( 'widgets_init', function(){
  register_widget( 'ACF_Custom_Widget' );
});

Conclusion

That’s pretty much it! With the basic structure for our widget in place, we now have the ability to create complex widgets using any number or combination of ACF field types.

The post How to Create Custom Widgets with Advanced Custom Fields appeared first on Adam Balée Designs, LLC.

One of the first things I started doing was to download and install WordPress via the command line. I bookmarked an article with the code and referred back to it regularly. Eventually I discovered how to create aliases and realized I didn’t have to remember the code at all. I only had to create an alias and remember the one word command I assigned to it.

There are a few different ways to create an alias, but I prefer to create my own .aliases file so I can keep everything nice and tidy. I’m doing this on a mac, but I’m sure the process is somewhat similar on Windows.

First, create the .aliases file in your user directory.

$ cd ~
$ touch .aliases

Next, in the same directory, we need to add the .aliases file to our .bashrc or .bash_profile. If you don’t see this file, go ahead and create one, and add the following using your editor.

. ~/.aliases

Now open the .aliases file in your favorite editor and add the following.

# WordPress
alias wordpress='wget https://wordpress.org/latest.tar.gz; tar xfz latest.tar.gz; mv wordpress/* ./; rmdir ./wordpress/; rm -f latest.tar.gz;'

That’s it! From now on, all you need to do to download and install WordPress is to type one word…

$ wordpress

The post Create an Alias to Download and Unzip WordPress via the Command Line appeared first on Adam Balée Designs, LLC.

Left Join

The ‘postmeta’ table is where all the custom field data is stored in the database. By default, the WordPress search functionality is set to search the ‘posts’ table only. In order to include the custom fields data in our search, we first need to perform a left join on the ‘posts’ and ‘postmeta’ tables in the database.

/**
 * Join posts and postmeta tables
 *
 * http://codex.wordpress.org/Plugin_API/Filter_Reference/posts_join
 */
function cf_search_join( $join ) {
    global $wpdb;

    if ( is_search() ) {    
        $join .=' LEFT JOIN '.$wpdb->postmeta. ' ON '. $wpdb->posts . '.ID = ' . $wpdb->postmeta . '.post_id ';
    }

    return $join;
}
add_filter('posts_join', 'cf_search_join' );

Modify the Query

Next we need to modify the WordPress search query to include custom fields.

/**
 * Modify the search query with posts_where
 *
 * http://codex.wordpress.org/Plugin_API/Filter_Reference/posts_where
 */
function cf_search_where( $where ) {
    global $pagenow, $wpdb;

    if ( is_search() ) {
        $where = preg_replace(
            "/\(\s*".$wpdb->posts.".post_title\s+LIKE\s*(\'[^\']+\')\s*\)/",
            "(".$wpdb->posts.".post_title LIKE $1) OR (".$wpdb->postmeta.".meta_value LIKE $1)", $where );
    }

    return $where;
}
add_filter( 'posts_where', 'cf_search_where' );

Prevent Duplicates

Finally, we need to add the DISTINCT keyword to the SQL query in order to prevent returning duplicates.

/**
 * Prevent duplicates
 *
 * http://codex.wordpress.org/Plugin_API/Filter_Reference/posts_distinct
 */
function cf_search_distinct( $where ) {
    global $wpdb;

    if ( is_search() ) {
        return "DISTINCT";
    }

    return $where;
}
add_filter( 'posts_distinct', 'cf_search_distinct' );

Wrapping It Up

Add the following to functions.php to start searching WordPress by custom fields. Not only will this code modify the search on the front-end, but you’ll also be able to search the edit screens in the admin by custom fields as well.

<?php
/**
 * Extend WordPress search to include custom fields
 *
 * https://adambalee.com
 */

/**
 * Join posts and postmeta tables
 *
 * http://codex.wordpress.org/Plugin_API/Filter_Reference/posts_join
 */
function cf_search_join( $join ) {
    global $wpdb;

    if ( is_search() ) {    
        $join .=' LEFT JOIN '.$wpdb->postmeta. ' ON '. $wpdb->posts . '.ID = ' . $wpdb->postmeta . '.post_id ';
    }

    return $join;
}
add_filter('posts_join', 'cf_search_join' );

/**
 * Modify the search query with posts_where
 *
 * http://codex.wordpress.org/Plugin_API/Filter_Reference/posts_where
 */
function cf_search_where( $where ) {
    global $pagenow, $wpdb;

    if ( is_search() ) {
        $where = preg_replace(
            "/\(\s*".$wpdb->posts.".post_title\s+LIKE\s*(\'[^\']+\')\s*\)/",
            "(".$wpdb->posts.".post_title LIKE $1) OR (".$wpdb->postmeta.".meta_value LIKE $1)", $where );
    }

    return $where;
}
add_filter( 'posts_where', 'cf_search_where' );

/**
 * Prevent duplicates
 *
 * http://codex.wordpress.org/Plugin_API/Filter_Reference/posts_distinct
 */
function cf_search_distinct( $where ) {
    global $wpdb;

    if ( is_search() ) {
        return "DISTINCT";
    }

    return $where;
}
add_filter( 'posts_distinct', 'cf_search_distinct' );

The post Search WordPress by Custom Fields without a Plugin appeared first on Adam Balée Designs, LLC.