git filter-branch –commit-filter

Don’t do it. Just don’t.

But suppose someone commits and then reverts a branch with a million files in it. It happens /vendor – I’m looking at you, here.

Make sure your local repo has all the same branches as the remote and that they all track.

git config --add remote.origin.push '+refs/tags/*:refs/tags/*'
git config --add remote.origin.push '+refs/heads/*:refs/heads/*'

for remote_branch in `git branch --all | grep -v HEAD | sed -e 's/\*//'`; do local_branch=`echo $remote_branch | sed -e 's!remotes/origin/!!'`; git checkout $local_branch; done

now get the commit hashes for the commits you need to remove – for example, 2 commits

git filter-branch --commit-filter '
    case $GIT_COMMIT in
    862ff2e9fc5926646bb9381e1a977c806e6f3e9e|862ff2e9fc5926646bb9381e1a977c806e6f3e9e)
        skip_commit "$@"
        ;;
    *)
        git commit-tree "$@"
        ;;
    esac' --tag-name-filter cat -- --all; git reflog expire --expire=now --all; git gc --aggressive --prune=now

force push
repeat in each branch

January 19, 2019January 19, 2019

Magento 2 Plugin Limitations

Limitations

Plugins can not be used on following:

Final methods
Final classes
Non-public methods
Class methods (such as static methods)
__construct
Virtual types
Objects that are instantiated before Magento\Framework\Interception is bootstrapped

January 19, 2019

Magento 2 Custom Router and the Dreaded 100 matches

public function match (\Magento\Framework\App\RequestInterface $request)
{
    if (strpos($request->getPathInfo(), 'test') === false) return;
    $request->setModuleName(‘MyCompany_MyModule’)
       ->setControllerName('test')->setActionName('test');

    return $this->actionFactory->create(
        \Magento\Framework\App\Action\Forward::class, ['request' => $request]
    );
}

https://magento.stackexchange.com/questions/135532/magento-2-ce-front-controller-reached-100-router-match-iterations-issue

December 12, 2018

Magento 2.3 Declarative Schema

In an effort to simplify the Magento installation and upgrade process, 2.3 introduces declarative schema.

With the new declarative schema approach allows, developers are no longer forced to write scripts for each new version of a module. Using declarative schema, developers declare the final desired state of the database, and the system adjusts to it automatically, without performing redundant operations. In addition, this approach allows data to be easily deleted when a module is uninstalled.

There are two parts to using declarative schema: the db_schema.xml file and the bin/magento command to register it.

Once you use declarative schema in a module, you cannot use setup/upgrade scripts again. In the future, upgrade scripts will be phased out in favor of declarative schema.

The following example, extracted from the Catalog/etc/db_schema.xml file, defines the catalog_product_entity_datetime table:

<table name="catalog_product_entity_datetime" resource="default" engine="innodb"
           comment="Catalog Product Datetime Attribute Backend Table">
        <column xsi:type="int" name="value_id" padding="11" unsigned="false" nullable="false" identity="true" comment="Value ID"/>
        <column xsi:type="smallint" name="attribute_id" padding="5" unsigned="true" nullable="false" identity="false"default="0" comment="Attribute ID"/>
        <column xsi:type="smallint" name="store_id" padding="5" unsigned="true" nullable="false" identity="false" default="0" comment="Store ID"/>
        <column xsi:type="int" name="entity_id" padding="10" unsigned="true" nullable="false" identity="false" default="0"/>
        <column xsi:type="datetime" name="value" on_update="false" nullable="true" comment="Value"/>
        <constraint xsi:type="primary" name="PRIMARY">
            <column name="value_id"/>
        </constraint>
</table>

https://magento-devdocs.github.io/devdocs-for-tests/guides/v2.3/extension-dev-guide/declarative-schema/db-schema.html

November 15, 2018

Backend Developer

August 24, 2018

Magento 2 Knockout JS in a Nutshell

We have defined a module with a simple module.xml and a registration.php file,

to call upon the regular flow of M2 merged XML layouts, to define a Block class that feeds data into a PHTML template,

which is then outputting a JSON configuration array that was inserted into the Block class using an XML argument-array,

and which is then used to initialize a custom AMD-style JS component through the Magento_Ui/js/core/app component,

which connects our require JS component to our KnockoutJS component.

Then, our JS component injects the customer-data component to collect a bit of information about the customer, which is fetched through a kind of local-storage-cached-AJAX-call to the backend,

which is configured through a DI type that injects an array of section sources into a backend class,

that fetches data from various sources, including our own, to then send back a bundled response, if possible, to the JS component, with the major feature being JavaScript AJAX lazy loading.

Namespace

/Module

/Block

Block.php

/etc

module.xml

/view

/frontend

/layouts

somelayout_file.xml

/templates

template.phtml

registration.php

July 30, 2018

Add Quantity to Product Widget Grid in Category Edit in Magento 2

Event/Observer

Event: backend_block_widget_grid_prepare_grid_before

Create Module

Namespace\Module\registration.php
Namespace\Module\composer.json
Namespace\Module\etc\module.xml
Namespace\Module\etc\adminhtml\events.xml
Namespace\Module\Model\Observer\BackendBlockWidgetGridPrepareGrid.php

events.xml

<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:framework:Event/etc/events.xsd">
    <event name="backend_block_widget_grid_prepare_grid_before">
        <observer name="category_product_picker_grid"
                  instance="Namespace\Module\Model\Observer\BackendBlockWidgetGridPrepareGrid"
        />
    </event>
</config>

BackendBlockWidgetGridPrepareGrid.php

namespace Namespace\Module\Model\Observer;

use Magento\Framework\Event\ObserverInterface;

class BackendBlockWidgetGridPrepareGrid implements ObserverInterface
{
    public function execute(\Magento\Framework\Event\Observer $observer)
    {
        $grid = $observer->getEvent()->getGrid();
        $grid->addColumn(
            'qty',
            [
                'header' => __('Quantity'),
                'type' => 'number',
                'index' => 'stock'
            ]
        );
        return $this;
    }
}

June 12, 2018

When Magento 2 Makes No Sense

Did you setup:di:compile?

–jennifer

nodwell.net

Posts

Title