Tag: WordPress (Page 55 of 220)

Articles, tips, and resources for WordPress-based development.

WordPress Admin Notice Plugins (And Why Options Are Good)

August 3, 2017 / Tom / 0 Comments

A couple of days ago, someone shot me a link to Dobby (no the house-elf, but sorta – and it would’ve been just a bit cooler, right? :). In short, it’s one of the various WordPress admin notice plugins that I think is worth checking out.

WordPress Admin Notices

It’s written by Thorsten Frommen (who inspired this post, to be honest) and a developer for whom I have a lot of respect.

The plugin’s description is as follows:

Dobby, the friendly Admin Elf, takes care of all your (unwanted) admin notices.

The emphasis added is mine, but it sounds a little familiar, doesn’t it? The drama.

Or not. 🙂

Debugging WordPress with Valet Error Logs

August 1, 2017 / Tom

I’ve written a number of posts about Valet (here and here) and why I think it’s a solid option when it comes to working as a local web server for WordPress-based development.

Valet Error Logs

It’s easy to setup, it’s got built-in support for WordPress, it uses Nginx (which is often faster than Apache is my experience), and it provides a great way to allow others to tunnel into your machine for testing if that’s something you’re into doing.

But if you’re someone who spends time debugging both through Xdebug and through reading through error logs, then you may be interested in reviewing the Valet error logs (if you can find where they are kept) when debugging your projects.

PSR Logging Interface (And Why Logging Matters)

July 27, 2017 / Tom / 0 Comments

Two features of PHP that I believe are often overused when it comes to “debugging” are using echo and var_dump. I’ve talked about this in a few different articles around debugging (like in here and here).

And as much as I am a fan of using a debugger, I think it’s also important to implement a type of logging system so that you or your client can go back and review the activity that’s been happening within the system as they or their users have been, you know, using it.

There are two aspects to doing this, though, especially if you’re looking to following the PSR logging interface and they are:

the rules for the actual logging interface,
a project that properly implements said logging interface.

So why not tackle both in this post?

What Are Programming Side Effects, Anyway?

July 26, 2017 / Tom / 0 Comments

Whenever we talk about certain programming concepts, I think it’s important to take a step back out of whatever specifics we’re discussing and look at things in the context of the bigger picture.

Some modules introduce side effects; some don’t. It’s okay.

For example, yesterday I briefly touched on the idea of programming side effects, but I did so when talking about using PSRs. And for those who are simply interested in aspects of programming in a more general sense, it’s important to understand them, too.

Remember, the idea of side effects as stated in PSR-1 is:

A file SHOULD declare new symbols (classes, functions, constants, etc.) and cause no other side effects, or it SHOULD execute logic with side effects, but SHOULD NOT do both.

In this post, I’m not so interested in discussing logic with side effects (because there are times where side effects will happen). Instead, I’m more concerned with understanding programming side effects (what they are, what to avoid, and so on).

After all, talking about side effects in one context may mean one thing whereas, in programming, it may mean another.

Basic Coding Standards via PSR-1

July 25, 2017 / Tom / 0 Comments

Yesterday, I talked briefly about a rationale for using PSRs versus the WordPress Coding Standards and the when and why of both. But that doesn’t mean it’s not without its points of confusion especially if you’re just starting with them, right?

By that, I mean: Say you’ve been working with the WordPress Coding Standards for years (because I can relate) and now there’s this whole new set of rules and guidelines to follow. But it’s not like a simple matter of changing some white space and renaming files.

There are other points to follow, and each is outlined in a number, quite literally (PSR-1, PSR-2, and so on), of how something should work.

So when it comes to just the basic coding standards as outlined in PSR-1, what are some problematic areas that we may encounter as WordPress developers?

WordPress Admin Notice Plugins (And Why Options Are Good)

Debugging WordPress with Valet Error Logs

PSR Logging Interface (And Why Logging Matters)

What Are Programming Side Effects, Anyway?

Basic Coding Standards via PSR-1

Current Projects