Author: Tom (Page 375 of 427)

Programmatically Resize Images in WordPress

October 4, 2012 / Tom / 0 Comments

If you're experienced with programmatically uploading files, you may wish to skip down to the code.

I’m finishing up an application that’s built on WordPress that has required that I programmatically resize images. When it comes to building themes or plugins, it’s relatively easy to specify add_image_size and then let the user interface and core application do it’s thing.

But in my case, the end user will have no idea that the actual application is built on WordPress and the image resizing function needed to be a little more tailored for specific templates (or views)

So rather than use the typical WordPress facilities for uploading and resizing images, here’s how to programmatically resize images in WordPress.

Write For WPTuts+: The Envato WordPress Site!

October 4, 2012 / Tom / 0 Comments

WANTED: WordPress Professionals With a Passion for Education. Enquire Within. http://t.co/UyG6C7dc

— Wptuts+ (@wptuts) October 3, 2012

Yesterday, @EnvatoWP invited others to apply to begin writing for WPTuts+, the Envato WordPress site.

Version Numbers: What’s The Point?

October 3, 2012 / Tom / 0 Comments

One of the things that my team and I have consistently discussed when working on Standard is how to actually maintain or version numbers. It doesn’t stop there, of course – even in my own work, I give considerable thought (how lame does that sound?) as to how I should track the version numbers of my projects.

Thought I tend to follow the schema of “Major Version, Minor Version, Hot Fix” (i.e., 3.0.2), I’m unsatisfied. And to put it bluntly, I’m discontent with the whole thing version numbering issue: They’re inconsistent, they aren’t user-friendly, and I’m not even sure what we should do about it.

Five Suggestions For Writing Better JavaScript in WordPress

October 2, 2012 / Tom / 0 Comments

This is the final post in the series JavaScript in WordPress. Be sure to read the first article, too!

In the first post in this series, I briefly mentioned that there is a problem with writing JavaScript in WordPress. In boils down to the fact that people are writing JavaScript who don’t truly know jQuery (let alone JavaScript), and that there are lack of standards to follow.

And though I’m not interested in defining the coding standards for JavaScript in WordPress – at least not here – I am interested in sharing four things that I’ve found to be successful in writing maintainable jQuery in WordPress for both individual and team-based projects.

Note, of course, that these are geared towards jQuery. After all, that is WordPress’ JavaScript library of choice.

The Problem of No Coding Standards For JavaScript in WordPress

October 2, 2012 / Tom / 0 Comments

This is the first post in the series JavaScript in WordPress. Be sure to read the final article, too!

One of the challenges of building projects on top of WordPress is that there are well-defined coding standards specifically for PHP-based components. There are even some guidelines for HTML, and the CSS guide is under construction, but there appears to be very little in way of coding standards for JavaScript in WordPress.

I’m certainly not going to be defining those standards here – that belongs in the Core Contributor Handbook, right? – but I am doing to be sharing my thoughts on JavaScript in WordPress and some of the things that I do in order to make sure that my projects and that my team’s projects are maintainable over time.