First, find your Local site site’s directory. Each site that you want to debug will need its configuration altered to work with debugging. Local ships with the xdebug extension available but not enabled.
Before we continue, let’s get Local configured for xdebug. vimrc looks like this: """ Vim-PlugĪfter adding Vdebug, we’ll need to add some configuration. Installation instructions are included on the plugin’s page. Setup vimįor vim or neovim, henceforth referred to simply as “vim” (with distinctions for neovim if necessary), you will need the Vdebug plugin. You can find a guide for getting started on Flywheel’s blog. If you haven’t set up a site before with Local, it is pretty straightforward.
#Local by flywheel wordpress how to#
If you aren’t familiar with how to use vi-like editors, but want to learn, I would recommend running vimtutor in your command line and learning how to move and work in vim before continuing with this post. Prerequisitesįirstly, this tutorial is intended for users of vim or neovim. Today, we’re going to go over how to get both of these working together within vim to provide a powerful interface that allows for some successful debugging of WordPress. xdebug is a PHP extension that allows for real-time debugging of PHP code. One of its lesser-known features is the inclusion of xdebug support. Local by Flywheel is a popular tool for getting quick and reliable WordPress installations running on your computer.
0 kommentar(er)
