Page 173 of 427

Deregistering WordPress Stylesheets

March 7, 2016 / Tom

Deregistering WordPress stylesheets is one of those things that we don’t always have to consider.

If you’re starting a project from scratch, then it’s usually safe to say that you’re starting a project at ground zero and have control over most of the assets that are to be enqueued in the project.

On the other hand, if you’re coming into a project at a later date or you’re working on a plugin that has to work in conjunction with another plugin that might use a shared stylesheet then you may need to deregister an existing asset to make sure everything works well together.

Digest For February 28, 2016

March 5, 2016 / Tom

I typically don’t post on Saturdays, and I usually let those who have signed up to receive emails via Postmatic get their summary via email once a week.

Time

But not everyone reads blogs the same way, and not everyone subscribes via email, so I thought I’d try something new. That is, this is an experiment (and I invite your critique at the end of the post).

With that said, here is a summary of the posts from this week.

Using PHP CodeSniffer with Atom

March 4, 2016 / Tom / 0 Comments

Using PHP CodeSniffer is one of those tools that is part of my workflow that I find utterly invaluable. I haven’t always used it, though.

Don’t get me wrong: If you’ve read this blog for any length of time, you know I’m big on Coding Standards. But when it came to the PHP CodeSniffer, there was an extended period I had gone before I installed it.

Why, though?

Simply put, it was because I didn’t know it existed, at least not for WordPress. When I discovered there was a ruleset for WordPress (and WordPress VIP), it became something that I believe should be a necessary tool in every WordPress developer’s toolbox.

Depending on your IDE, you may or may not be able to install a plugin or an extension that will automatically monitor your code while you’re writing.

I made the change to Atom some time ago, which I’ll share more about momentarily, and it has excellent support for incorporating PHP CodeSniffer into your workflow.

Praise in Public, Reprimand in Private

March 3, 2016 / Tom / 0 Comments

“Praise in public, reprimand in private” is a phrase that I heard years ago (and I can’t remember who I actually heard say it first), but it was one of those things that stuck with me.

When you hear phrases like that, I think we often consider things like parenting, leadership, managing a team, or something similar. But do you ever think about it in terms of blogging, tweeting, or what we share online?

For anyone who works online the majority of the day and is engaged in some form of social media, I think we’re used to seeing people both praise and critique others be it via tweets, blog comments, and so on.

And sure, there’s something to be said for “calling people out” for whatever reason, but I think there’s something to be said for also handling some of that stuff privately.

Sharing GPL Code and Its Ethics

March 2, 2016 / Tom / 0 Comments

“Sharing GPL Code” sounds like such a loaded title because the topic is forever hot. But hang with me because the purpose of this post has nothing to do with actually arguing for or against the GPL or code around it.

I know the simple answer is that all GPL code, by very nature of its license, it’s available for sharing, but there’s another aspect that plays into this I want to discuss.

Sharing GPL Code can be more about collaborating on code, right?

And that’s this:

What is the ethics of sharing the code for a project that you’ve built for someone else even if it maintains the GPL?

For the most part, I think it’s fine. But when you’re running a business and you’re building solutions for clients, there’s a little more to it.

At least, that’s my experience.

Tom McFarlin

Deregistering WordPress Stylesheets

Digest For February 28, 2016

Using PHP CodeSniffer with Atom

Praise in Public, Reprimand in Private

Sharing GPL Code and Its Ethics