albertobraschi

Install GrumPHP in your Magento 2

Create the grumphp.yml in the root folder of your project and run these commands below:

    composer require "phpro/grumphp:^0.14" --dev
    composer require nlubisch/grumphp-easycodingstandard --dev
    composer require wearejust/grumphp-extra-tasks --dev
    composer require jakub-onderka/php-parallel-lint --dev   

albertobraschi

Programas RFB no Wine

Este guia tem como objetivo guardar informações de como rodar os programas da receita federal no Wine.
Visa oferecer uma forma de rodar os programas proprietários do Windows no Linux.

Não use este guia para os programas da RFB baseado em Java!
Os programas da RFB baseados em Java devem rodar na VM Java do Linux nativamente.
Rodar Java no Wine não é recomendado!

Testado com Wine 3.0 no Linux Mint 18.3 64bit

Abreviações

albertobraschi

#Path to shops' active theme (multiple locations allowed, separated by a ' ' (SPACE))
THEME_FOLDER=('pub/static/frontend/Magento/luma/')

#Find deployed themes (languages) and copy the themes. 'us_US' becomes 'us_US_source'. We skip directories already having a '_source' suffix
find ${THEME_FOLDER[@]} -mindepth 1 -maxdepth 1 \( -not -name '*_source' \) -type d -execdir mv -f \{} \{}_source \;

#Find all *_source themes and use them as input for r.js. The output directories are the input directory with '_source' stripped again.
find ${THEME_FOLDER[@]} -mindepth 1 -maxdepth 1 \( -name '*_source' \) -type d -exec bash -c 'r.js -o requirejs-bundle-config.js baseUrl=\{} dir="${@%"_source"}"' bash {} \;

#Find the themes that don't have _source as suffix, assuming these are the ones that are now bundled.

albertobraschi

Magento testing scenarios

For use after an upgrade to verify the correct working of Magento

Frontend

General

• Activate all logs on the server (PHP, MySQL, Magento, mail, etc)
• Check meta tags in HTML

albertobraschi

These set of scripts are for Magento 2. For Magento 1, see this Gist.

albertobraschi

Archive of Debugging tips & tricks with Magento Commerce

Originally posted from https://web.archive.org/web/20171207214530/http://www.molotovbliss.com/debugging-tips-and-tricks-with-magento-commerce

Zend_Debug::Dump

Zend_Debug::dump

Use Zend_Debug::dump($foo); instead of using var_dump($foo); or print_r($foo); it is essentially the same, just a wrapper with pre HTML tag for formatting and escaping of special characters.

albertobraschi

Archive of Debugging tips & tricks with Magento Commerce

Originally posted from https://web.archive.org/web/20171207214530/http://www.molotovbliss.com/debugging-tips-and-tricks-with-magento-commerce

Zend_Debug::Dump

Zend_Debug::dump

Use Zend_Debug::dump($foo); instead of using var_dump($foo); or print_r($foo); it is essentially the same, just a wrapper with pre HTML tag for formatting and escaping of special characters.

albertobraschi

#!/bin/bash

PROGNAME=${0##*/}
INPUT=''
QUIET='0'
NOSTATS='0'
max_input_size=0
max_output_size=0

usage()

albertobraschi

M2 DEV LINKS

Needing a place to keep a list of all the tools/references used during Magento development.

---

OFFICIAL MAGENTO REPOS AROUND M2

• https://github.com/magento/magento2 Mothership
• https://github.com/magento/magento2-sample-data Sample Data
• https://github.com/magento/data-migration-tool M1-to-M2 Data Migration

albertobraschi

####################
#  CLI cheatsheet  #
####################

# cheatsheet directory location:
CHEATDIR=~/.cheatsheet

# Use 'vicheat' to edit the cheatsheet
alias vicheat='vim $CHEATDIR/command_cheatsheet'