Wes recommends to chat to someone about the course on a regular basis, to keep you motivated and to give you a slap as soon as you start slacking. So, I’ve decided to log my progress in a public repository on GitHub, so you all can follow along (and improve it as we go, perhaps). Here we go!
Sigh. Where do I start on this? Everyone who owns a website these days and has some sort of analytics tool active has seen the lifehacĸer and ɢoogle domain spam (note the weird characters). For the last couple months, the amount of spam like this has been growing slowly but steady. Annoying, yes, but also very easy to filter out in your reports.
Today, however, I’ve stumbled upon something new. Google Analytics showed me a bunch of extra traffic over the past couple days. A quick look at where the traffic was coming from, showed that it was coming from Reddit. Okay, that’s interesting, as I hadn’t been active on Reddit for a while. Diving deeper in the referrals report, lead me to this Reddit thread (don’t click the link in the thread, but you can view the thread without risk).
The Reddit thread links to one of the well known domain spam websites. This same thread is used as referral for over 1000 unique visitors to my humble website on a single day. The thread does not link to my website at all, so the referral is fake. But it did offer me the link to the spam website again, while I thought that I was just looking at a Reddit thread giving me a ton of new traffic… Continue reading Analytics spammers now use legit websites as referrals
I remember the feeling of pride, excitement and determination to make something great, in the months prior to the launch of Listings. The project was born out of frustrations with WP Job Manager being abandoned after the Automattic acquisition and the idea that we could do something better. We made a plan to setup a more generic listings experience, powered by niche specific implementations. Listings was born.
After a couple weeks of digging through the WP Job Manager code (which we forked Listings out of) we got a point where the plugin was ready to be viewed by the public. The first public beta version was available and we got a lot of press coverage, tweets, likes and everyone seemed to like the idea.
All this attention made us believe in the project even more. Listings was born out of a need, there is a massive target audience for each specific niche we wanted to target and people seemed to like our setup. We got Listings from initial idea to actually released project and were able to tick all boxes of our plan so far. I think I’ve never been more enthusiastic about a project, than I was about Listings. That’s why it stings so much that I have to step down as project lead. Continue reading Leaving the Listings project
In April of this year, Scott Basgaard and I started an adventure together. I became part of The Look and Feel as technical lead. We had all the right projects, exciting clients to work with and a lot of potential for our own products to launch.
Later on, Rob, Gareth and Jack joined the team and we had a lot of fun, while working on exciting stuff. I can think of nothing wrong about our current team, except for the fact that our plans for the future have started to differ. What is best for the team in the long run, is not best for my personal life and future career.
It’s been a while since I last posted something about the whole dependencies horror that I’m still trying to deal with in the WordPress ecosystem. Justin Sternberg’s post on the future of the CMB2 library got the discussion going again and soon after, we were at the dependencies discussion again.
Today I published the pre launch page for my side project Lapisense. In case you missed it, it’s a hosted activation and updates API for WordPress based products. If you don’t like running a plugin that does this for you, Lapisense might be a nice fit for your products.
There is a lot of confusion in the WordPress ecosystem when it comes to the issues around bundling dependencies. Peter Suhm has published a detailed post about this exact issue: A Warning About Using Composer With WordPress, where I have left the following (partial) comment:
So imagine both of us loading library x in our plugins, both requiring a version that’s incompatible with each other. No matter how well tested your plugin is, if I get a chance to load my autoloader before yours, I can load a version of the library that is not compatible with yours and your plugin will break (at least, the end user will see it like that and the horror of finding the culprit begins)…
This obviously is not a Composer issue, but related to the way WordPress loads its plugins. It’s also not a well known issue, since Composer isn’t used a lot in the WordPress ecosystem (yet!), especially not in distributed plugins. But as Composer becomes more used, more collisions like this will happen. Without a proper dependency management system in place, this is really hard to solve.
My WordPress Composer Installer proof of concept is as close to solving this issue as I’ve ever been. If there is anyone more experienced with the plugins installer in WordPress and maybe knows their way around Composer as well, I could use some help. 🙂
I’ve been working on a proof of concept for solving dependency management in WordPress plugins for a while now. It was in a private repository on GitHub, where I would invite some people in to work out the most obvious issues, while keeping it a bit on the down-low (this is a big change, potentially, after all).
Now it’s time though. The WordPress Composer Installer repository is now open to the public. Note that this is not more than a proof of concept, albeit it a working one. There are some hoops to jump through to get this working, but all these steps can be automated once I make this a fully featured plugin.
The number one remark I heard when I launched WPupdatePHP, is that users shouldn’t be bothered with this. In an ideal world, this is true, but in reality this isn’t going to stand for long. Allow me to explain why:
The core WordPress team can’t get every single hosting company to comply. I admire their intentions, but in reality this is not going to help everybody.
At the time of this writing, PHP 5.4 is actually already nearing its EOL date and we’re still figuring out how to make PHP 5.2 and 5.3 platforms go away…
The end user is one of our most important, but underestimated, assets in this battle. They have the strongest voice in this all.
WordPress has PHP 5.2 as the minimum required PHP version. For a while now, PHP 5.4 has been listed as the recommended version. That’s a big step in the right direction, but I feel we can do more to help push the requirements forward.
At Radish Concepts we work with a lot of different platforms, frameworks and even languages. Most of our PHP projects are based on the Laravel framework, but we also do a lot of WordPress projects. When writing code for Laravel based projects, we obviously use namespaces and such, something we can’t do in publicly available WordPress plugins (since namespaces require PHP 5.3).
What we’d really love to do is be able to use namespaces for example, in our WordPress plugins as well. In addition to that, PHP 5.2 and 5.3 are really, really old. Even though lots of the Linux distributions tend to backport security fixes, it’s never a reassuring thought to read that PHP 5.2 has been unsupported for over 4 years now. We need to move on, as a community. Continue reading Time to update your PHP version