Author: Tom (Page 139 of 428)

WordPress JSON Encoding For Ajax

November 1, 2016 / Tom / 0 Comments

If you’ve worked with Ajax in any capacity, then you’ve likely tried to send response data using various formats. Obviously, the original format of the response data is XML but JSON is a second, [and arguably] more popular format.

When working with WordPress’ Ajax API, arguably, the most important things to remember are:

Make sure the function is using the proper hook (should it be available for the public, for users who are logged into their account, or both?),
Terminate the function using wp_die unless you want an incorrect or malformed response sent to the client.

In addition to that, if you’re sending your response data to the client in the form of JSON then you have several options on how to return the data:

Structure the JSON data yourself (which I think would be an overly complicated feat 🙂),
Use PHP’s json_encode function,
Or use WordPress’ wp_json_encode function.

You can see there this is going, right? So I’ll make it quick.

Desktop Applications via the WordPress REST API?

October 31, 2016 / Tom / 0 Comments

There are a lot of reasons that people are excited to have the WordPress REST API merged into core.

The WordPress REST API Plugin

I think some are excited because they won’t need to include the plugin dependency anymore; others, honestly speaking, I think are happy to see it merged for the sake of it. Whatever the case, having the entire infrastructure is core is neat, and I’m excited, but almost none of the client work I’m doing at the moment warrant it.

I believe that will change, though, as people learn what we can do with it. But until that time comes, one of the things I like to do is try to think broadly about what could the REST API offer that isn’t directly related to blogging.

And this leads me to a much broader question.

Learn “WordPress JavaScript” (And What That Means)

October 28, 2016 / Tom

Now and then, I’ll stumble across a blog post, question, or comment that talks about WordPress JavaScript as if it’s a different type of or variant of JavaScript that exists solely within the WordPress application.

For those who have been working in web development for a long time, this seems like a silly statement, but if you’re brand new to web development (regardless of your age), then this is something that might be a bit confusing.

After all, it’s not like the JavaScript standard is cut and dry right now, right? But I digress.

Furthermore, WordPress includes jQuery, jQuery UI, Backbone, and so on. So when someone wants to work with JavaScript within the context of WordPress, what are they actually talking about?

And the answer is, unfortunately, “it depends.” But it does: It depends on the type of work you’re doing and where you’re focusing your efforts.

But this brings us back to the original problem: How do you learn “WordPress JavaScript” if you’ve never even touched JavaScript?

Working with Associative Array Values in WordPress

October 27, 2016 / Tom / 0 Comments

Spend enough time working in WordPress, and you find that a lot of data is often held in arrays (and multidimensional arrays, at that). I’m not arguing whether or not this is a bad thing or a good thing; it’s more of an intermediary step between grabbing something from the database and then rendering it on the page.

As you venture into the world of WordPress development, though, and you aren’t necessarily sure how you want to manipulate some of that data before rendering it, saving it, or working with it, you may ask yourself the following question:

How do I read the associative array values in WordPress?

And if you have experience in PHP, this isn’t something that’s terribly difficult. But if you’re working with an existing structure or trying to extend or manipulate something that already exists,

Look at all the serialized options.

But if you’re still learning the ropes and you start trekking down the PHP manual, you’re likely to find something like array_values or array_intersect_key or something like that only to find out that you’re more confused than when you’ve started.

So what are you to do?

Should We Use PSRs or WordPress Coding Standards?

October 26, 2016 / Tom / 0 Comments

It probably gets a bit tiresome to talk about coding standards, practices, and things like that when you’re trying to focus on simply getting things done.

And though I get it, I also think that having standards and practices – at least within the context of your team – can go a long way regarding being productive, writing maintainable code, and having things in place to help with maintenance over time.

PSRs or WordPress Coding Standards: The PSRs

All of that’s beside the point, though. In the last few years, I’ve found that WordPress – at least those who work on the server-side – usually come in two flavors:

Those who follow the WordPress Coding Standards,
Those who follow the PSRs.

I think there are good reasons for choosing either one. Naturally, I’d say that because I’ve almost always used the WordPress Coding Standards (I have very few exceptions), but I understand the choice to use the alternative as well.

PSRs or WordPress Coding Standards: The WordPress Coding Standards

And it’s something I’m beginning to consider doing, too. But I’m curious, for anyone who’s used both or who has an opinion (strong or otherwise) on which one and why to share.