- Generate high-level overview of all the main components
- How are the total item counts for each option generated?
- How is the catalog updated to display the matching products?
- How are options rendered?
- What are the customisation points?
- What events are dispatched?
<?php | |
declare(strict_types=1); | |
namespace Vendor\Module\Plugin\Checkout; | |
use Magento\Checkout\Model\DefaultConfigProvider; | |
use Magento\Framework\Stdlib\ArrayManager; | |
class AddProductLabelPlugin |
<?php | |
declare(strict_types=1); | |
namespace Vendor\Module\Service; | |
use Magento\Framework\App\Area as AppArea; | |
use Magento\Framework\App\State as AppState; | |
use Magento\Framework\DataObject; | |
use Magento\Framework\Exception\NoSuchEntityException; |
- Find the commit a GitHub
- Add .patch to the URL
- Require vaimo/composer-patches
- Add an entry like the above, with path-removal-level 5, to the composer.json
source: https://savedlog.com/uncategorized/letsencrypt-ssl-certificate-namecheap-hosting/
The “Positive SSL” certificate I bought along with my domain is invalid with any of my subdomains and cannot be used with wildcards. One annoying thing is that namecheap doesn’t offer auto installation of free let’s encrypt certificates, even though, they are saying “Namecheap is dedicated to data security and privacy for all internet users. We believe the movement to encrypt nearly all web traffic is a positive direction. As more sites embrace HTTPS and use of security products, providers of free SSL are beginning to come online.”
Let me show you what it needs to be done in order to “encrypt nearly all web traffic”.
First, not required but it’s helpful to enable ssh access, it is not enabled by default on the base hosting plans, just go an start a live chat and request ssh access.
FROM ubuntu:16.04 | |
RUN apt-get update && \ | |
apt-get dist-upgrade -y && \ | |
apt-get install -y htop curl nano | |
# Install PHP | |
RUN apt-get install -y php7.0 php7.0-mbstring php7.0-dom |
{ | |
"rules": { | |
"indentation": 4, | |
"block-opening-brace-space-before": "always", | |
"block-opening-brace-newline-after": "always", | |
"block-closing-brace-newline-before": "always", | |
"selector-list-comma-newline-after": "always", | |
"string-quotes": "single", | |
"selector-combinator-space-after": "always", | |
"selector-combinator-space-before": "always", |
At some point you’ll find yourself in a situation where you need edit a commit message. That commit might already be pushed or not, be the most recent or burried below 10 other commits, but fear not, git has your back 🙂.
git commit --amend
This will open your $EDITOR
and let you change the message. Continue with your usual git push origin master
.
# ---------------------------------- | |
# Colors | |
# ---------------------------------- | |
NOCOLOR='\033[0m' | |
RED='\033[0;31m' | |
GREEN='\033[0;32m' | |
ORANGE='\033[0;33m' | |
BLUE='\033[0;34m' | |
PURPLE='\033[0;35m' | |
CYAN='\033[0;36m' |
select p1.sku `parent sku`, group_concat(p2.sku) `associated skus`, lt.code `type` | |
from catalog_product_link l | |
inner join catalog_product_entity p1 on p1.entity_id = l.product_id | |
inner join catalog_product_entity p2 on p2.entity_id = l.linked_product_id | |
inner join catalog_product_link_type lt on l.link_type_id = lt.link_type_id | |
group by l.product_id |