Magento 2 and avoiding the rabbit hole

transcript

@TONEGOLF71 @SPACE48ERS

#MAGETITANSIT

MAGENTO 2 AND AVOIDING THE RABBIT HOLE

Tony Brown

#MAGETITANSIT

Imagine…• You’re on the “learn Magento 2” journey

• You hit a tricky problem which isn’t easy to diagnose

• What do you do?

• How can you avoid losing time when learning / fixing problems?

#MAGETITANSIT

• Worked on Magento since 1.2

• Technical Director @ Space 48

• Love learning and collaborating

#MAGETITANSIT

Overview

• Magento 1 to Magento 2

• A learning / debugging technique

• Magento 2 development environment

• Problem solving example in M2

#MAGETITANSIT

Magento 1 to Magento 2• Architecture changes

• Makes it easier to write tests

• More isolation of code

• More component friendly

• Mechanisms for more targeted changes

• Test coverage

#MAGETITANSIT

What does this mean?

• Your WTF per minute rate is going to increase for a while!

#MAGETITANSIT

Learning / Debugging Technique

• Debugging and Magento : https://youtu.be/xCjPQfuxxxQ

• Time can run away

• Regularly stepping back

• Pomodoro technique

#MAGETITANSIT

Dev Environment / Infrastructure

• VM via Vagrant

• Nginx, PHP-PFM (v7) with Xdebug

• Percona MySql

• Varnish

• SSL

#MAGETITANSIT

Varnish

#MAGETITANSIT

Problem Solving Example

#MAGETITANSIT

The problem

Varnish for Full Page Cache

SSL for the front-end

No navigation menu in Luma

#MAGETITANSIT

Research for M2 FPC

• Magento Stackexchange

• Same problem, but no answers! http://goo.gl/xK7VQi

• Alan Kent article

• http://devdocs.magento.com

• Other blog posts inc. Alan Storm: http://goo.gl/o4Z107

#MAGETITANSIT

FPC with Varnish

• Varnish holds content responses for URL requests

• Magento decides if a page should be cached or not

• Ajax is used for private data

• ESI is used for finer control of public cache

#MAGETITANSIT

Debugging Steps

• Are there any errors in the Magento Logs?

• Are there any console errors?

• Examine the HTML output?

#MAGETITANSIT

Output over HTTPS

#MAGETITANSIT

Output over HTTP

#MAGETITANSIT

Debugging Steps

• Examine Varnish cache headers

#MAGETITANSIT

Debugging Steps• Find the block definition

/vendor/magento/module-theme/view/frontend/layout/default.xml

#MAGETITANSIT

Debugging Steps

• Step through the code:

• /vendor/magento/module-page-cache/Model/App/FrontController/VarnishPlugin.php

#MAGETITANSIT

HTTPS = Not working

HTTP = working

#MAGETITANSIT

Debugging Steps

• Visit the ESI Controller directly

#MAGETITANSIT

HTTPS HTTP

magento2.local/page_cache/block/esi/blocks/[%22catalog.topnav%22]/handles/…

#MAGETITANSIT

Debugging Steps

• Verify the ESI Controller is being called by Varnish

#MAGETITANSIT

Debugging Steps• Looking for Varnish logs?… use varnishlog

#MAGETITANSIT

Debugging Steps• Search for the error

• An old Varnish ticket was found:

By default ignore an <esi:include> with src=" https://..."

Feature +esi_ignore_https treats it as http://... instead.

#MAGETITANSIT

Debugging Steps

#MAGETITANSIT

Conclusion

• Magento 2 has a tricky learning curve

• Take regular breaks to avoid wasting time

• The Varnish FPC implementation is pretty cool!

#MAGETITANSIT

THANKS!!

Any questions?

Magento 2 and avoiding the rabbit hole

Technology