webhouse-dev

RewriteCond %{QUERY_STRING} "fbclid=" [NC]
RewriteRule (.*) /$1? [R=301,L]

webhouse-dev

.site-branding {
  pointer-events: none;
}

webhouse-dev

<?php

add_filter('blocksy:header:logo:url', function ($url) {
  return 'YOUR_URL';
});

webhouse-dev

WooCommerce

• filters
• category description option to move below content
• option to change single product and single category width
• adapt custom attributes in menus and taxonomy archives
• category settings: display subcategory filter
• category featured image

WordPress

• add integration with Mailer Lite

webhouse-dev

add_action( 'woocommerce_thankyou', 'custom_woocommerce_auto_complete_order' );
function custom_woocommerce_auto_complete_order( $order_id ) { 
    if ( ! $order_id ) {
        return;
    }

    $order = wc_get_order( $order_id );
    $order->update_status( 'completed' );
}

webhouse-dev

/**
 * @snippet       Upload WordPress images to day folders
 * @how-to        Add to functions.php or get plugin Code Snippets
 * @author        webhouse.dev
 * @url           https://webhouse.dev
 */

function upload_dir_filter($uploads){
    $day = date('d');
    $uploads['path'] .= '/' . $day;

webhouse-dev

It's not a secret that Redis service is a really great backend caching service. Normally people use that via TCP. It's fast and reliable. However if you do benchmark via unixsocket you will see that it will double amount of requests per second (of course depend on your server but much much faster than TCP). Redis via unixsocket is the best setup to go... however people using CageFS in Cloudlinux will struggle with permissions and they won't be able to connect to unixsocket. Here is the solution!

Step 1: change redis config to use unixsocket (still keeping TCP). In /etc/redis.conf uncomment and change lines:

# Unix socket.
#
# Specify the path for the Unix socket that will be used to listen for
# incoming connections. There is no default, so Redis will not listen
# on a unix socket when not specified.
#