As demonstrated by the latest Twitter storm around PyCon, the “gender in tech” debate is being derailed by the misguided idea that people have a right not to be offended.
A couple of weeks ago, we quietly relaunched the Experience website.
The most obvious difference is that the new site now meets the predefined buzzword quota for all websites developed since 2012 (responsive! icon fonts!), but actually the biggest change is behind the scenes: Experience HQ is no longer built on ExpressionEngine.
So, the ExpressionEngine community is once again abuzz thanks to some unexpected EllisLab behaviour. In fairness it’s always abuzz, I’ve just been avoiding such things because I’ve long since given up on both the product and the company (mostly the latter).
That said, the latest piece of news regarding EllisLab ending its long-running affiliate program is so strange that it warrants more than a snarky Tweet. It warrants a snarky blog post. You’re welcome.
A couple of weeks ago, I wrote a quick blog post to announce that Testee 2.2 now lets you run your tests via an ACTion ID.
Whilst writing said blog post, I discovered that the world is sadly lacking in a succinct overview of ExpressionEngine ACTion IDs. Read on for my attempt to plug this hole in the ExpressionEngine documentation dam.
It’s been 12 month since the previous Updates and Oddments post. I haven’t been completely idle during this time, but my rather erratic blogging schedule means that most of my side projects are released without fanfare.
Read on for a collection of ExpressionEngine-related oddments that quietly slipped out the back door over the past year.
Yesterday I released Testee 2.2, which contains a significant new feature: automated testing.
You can now run an add-on’s test suite by loading an “ACTion” URL; Testee does your bidding, and returns the results as JSON.
Last week I published a post about a bug in the ExpressionEngine Template parser, which causes problems with nested
Said post includes a couple of quick fixes: one suitable for use by general ExpressionEngine developers; the other intended for add-on developers.
The “general” fix remains unchanged, so if you’re not an add-on developer your work here is done.
If you are an add-on developer, continue reading for a much better solution than the one I originally presented.
This week in EEceania has been a joyous celebration of increased productivity and doubleplusgood social harmony.
If you consider it reasonable to suggest the ExpressionEngine community should be responsible for fixing the myriad bugs in EE2, this post is for you.