Damien Chantelouve DamChtlv

Remove WooCommerce Bloated Features from WP Admin Menu

Recently WooCommerce has added a lot of improvements to the plugin which we really appriciate but at the same time a lot of bloated features has alos been added to the plugin like Marketing Hub, a completely useless menu taking extra space among the other important menu items. Now if you find Marketing Hub to be useful, you can keep it.

But just in case you are looking for a way to remove these features that you no longer need from your WordPress Admin menus, take a look at the following code snippets. Please note: though I will show you how you can remove the Marketing Hub from your WP Admin menu list completely and make sure WooCommerce doesn't execute codes for that feature you don't need, you can do the same for other WooCommerce features as well like Analytics.

How to remove Marketing Hub for WooCommerce <= v4.2

If you are using WooCommerce <= v4.2, you can simple add this one line of code in your theme's functions.php f

To support my open-source work, consider adding me on Patreon.

macOS 10.14 Mojave Mostly-Automated Setup

An easy to refer to document for regularly setting up macOS 10.14 Mojave.

Controversy

The topic of recipe-based frequent fresh reinstalls of macOS is a controversial issue. Some people are against reinstalling macOS, citing that they have never had an issue with Apple provided upgrade installs.

	# This GitHub workflow will build a WordPress Bedrock site and deploy it to a shared server (french one: O2Switch, but URLs can be adapted) using SSH
	# Actions secrets are used to store sensitive information:
	# - SSH_PRIVATE_KEY: The private key used to authenticate with the remote server
	# - REMOTE_HOST: The hostname of the remote server
	# - REMOTE_USER: The username used to authenticate with the remote server
	# - REMOTE_PROD_TARGET: The path on the remote server where the site will be deployed to
	# - REMOTE_PREPROD_TARGET: The path on the remote server where the site will be deployed to
	# - URL_ENCODED_PASSWORD: The password used to authenticate with the remote server, URL encoded (e.g. using https://www.urlencoder.org/)
	# Workflow triggers on pushes to the develop and master branches:
	# - On the develop branch, the site is deployed to the preprod target

	<?php
	/**
	* Plugin Name: Content Security Policy
	* Version: 1.0.0
	* Description: Adds a Content-Security-Policy header to all non-admin requests.
	* License: GNU General Public License v2
	* License URI: http://www.gnu.org/licenses/gpl-2.0.html
	* Original Inspiration: https://gist.github.com/westonruter/c8b49406391a8d86a5864fb41a523ae9
	*/

	{
	"name": "automatic-wide-width",
	"title": "Automatically Align Wide",
	"description": "A demo block.json for a forced align-wide block",
	"apiVersion": 2,
	"acf": {
	"mode": "edit",
	"renderTemplate": "render.php"
	},
	"supports": {

	{
	"title": "JSON schema for WordPress blocks",
	"$schema": "http://json-schema.org/draft-04/schema#",
	"definitions": {
	"//": {
	"reference": "https://developer.wordpress.org/block-editor/reference-guides/block-api/block-metadata/",
	"attributesReference": "https://developer.wordpress.org/block-editor/reference-guides/block-api/block-attributes/",
	"contextReference": "https://developer.wordpress.org/block-editor/reference-guides/block-api/block-context/",
	"supportsReference": "https://developer.wordpress.org/block-editor/reference-guides/block-api/block-supports/",
	"registerReference": "https://developer.wordpress.org/block-editor/reference-guides/block-api/block-registration/#example-optional"

	<?php
	/**
	* Title: Content-only Test
	* Slug: prefix/content-only-test
	*/
	?>
	<!-- wp:group {"templateLock": "contentOnly", "align":"wide","layout":{"type":"constrained","wideSize":"2000px"}} -->
	<div class="wp-block-group alignwide"><!-- wp:columns -->
	<div class="wp-block-columns"><!-- wp:column -->
	<div class="wp-block-column"><!-- wp:image {"id":231,"sizeSlug":"large","linkDestination":"none"} -->

	# Check your website headers here: https://www.serpworx.com/check-security-headers/ or https://gf.dev/
	# This configuration works for WP, WC on LiteSpeed server. Be careful. Test site after installing. All lines are explained are in serpworx.com tester.

	# More docs:
	# https://www.netsparker.com/whitepaper-http-security-headers/#XFrameOptionsHTTPHeader
	# https://owasp.org/www-project-secure-headers/
	# https://www.keycdn.com/blog/http-security-headers

	# WordPress plugin for Headers setup https://wordpress.org/plugins/http-headers/
	# Main security options in .htaccess file:

	#!/usr/bin/env bash

	# Related to WP CLI as single site, check following link
	# @see https://gist.github.com/MaximeCulea/dbd5835a01d2b4e6a6544919db3f26a0

	# All wp cli comands will be declared both (as much as possible) :
	# - with xargs (not all servers support xargs)
	# - more native shell syntax "for in"

	# WP Crons MS

	#!/usr/bin/env bash

	# Related to WP CLI in Multisite check following link
	# @see https://gist.github.com/MaximeCulea/575e493a061359edbb12cefc3aa4c770

	# Update all post's thumnbail
	wp post update $(wp post list --format=ids --post_type=post) --post_type=post --meta_input='{"_thumbnail_id":"160"}'
	# Generate and add dummy thumbnails to a wanted post type : https://gist.github.com/MaximeCulea/c04e62c4b6e79b4e4e17b73dd023b6c4

	# Search Replace with regex