Leonardo Noering lnoering

WordPress Admin Cleanup Checklist

A fast and safe workflow to review a WordPress/WooCommerce admin and remove unused plugins, ACF groups, CPTs, and clutter.

1. Generate a Plugin Inventory

List all plugins:

Sample to add filters on related products

With one Attribute

function filter_related_products_exclude_attribute_value( $related_product_ids, $product_id ) {

    $filtered_related_product_ids = array();

    foreach ( $related_product_ids as $related_product_id ) {

Find your not compatible custom modules in Magento.

Version - ( 2.4.4 ~ 2.4.5-p1) add code in vendor/magento/framework/Reflection/MethodsMap.php line 143

if($paramReflection->detectType() == NULL)
{
    var_dump($paramReflection->getDeclaringClass());
    die();
}

Creating new environment to test the upgrade

1 - Create new branch from master

git checkout -b cloud/upgrade-2.4.5

2 - Push that branch to cloud

git push -u cloud cloud/upgrade-2.4.5:upgrade-2.4.5

Get all product attributes from entity

SELECT
	ea.attribute_code,
	ea.frontend_label,
	ea.entity_type_id 
FROM 
	eav_attribute AS ea
LEFT JOIN eav_entity_type as eat ON eat.entity_type_code = 'catalog_product'

Magento 2

Get all eav data from specific product

use magento;

SET @ENTITY_TABLE = 'catalog_product_entity';
SET @COLUMNID = 'sku';

Docker from magento cloud at local.

1 - Need start the project.

bash <project-root>/vendor/magento/magento-cloud-docker/bin/init-docker.sh

https://devdocs.magento.com/cloud/docker/docker-development.html

2 - Build the compose

Only on the commerce cloud projects, it goes like this: When branches are ready to deploy to production:

create a release/[yyyymmdd] branch (e.g. release/20220315) from git master
merge feature branches that are ready to deploy to this release branch (push release branch to git repo)
merge the release branch to git production (push git production up to repo)
merge git production to cloud production
merge git production to git master
optional: merge cloud production to cloud master

for all the other "on-premise" projects, we

Zip all modules to install by artifact

Steps

Go to the vendor_name folder.

Ex.: cd vendor/amasty

Create the file at that folder.

Ex.: zip-all.sh

	#!/bin/bash

	#
	# Magento 2 - Backup scripts (database \| media)
	#
	# @author Leonardo <lnoering@gmail.com>
	# @version 1.0.0

	# UnComment it if bash is lower than 4.x version
	shopt -s extglob