Author: Tom (Page 151 of 428)

How To Prevent Direct Access To Your Plugin

August 9, 2016 / Tom / 0 Comments

As developers, one of the most important things we can do is prevent direct access to your plugin. By this, I mean if someone gets clever and tries to access to one of the files located in any given plugin’s directory, they should not be able to execute any of the code in the script.

A simple plugin’s directory from which the below source is pulled.

And I know: This seems like something that’s easy (it is), but even in a recent project, I’m reminded how it’s not something that even some of the most useful plugins do.

I can only chalk this up to lack of awareness or perhaps lack of education. If you’re not setting your work up to prevent direct plugin access to your plugin, you’re leaving a significant security gap in place, and it’s something that can be easily corrected.

A Primer on Options and The WordPress Object Cache

August 8, 2016 / Tom / 0 Comments

When working on a site, blog, or project on WordPress, it’s not at all uncommon to hear users (developers, designers, bloggers, and so on) talk about caching.

Caching can be a tricky subject to tackle, though. I think that most people have an understanding that caching, in general, can be used to speed up a site. But regarding what it does, how it works, and any other details beyond that are hit-or-miss, pun intended, depending on your level of experience.

And one area in which I see – and have personally experienced – is the understanding of the WordPress Object Cache. Feel free to click the link, though it’s far more advanced than what I plan to cover in this article.

That is, WordPress provides some basic functionality for loading the options in the wp_options database table, but how WordPress caches data, how WordPress retrieves non-cached data, and how it works is often glossed over or assumed to be a sort of magic.

How it feels to work with the magic of WordPress (and not understanding what’s happening).

So I thought it might be worth sharing a few notes about the WordPress Object Cache and how it works with objects if for no other reason that to provide a quick reference for what it is, how it works, and how we, as developers, can leverage it to our advantage.

What Are WordPress Plugins, Anyway?

August 5, 2016 / Tom

For those who work with WordPress on a daily basis, the ideas of WordPress themes, WordPress plugins, and other WordPress-related topics become second nature.

As is the case with anything any of us do on a regular basis.

Anyway, when there are others who are interested in getting started with WordPress either as content managers, bloggers, or developers, there’s a lot to learn. And sometimes, when we talk about WordPress plugins in blog posts, WordCamp presentations, and podcasts, we assume that the audience already has some understanding of the words we’re using.

But that’s not always the case. Some time ago, I started a series for Envato on Understanding WordPress Themes and Plugins.

Recently, the second portion of the series ran in which I talk about WordPress plugins specifically targeting those who are looking to have a greater understanding of what they are, how they work, and how they fit into the overall WordPress economy.

How To Concatenate JavaScript Files with CodeKit

August 4, 2016 / Tom / 0 Comments

Of all the various build tools that are available right now (such as Gulp, Grunt, and others), I still find myself using CodeKit. I’ve been a fan of it for a long time, and it still fits well into my workflow.

Concatenate JavaScript Files with CodeKit

It’s not that I’m making a case for you to use it, but if you are using it, then there are some that it offers that aren’t immediately evident. Things that other build tools tend to make a bit easier to achieve.

For example, when I’m working on a project for WordPress that will focus on a single area of the application, such as the administration area, then I prefer to take all of the various JavaScript files I’m writing and then concatenate them into a single, minified file.

CodeKit makes this possible in two ways: Through the GUI and directives in an individual file.

What to Expect With Start Here For WordPress

August 3, 2016 / Tom

Earlier this summer, I talked about Start Here for WordPress which is a closed and limited membership site for those who are interested in becoming WordPress developers but aren’t sure where to, you know, start.

Start Here for the aspiring WordPress developer.

The site is going to open officially on Friday for registration, and though the mailing list has been active for a few months, I’ll be sending out two more emails before registration.

To that end, I thought it would be worth sharing some information about those who have been helpful in sponsoring the mailing list as well as the site, and highlighting what to expect if you opt to sign up for membership.