For as much as I talk about writing code that conforms to the WordPress Coding Standards and for using tools such as PHP CodeSniffer, there are times where I’ve found that you need to silence the errors for the sake of something you’re trying to do.

Case in point:

WordPress uses global variables to maintain certain data structures. As per the coding standards, you should not change the values of global variables.

As a rule of thumb, this is true. But what about in the case where you need to make a modification to the admin menu (which uses a global variable)?

Continue reading

Please see this comment for updated information about this filter.

If you have a project for a client or perhaps just for yourself, you may find that you need to upload a file in the WordPress back-end that is not supported by the core application.

Depending on the type of file that you want to introduce, you may need to add support for additional MIME types. Luckily, this is easy enough to do.

No, not that type of mime.

But before looking at the code for how to do it, I think it’s important to understand exactly what we’re adding (otherwise, we run the risk of copying and pasting code and not knowing what it is or what it does other than it works).

Continue reading

GPL attribution is one of those tangential topics to a lot of the GPL discussion around WordPress (which I’m not interested in discussing here).

Instead, what I’m trying to answer is this:

How do you give proper GPL attribution when using someone else’s work in your work?

Case in point: Let’s say someone is building a theme and wants to bundle some code you’ve written (and it’s available on GitHub) and is trying to attribute it properly to you?

First, this is something that someone was kind enough to ask me when working on a project of his own. Second, I think it’s a great question as it’s something we should all know how to answer since much of our work is likely using other third-party, open source libraries.

Continue reading