Tag: Laravel Valet | Page 2

Though I’m not a fan of strictly using var_dump or echo statements as a way to debug code, that doesn’t mean there aren’t times in which they are useful (otherwise, they wouldn’t be part of the language, right?).

But what if you’re using Laravel Valet (which is easy enough to setup for WordPress) and you’re trying to display some multidimensional array and rather than getting some nicely formatted output, you end up getting one long line of text in Times New Roman? Odds are this is because you don’t have Xdebug.

Using Xdebug with Valet and WordPress: Valet

It’s easy enough to do, but it’s predicated on a few different things. Plus, once you get Xdebug installed, then you’re able to use a debugger with your code, as well. That’s not the point of this post, though.

One of the latest options available for local development is using Laravel Valet for WordPress. This is now one of the options available for the already set of options we already have:

XAMPP, MAMP, WAMP, etc.,
VVV,
WP-Lib Box
And more.

When it comes to having choices like this, it can make it difficult for a beginner to decide where to start. And as important as I think it is to explain the benefits of each of the above options, that post is not this post.

Instead, I want to share a short tutorial I wrote about using Laravel Valet for WordPress. Personally, I think Valet is a great solution for beginners, but it assumes a bit of familiarity with the command-line that might be off-putting to new users.

Once you setup the software, it’s hard to argue against using it. So with that said, here’s how you can get started.

Tag: Laravel Valet (Page 2 of 2)

Using Xdebug with Valet and WordPress

Using Laravel Valet for WordPress Development