Author: kilwag

Bands FC reimagines soccer team logos as band logos, or vice versa. Some of them are really, really good. Some aren’t. Here’s Tool and the Portland Timbers. 

UPDATED: Another MP tweet in the full post.

Merritt Paulson may have given us a spoiler on what the 2019 kits will look like when he replied to a fan-designed kit in a tweet. “…we jumped through hoops to design the 2019 kit.”  Confused?  Hoops in the context of soccer jerseys refer to horizontal bars or stripes.  T2 kits from 2016-17 had hoops, as did 2002-2003 Timbers. It’s getting impossible to find old Timbers jerseys online, as there is no definitive record, and with Timbers and Timbers 2 both existing in USL at different times, well Google isn’t very helpful.

I’m picturing Merritt hunched over his phone, trying to decide whether to submit his reply, agonizing over ruining the surprise. That’s what I’m picturing, but it’s a safe bet to assume he didn’t do that though. Of course, it could be just a common phrase with no hidden inference. 

Yes, it’s true. There have essentially been no new updates since the recovery from the server crash, with the exception of the 2018 standings graph. Sooooo much has happened. I’m still trying to figure out the future of this site, and involved in a lot of other things like for example this upcoming Subbuteo table soccer tournament.

Just 3 days before the 2018 season and PTFZine is online again! So much has happened that I wasn’t able to post about since the site went down in October… but it’s finally online again!

TLDR: Web host had massive hard drive failure. Everything was lost. Now, several months later, they managed to recover the files, and I’ve managed to reinstate them. There might be some weirdness here and there that I haven’t discovered yet, and if there is, I will be fixing that in the coming week.

The full Story: My web host had a catastrophic RAID failure, and had no off-site backups. Apparently, that’s my job. They must have have done something wrong however, because after they tried to fleece their customers for a forensic hard drive recovery service and didn’t get enough takers, the eventually decided to pay for it themselves and only charge their users $20 a site to retrieve what they could. Fortunately, everything appears to have been recovered for this domain.

There are some minor additions to the Season Tracker seen at the top of every page.  Points Per Game (PPG) have been added to individual games (visible on rollover) as well as the current PPG in the legend under the individual match boxes.  On the Standings chart, PPG has been added as well as the individual match result and the opposing team. As a bonus, the data is pulled from the match results the Season Tracker uses. This means the chart is updated the fly as I update a match, and I don’t have to monkey with the embedded javascript in the post. Can you say Data Integrity? Tim will appreciate this.

I made a WordPress plugin to help visualize match results and double as schedule that would allow me to easily see who and when we were playing. If you operate a WordPress-based site you can use it to track the Portland Timbers, or some other, inferior MLS team. Rolling over one of those squares will give you the match date, and if the match is finished, goals, and other results. A running tabulation of the season is kept at the bottom, and you can sort by home or away, conference, and games played, and more.

You can see it under the banner at the top of every page. Those are generated by a function called in the theme template. You can also generate it inline with shortcode in a post. [See below]

2016 Timbers Schedule and Results

The project started last season. Once I figured the basics of how I wanted it to work, I coded up some CSS, Javascript, and PHP to make it work. It’s pretty easy in a one use situation, where you’ve only got one season and you’re only interested in one specific team. Updating results was a matter of editing a text file with serialized information. It was simple, but not simple enough. I wanted to be able to do the whole thing in the backend of WordPress, make it reusable, and not limit it to one team. I imagined a scenario where someone might want to show two different teams on the same page, or the same team in multiple seasons. Simple enough… sort of. It needed to be flexible enough to easily accommodate expansion teams and teams that switch from one conference to another during different seasons. Figuring out the approach to take was the hardest part. It would have been easiest to create my own tables in the MySQL database, but I considered it a challenge rearrange my thinking and make it work with custom post types, taxonomy, and custom meta boxes.

Installing and activating the plugin automatically creates the teams. It’s up to you to create the matches and sign home and away teams to each match. You can do it manually, or you can upload it in a CSV spreadsheet and do it all at once. I used the MLS calendar subscriptions viewed in the Google Calendar, agenda tab. A copy and paste into a text document and some search and replacing made it a pretty quick affair, and one where I didn’t have to worry about typos on match dates. Now that I’ve got it figured out, I might even consider converting some other teams schedules and making them available for others.

Implementing it in a site can be done with a function call in a template, or shortcode in a WordPress post or widget. Of course, if you fail to specify a team, it defaults to the mighty Portland Timbers. After a game is done, you edit the match with the goals and optional information like Conference and Supporters Shield standings. If you’re logged in as an admin you’ll be able to access edit links directly from the match info rollovers.

On the roadmap, I want to submit it to the WordPress Plugin Repository. There are some minor options I’d like to add, and some tweaks to the UI. Once that’s tackled, I want to work on making the CSS more elegant, but I figure that can wait until the mechanics are more or less complete. Also, the interface is based on rollovers, so I need to make it work on touch devices too, because apparently these new-fangled iPhones and iPads are going to stick around…

I’d love to hear feedback. Until it makes it to the official repository, you can download the code here. No, I’m not on Github.