This kind of block has limited editing. So hover over the block that says “Start writing or type” and click the plus sign. Then search for classic and select the option when it appears.

Now you will see a block that is just like the old classic style. This way you don’t need to install the classic editor plugin.

The post WordPress 5 Classic Block appeared first on Magento Wizard | Lakewood Colorado Magento Web Design, E-Commerce, Online Marketing, SEO.

You can easily fix this by installing the module Admin CSS MU. Then you just need to add the following CSS:

I also noticed that the new editor is also buggy. So if you get too frustrated, you can always install the classic editor.

The post WordPress 5 Expand Post/Page Editing Area appeared first on Magento Wizard | Lakewood Colorado Magento Web Design, E-Commerce, Online Marketing, SEO.

Use the Mage2gen Magento 2 module creator to generate basic Magento 2 Modules and code snippets. You can also use the commandline tool to interactively create a Magento 2 module.

The post Magento 2 module creator appeared first on Magento Wizard | Lakewood Colorado Magento Web Design, E-Commerce, Online Marketing, SEO.

The post Microservices + Events + Docker = A Perfect Trio appeared first on Magento Wizard | Lakewood Colorado Magento Web Design, E-Commerce, Online Marketing, SEO.

The post Code This Not That Javascript appeared first on Magento Wizard | Lakewood Colorado Magento Web Design, E-Commerce, Online Marketing, SEO.

1. What is the unit under test (module, function, class, whatever)?
2. What should it do? (Prose description)
3. What was the actual output?
4. What was the expected output?
5. How do you reproduce the failure?

Read the rest of the article here.

The post  5 questions every unit test must answer appeared first on Magento Wizard | Lakewood Colorado Magento Web Design, E-Commerce, Online Marketing, SEO.

https://www.infoq.com/articles/microservices-startup

The post Building Microservices appeared first on Magento Wizard | Lakewood Colorado Magento Web Design, E-Commerce, Online Marketing, SEO.

The Magento 2 Certified Professional Developer exam, a primarily scenario-based exam, is designed to validate the skills and knowledge needed to customize Magento 2 in the areas of: UI modifications, database changes, admin modifications, checkout process customizations, order management integrations and customizations, catalog structure and functionality changes. This exam is for a Magento 2 developer who has a deep understanding of Magento 2 development concepts and experience (recommend 1.5 years) in implemementing and customizing Magento 2.

You can also dig deeper in the full developer documentation located here.

The post Magento 2 appeared first on Magento Wizard | Lakewood Colorado Magento Web Design, E-Commerce, Online Marketing, SEO.

Blocks

Making blocks visible to you and getting info on which template files are displaying which code, is very helpful. This is standard Magento functionality found under System->Configuration->Developer->Debug. Just change the site scope and clear the cache. Now you will see the blocks and their templates surrounded in red.

Logs

My first stop is always logs. There is the standard Magento logs in var/log. I usually start with this command so I can watch for errors:

tail -f system.log

If the error is more serious, I will checkout the exception log. If we are lucky, we might get a report of the error from Magento. In this case you will get a number for the report and can look at the report in var/report.

Most developers in Magento 1 will use Mage::Log($foo); to output info in code to the system log. Just make sure you add some info to tell you where you put this code. For example:

Mage::Log('Shipping module controller: '.$foo);

That way if you forget to remove your logging code, it can be easily found and removed by you or other developers.

In Magento 2, you will need to use these commands to output to the correct log file:

$this->_logger->addDebug($message); // log location: var/log/system.log 
$this->_logger->addInfo($message); // log location: var/log/exception.log 
$this->_logger->addNotice($message); // log location: var/log/exception.log 
$this->_logger->addError($message); // log location: var/log/exception.log 
$this->_logger->critical($e); // log location: var/log/exception.log

Finally you can check the server logs, usually located in /var/log/ and check out Mysql, Php, Apache or Nginx error logs.

Conflicts

Modules often times use the same core Magento methods and thus one module can have parts of it not function correctly. In this case you will need to have one of the modules extended it’s class from another module using the same core method. If you have n98-magerun installed, you can run this command:

n98-magerun.phar dev:module:rewrite:conflicts

There are modules which can help you easily track these down.

Alekeon Module Detector

Boost my Shop Magento Extension Conflict

Extendware Extension Conflict

Template File Overrides

A very common issue, is when a module’s template file is located in the base directory and has been customized and put into the theme directory. Then when someone upgrades the module, the module template file located in the theme directory will override the one in the base directory causing errors. The best approach is to take the base template file and upgrade the code with the changes in the theme directory. Then replace that upgraded template file with the one in the theme directory.

Another issue can be files found in app/code/local/Mage/. These files override the core files. If Magento has been upgraded or patched, these can be defunct and cause problems. It is wise to review these and see if they are still needed. In many cases it would be better to move these into their own custom module.

Developer Tools

Commerce Bug 3 is an amazing toolbar for showing tons of info on what is happening on a particular page.

PHPStorm is an IDE that is very powerful, especially when you combine it with Magicento and Xdebug.

