Sign up to save your podcasts
Or
Share Episode 33 – WordSesh Special – Upgrade routines in plugins and WordPress 4.1
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
Episode 33 – WordSesh Special – Upgrade routines in plugins and WordPress 4.1
In episode 33 we discuss upgrade routines in plugins and what’s new in WordPress 4.1. This episode was recorded on December 19th as part of WordSesh, marking the first time we’ve done a video episode. If you’d like to watch and listen, head over to YouTube.
This episode was sponsored by WP Ninjas, the creators of Ninja Demo and the highly popular Ninja Forms plugin.
Show Notes:
WP Core Ticket: Bulk load Comment Meta upon access
Restrict Content Pro
WordPress 4.1
New template tags
Title tags
Complex queries
Review us on iTunes
Transcript
INTRO: Welcome to Apply Filters, the podcast all about WordPress development. Now here’s your hosts, Pippin Williamson and Brad Touesnard.
BRAD: Welcome to Episode 33 of Apply Filters. Today is a special WordSesh episode, and we’re going to be talking about upgrade routines and plugins and what’s new in WordPress 4.1. But first, Pippin, how about the sponsors?
PIPPIN: Once again, this episode is sponsored by the WP Ninjas. They are the developers behind Ninja Forms, as well as Ninja Demo and several other pretty cool little plugins. They’re some good friends of ours, and they’ve been very generous in helping us keep this thing going.
This is also the first time we’ve ever done a video episode, so this is a little different for us, but it should be fun. Why don’t we go ahead and get started? Brad, take us away. What have you been working on?
BRAD: Last Friday, we had a Core Contributor Day with Delicious Brains, Inc., my company. All the employees just spend the whole day working on Core, WordPress Core. It was just pretty fun just to kind of work on Core.
PIPPIN: That’s for the five for five, right?
BRAD: Yeah, well, that’s kind of what pushed me over the edge, for sure. I’d been thinking about it before Matt put up that thing, but that kind of pushed me over the edge.
PIPPIN: You guys spent the time working on Core. As a team, what did you guys work on for the day? Did you find anything interesting?
BRAD: Yeah, so one of the bugs I found was an interesting little bug. It was just a little performance bug, so the problem is with comments. When you list comments on the page, if there’s any metadata that you’re displaying, like comment metadata, it’ll do a select query for that comment meta for every comment. If there are 100 comments on the page, it’ll do a select query for each one of those. This is a bug that someone suggested be implemented four years ago.
PIPPIN: Oh, yeah. It looks like it came from … been around for a while.
BRAD: Yeah, it’s been around, so I kind of dug into it. It took a while to get my head around it. I probably, I don’t know, spent like over an hour trying to figure out what I needed to bring together, the best way to bring it together and make it happen. If you look — we’ll link up the bug in the show notes and the patch that I….
PIPPIN: I’m going to drop it into the chat too for anybody who wants it.
BRAD: Yeah, yeah, do that. It’s super small, and it’s really brief. It’s one screen.
PIPPIN: It’s funny. I was reading through that issue to … and as I was reading it, I was thinking this is a pretty large problem. I saw your patch, and it’s tiny. It’s so small; it’s awesome.
BRAD: I know. No one has reviewed it yet, so I hope it’s right.
PIPPIN: Yeah, we’ll see.
BRAD: But I’ve tested it, and it seems to work great. It cuts all those queries down to one query.
PIPPIN: That’s really cool.
BRAD: Instead of 100 queries, you get one query.
PIPPIN: That’s going to be a major improvement for anything that, if anybody is using plugins that add a lot of comment meta.
BRAD: Yeah.
PIPPIN: Or review plugins, for example. In Core, by default, there’s really very little metadata stored in comments.
BRAD: Right. Yeah, yeah, exactly.
PIPP
View all episodes
By Apply FiltersIn episode 33 we discuss upgrade routines in plugins and what’s new in WordPress 4.1. This episode was recorded on December 19th as part of WordSesh, marking the first time we’ve done a video episode. If you’d like to watch and listen, head over to YouTube.
This episode was sponsored by WP Ninjas, the creators of Ninja Demo and the highly popular Ninja Forms plugin.
Show Notes:
WP Core Ticket: Bulk load Comment Meta upon access
Restrict Content Pro
WordPress 4.1
New template tags
Title tags
Complex queries
Review us on iTunes
Transcript
INTRO: Welcome to Apply Filters, the podcast all about WordPress development. Now here’s your hosts, Pippin Williamson and Brad Touesnard.
BRAD: Welcome to Episode 33 of Apply Filters. Today is a special WordSesh episode, and we’re going to be talking about upgrade routines and plugins and what’s new in WordPress 4.1. But first, Pippin, how about the sponsors?
PIPPIN: Once again, this episode is sponsored by the WP Ninjas. They are the developers behind Ninja Forms, as well as Ninja Demo and several other pretty cool little plugins. They’re some good friends of ours, and they’ve been very generous in helping us keep this thing going.
This is also the first time we’ve ever done a video episode, so this is a little different for us, but it should be fun. Why don’t we go ahead and get started? Brad, take us away. What have you been working on?
BRAD: Last Friday, we had a Core Contributor Day with Delicious Brains, Inc., my company. All the employees just spend the whole day working on Core, WordPress Core. It was just pretty fun just to kind of work on Core.
PIPPIN: That’s for the five for five, right?
BRAD: Yeah, well, that’s kind of what pushed me over the edge, for sure. I’d been thinking about it before Matt put up that thing, but that kind of pushed me over the edge.
PIPPIN: You guys spent the time working on Core. As a team, what did you guys work on for the day? Did you find anything interesting?
BRAD: Yeah, so one of the bugs I found was an interesting little bug. It was just a little performance bug, so the problem is with comments. When you list comments on the page, if there’s any metadata that you’re displaying, like comment metadata, it’ll do a select query for that comment meta for every comment. If there are 100 comments on the page, it’ll do a select query for each one of those. This is a bug that someone suggested be implemented four years ago.
PIPPIN: Oh, yeah. It looks like it came from … been around for a while.
BRAD: Yeah, it’s been around, so I kind of dug into it. It took a while to get my head around it. I probably, I don’t know, spent like over an hour trying to figure out what I needed to bring together, the best way to bring it together and make it happen. If you look — we’ll link up the bug in the show notes and the patch that I….
PIPPIN: I’m going to drop it into the chat too for anybody who wants it.
BRAD: Yeah, yeah, do that. It’s super small, and it’s really brief. It’s one screen.
PIPPIN: It’s funny. I was reading through that issue to … and as I was reading it, I was thinking this is a pretty large problem. I saw your patch, and it’s tiny. It’s so small; it’s awesome.
BRAD: I know. No one has reviewed it yet, so I hope it’s right.
PIPPIN: Yeah, we’ll see.
BRAD: But I’ve tested it, and it seems to work great. It cuts all those queries down to one query.
PIPPIN: That’s really cool.
BRAD: Instead of 100 queries, you get one query.
PIPPIN: That’s going to be a major improvement for anything that, if anybody is using plugins that add a lot of comment meta.
BRAD: Yeah.
PIPPIN: Or review plugins, for example. In Core, by default, there’s really very little metadata stored in comments.
BRAD: Right. Yeah, yeah, exactly.
PIPP