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.
Fix term counts so wp-admin Taxonomy listings show the correct number of items for the selected post_type.
| <?php | |
| array ( | |
| '^wp-json/?$' => 'index.php?rest_route=/', | |
| '^wp-json/(.*)?' => 'index.php?rest_route=/$matches[1]', | |
| '^index.php/wp-json/?$' => 'index.php?rest_route=/', | |
| '^index.php/wp-json/(.*)?' => 'index.php?rest_route=/$matches[1]', | |
| 'robots\\.txt$' => 'index.php?robots=1', | |
| '.*wp-(atom|rdf|rss|rss2|feed|commentsrss2)\\.php$' => 'index.php?feed=old', | |
| '.*wp-app\\.php(/.*)?$' => 'index.php?error=403', | |
| '.*wp-register.php$' => 'index.php?register=true', |
| import { exec } from "node:child_process"; | |
| export function callExec() { | |
| return new Promise((resolve, reject) => { | |
| exec(`ls -la`, (error, stdout, stderr) => { | |
| if (error) { | |
| reject(error); | |
| return; | |
| } | |
| if (stdout) { |
| /** | |
| * For ADP's 2022 sexual harrassment training | |
| */ | |
| cr = () => { | |
| const next = $('button.next-button:not(.disabled)') | |
| if (next.length) { | |
| next.click(); | |
| } |
post_type to Posts in phpMyAdmin:
UPDATE `wp_posts` SET `post_type` = 'post' WHERE `post_type` = 'news';/news/%postname%/| # Cron on modern macOS systems (10.14+) requires Full Disk Access permissions | |
| # in System Preferences->Privacy & Security. To enable this, drag the cron | |
| # binary from /usr/sbin/cron into the Full Disk Access list. | |
| # More here: https://apple.stackexchange.com/a/372810/42898 | |
| # https://gist.github.com/joemaller/c4c0a6000ac53c8b1a70ff66c547380a | |
| # Removes downloads older than 14 days. Runs every 6 hours | |
| 45 */6 * * * echo "$(date)\nRemoving downloads older than 14 days (cron)" >> /tmp/cron.log | |
| 45 */6 * * * find ~/Downloads -maxdepth 1 -mtime +14 -exec du -sh {} \+ | sort -rh >> /tmp/cron.log | |
| 46 */6 * * * find ~/Downloads -maxdepth 1 -mtime +14 -exec rm -rf {} \; >> /tmp/cron.log 2>&1 |
| #!/usr/bin/env bash | |
| # Download this file then run: | |
| # % chmod a+x setup.sh | |
| # % ./setup.sh | |
| # Or run directly from this Gist: | |
| # % curl https://gist.githubusercontent.com/joemaller/55aca1bcffe44558cf93527153d6896a/raw/setup.sh | bash | |
| # Install Homebrew first https://brew.sh | |
| set -u |
I've been running all my dev projects via Docker to avoid the pitfalls of installing server software on my computer. This also lets me jump between macheines very easily since everything I need is wrapped up in dockerfiles, docker-compose files or package.json scripts.
WordPress development doesn't work like that. The default development environment expects PHP to be installed and will try to run PHPCS validation checks from a local instance of PHP.
The official Composer Docker image is extremely versatile. It can run arbitrary shell commands if the passed argument isn't a Composer keyword.
WordPress v6.3.1 inlines styles for used blocks via the wp_head hook. However there is an additional wrinkle. If the SCRIPT_DEBUG constant is set and truthy, then a minimized copy of the styles will be inlined. The minimized copy is pre-generated and included with WordPress.
Code for choosing to use the min variant is in wp-includes/blocks.php:
// Check whether styles should have a ".min" suffix or not.
$suffix = SCRIPT_DEBUG ? '' : '.min';
if ( $is_core_block ) {
$style_path = ( 'editorStyle' === $field_name ) ? "editor{$suffix}.css" : "style{$suffix}.css";
}