MichaelBelgium

# Requires -RunAsAdministrator
# Only works for WSL v2,  this is completely not needed for WSL v1 where u always can use 127.0.0.1 in hosts file

Clear-Host

if ((Get-InstalledModule "Carbon" -ErrorAction SilentlyContinue) -eq $null) {
    Install-Module -Name 'Carbon' -AllowClobber
}

Import-Module 'Carbon'

f9n

Unbound Cheat Sheet

Installation

$ yum install -y unbound

Setup SSL keys for unbound-control

GlauberF

/**
 * Simulate a key event.
 * @param {Number} keyCode The keyCode of the key to simulate
 * @param {String} type (optional) The type of event : down, up or press. The default is down
 * @param {Object} modifiers (optional) An object which contains modifiers keys { ctrlKey: true, altKey: false, ...}
 */
function simulateKey (keyCode, type, modifiers) {
	var evtName = (typeof(type) === "string") ? "key" + type : "keydown";	
	var modifier = (typeof(modifiers) === "object") ? modifier : {};

aperuzzo

/**
 * set transient for excluded states on articles
 * 
 */

add_action( 'edit_term', function($term_id, $tt_id, $taxonomy){
    if($taxonomy == 'state'){
        delete_transient( 'excluded_states' );
        $states = get_terms( array(
            'taxonomy' => 'state',

OmegaRogue

Windows Registry Editor Version 5.00

; Windows terminal

[-HKEY_CLASSES_ROOT\Directory\shell\MenuWindowsTerminal]


[-HKEY_CLASSES_ROOT\Directory\background\shell\MenuWindowsTerminal]

[-HKEY_CLASSES_ROOT\Directory\LibraryFolder\shell\MenuWindowsTerminal]

joemaller

Fixing post counts for WordPress taxonomies

The problem

For WordPress sites using Custom Post Types, Taxonomy admin listings show cumulative term-assignment totals for all post_types instead of counts specific to the selected post_type. Since Taxonomy listings are always attached to a single post_type, totals for shared taxonomies don't make sense.

The Goal

Fix term counts so wp-admin Taxonomy listings show the correct number of items for the selected post_type.

christroutner

/*
  Tests the promise queue (p-queue) and promise retry (p-retry) libraries.
*/

"use strict";

const { default: PQueue } = require("p-queue");
const queue = new PQueue({ concurrency: 1 });

const pRetry = new require("p-retry");

lukecav

wp term list product_tag --format=csv

coltenkrauter

Permanent WSL DNS Fix (WSL 2.2.1+)

If you're encountering ping github.com failing inside WSL with a Temporary failure in name resolution, you're not alone — this has been a long-standing issue, especially when using VPNs or corporate networks.

This issue is now fixed robustly with DNS tunneling, which preserves dynamic DNS behavior and avoids limitations like WSL’s former hard cap of 3 DNS servers in /etc/resolv.conf.

DNS tunneling is enabled by default in WSL version 2.2.1 and later, meaning that if you're still seeing DNS resolution issues, the first and most effective fix is simply to upgrade WSL. Upgrading WSL updates the WSL platform itself, but does not affect your installed Linux distributions, apps, or files.

To upgrade WSL, follow these steps,

hirejordansmith

<?php 

// Adds a custom rule type.
add_filter( 'acf/location/rule_types', function( $choices ){
    $choices[ __("Other",'acf') ]['wc_prod_attr'] = 'WC Product Attribute';
    return $choices;
} );

// Adds custom rule values.
add_filter( 'acf/location/rule_values/wc_prod_attr', function( $choices ){