Adminer is a single PHP file to manage your database. Adminer has a fast search that can search all database tables for your keyword.

The post Debugging Magento appeared first on Magento Wizard | Lakewood Colorado Magento Web Design, E-Commerce, Online Marketing, SEO.

When you install Magento 2 you will need newer versions of php and mysql/mariadb. So using the latest version of Debian 9 is very helpful, as it includes latest versions of many software packages. After you install I usually run the following commands so the base system is updated.

apt-get update; apt-get upgrade

Next I like get quickly setup and have control panel to manage my server. My control panel is Webmin with Virtualmin. This will get everything installed like mail servers, bind, spam and virus detection. Virtualmin also has easy install of SSL certificates and managing server limits.

wget http://software.virtualmin.com/gpl/scripts/install.sh; chmod +x install.sh; sh ./install.sh

Some people may feel that this installs too much software on their server. In that case you can avoid Virtualmin and just have Webmin installed or avoid a control panel all together.

Now that you have run the Virtualmin script, you need to stop Apache which it uses by default and install nginx.

systemctl stop apache2.service;apt-get install nginx; apt-get install webmin-virtualmin-nginx webmin-virtualmin-nginx-ssl

Next we need to install all the php modules that are required by Magento 2:

apt-get install -y php7.0 libapache2-mod-php7.0 php7.0 php7.0-common php7.0-gd php7.0-mysql php7.0-mcrypt php7.0-curl php7.0-intl php7.0-xsl php7.0-mbstring php7.0-zip php7.0-bcmath php7.0-iconv php7.0-soap

Now you are ready to setup your Magento 2 website. Make sure you have pointed your domain name to your server IP. When you log into Webmin. You will get an error message from the browser as the browser thinks the site is insecure. Just click the Advanced button/link and add an exception or proceed. You can access the Webmin control panel by:

https://domain.com:10000

Once you are logged in with your root username and password,run through the system setup. Now you need to disable  Apache and activate Nginx. In the Virtualmin tab, choose System Settings -> Features and Plugins.

Now uncheck:

Apache website, SSL website, DAV Login, Mailman, Protected web directories

Now check:

Nginx website and Nginx SSL website

Now click Create Virtual Server. Once you have setup your domain name as a new server, you will need to click on Server Configuration.  Click on Website Options and change PHP script execution mode to FPM.  Right above you will see Manage SSL Certificate. If you click on that option, you can choose Let’s Encrypt tab and Request Certificate.

Now go back to the command line and install sudo and assign the new user, which will be the name of your domain in most cases. If in question, check what Virtualmin created as a username for the domain,

apt-get install sudo zsh; usermod -aG sudo domain

STEP 2: Install Magento 2

Now that you have your domain setup in Virtualmin, SSH into that account.

I like to improve my shell by using ZSH with OH-MY-ZSH. This is optional but a great improvement. Just run the following commands:

sudo apt-get install sudo zsh; sh -c “$(curl -fsSL https://raw.github.com/robbyrussell/oh-my-zsh/master/tools/install.sh)”

Next install composer:

sudo apt-get install composer

To install Magento 2 with composer, you will need to setup an Acess key with your account. Go to:

https://marketplace.magento.com/customer/account/

The public key will be the username and the private key will be the password. Run this composer command:

sudo composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition .

Now you need to configure Nginx for Magento 2. Go back to Webmin and choose Servers. Then click Nginx Webserver and finally Edit Configuration Files. From the drop down choose your server from the list, which should be the last item in the list. Domain.com.conf

Replace the configuration with this one. Make sure you replace domain with your domain name:

upstream fastcgi_backend {    
# socket    
# server unix:/var/run/php5-fpm.sock;   
server   unix:/var/run/php/php7.0-fpm.sock;    
# use tcp connection    
#  server  127.0.0.1:9000;
}

server {    
listen 80;    
server_name www.domain.com;    
return 301 https://www.domain.com$request_uri;    
}
server {    
listen 80 reuseport;    
server_name domain.com;
 listen 45.76.228.48:443 default ssl; 
ssl_certificate /home/domain/ssl.combined; 
ssl_certificate_key /home/domain/ssl.key;
set $MAGE_ROOT  /home/domain/public_html;
set $MAGE_MODE developer;
#set $MAGE_MODE default;
#set $MAGE_MODE production;
include /home/domain/public_html/nginx.conf.sample;    
fastcgi_read_timeout 3000;
}

Click Save and it will test the script. If the test goes fine click Return to virtual hosts list and click Apply Nginx Configuration.

Now go to your domain name and run the Magento 2 install.

FINAL NOTES

I suggest you setup SSH keys and lock down your server to prevent people hacking your site. You can shut off root access at this point and just sudo into root if you need to manage the server.

It is also wise to shut down Webmin when you are using it to manage the server. From the command line, type:

service webmin stop

The post Magento 2 with Debian 9 and Nginx appeared first on Magento Wizard | Lakewood Colorado Magento Web Design, E-Commerce, Online Marketing, SEO.