user www-data;
worker_processes 4;
pid /run/nginx.pid;| #!/usr/bin/env bash | |
| # Install Magento sample data from pre-existing archive | |
| # Just find and replace version number | |
| # Run this from the projectroot of the vhost (usually folder with www and logs in it) | |
| # | |
| # What it does: | |
| # | |
| # 1. Copy media folder into current folder | |
| # 2. Copy skin folder into current folder | |
| # 3. Copy local.xml into app/etc ready for editing |
- Login to Magento.com and find your account ID.
- Go to
Account Settings > Downloads Access Tokenand generate a new token. - cURL (or wget) the following URL to make sure you can authenticate:
https://MAG_ID:[email protected]/products/downloads/info/help
Example:
$ curl -k https://MAG_ID:[email protected]/products/downloads/info/helpNote: This guide assumes you are using PHP-FPM and Ubuntu 16.04
Speed (and therefore time) is of the essence
Xdebug is a fantastic tool which can save hours or even days of debugging effort.
Yet just enabling the extension itself will slow down Magento. Composer will also warn you of performance degradation when running it with Xdebug enabled.
- Basic concepts of asynchronous programming
- Using it to process queues
- Any other angles?
In this talk, I'll discuss how to appply asynchronous programming techniques to solve common problems in Magento.
After a quick introduction to the basics of asynchronous programming, I'll show you how frameworks like ReactPHP and AmPHP can take PHP beyond the traditional 'run the script, execute some code and die' paradigm and demonstrate some novel and unique ways that asynchronous programming can be used in your Magento store.
- (/) Check the patch release notes for any dependencies. Some patches need to have other patches applied/reverted before they can be applied successfully
- (/) Check if earlier patches need to be reverted and a newer version installed first
- (/) Download patch
- (/) Make it executable
- (/) Run patch helper
- (/) Apply patch
- (/) Move the patch file to /app/etc/patches
- (/) Manually add files created by the patch to git
- (/) Commit the patch changes before manually merging any changes
PHP Fatal error: Uncaught Error: Class "Monolog\Logger" not found in ./vendor/monolog/monolog/src/Monolog/Handler/AbstractHandler.php:60
This occurred because the PHP PSR extension php8.3-psr was enabled, but is apparently 'broken' (see Seldaek/monolog#1876 (comment)). Disabling the extension fixed the problem.
If that's not it, then try these steps:
- Power user tip: If the error message or error description sounds familiar, check your list of previous solutions, before you spend hours debugging.
- Otherwise, start gathering evidence:
- From error logs, error messages, unusual behaviour, entities with missing information (e.g. Orders, customers, products)
- Reproducibility: If it can't be reproduced, it'll be hard, if not impossible to debug. Wait for it to occur regularly before investing time in debugging it.