Showing posts tagged as "expressionengine"

EE Reactor Team to the rescue!

I’m just going to put this out there. Does anyone else think that the EE Reactor team needs some kind of super-hero-esque logo? Something like the bat-signal perhaps?

Then, without committing to anything on the forums; any time they see something they are interested in addressing, they can just post up that image and we will all sleep a little better knowing that they are, protecting us all. Like vigilantes for code-justice?

If I were a designer, I would knock this out and send it to them. I know SOMEONE out there can do this. And they should.

ExpressionEngine 2 Bootstrap

Need a cron job in your ExpressionEngine 2 environment? Want to take advantage all that lovely CodeIgniter goodness? Not quite sure how to get access to the EE super object to make it happen?

As per usual, Rob Sanchez (@_rsan) has a solution for us.

Check out his ExpressionEngine Bootstrap and you’ll be good to go.

…But Instead I’m Writing About Dildos

I should be:

  • explaining the importance of understanding parse order in your templates – thanks to Low (@low)
  • listing 10 ways to make ExpressionEngine rock even harder than it already does – thanks to Matt Weinberg (@mrw)
  • assisting you in tuning your EE site to be as fast as possible – thanks to Jacob Russell (@jacobrussell)
  • giving you really cool insight into things the EE docs don’t tell you about Addon development – thanks to Mark Huot (@markhuot)
  • tearing the covers off of ExpressionEngine and discussing what we all saw – thanks to Rob Sanchez (@_rsan)
  • discussing the potential benefits of prototyping in EE – thanks to Ruthie Bendor (@unruthless)

But I’m not. I’m writing about dildos. And that is lame.

VS. EECI2010

Everything about EECI2011 felt bigger and better to me than EECI2010. There were more people here (twice as many in fact). I’m sure some of the attendees had things to complain about, but the general vibe in the room was incredibly positive. Everyone seemed excited about the future of EllisLab and ExpressionEngine. Although maybe that’s just it, maybe they are just confident that there is a future.

The Invisible Dog Art Center was a great venue for the event, and Brooklyn in general provided an almost infinite amount of spots for people to congregate and continue the discussions that were started during the actual conference.

Paul Burton & #dildogate

The event started off with some controversy: #dildogate. Paul Burton (@16toads) took the stage to give the first talk of the conference, entitled “Don’t Call Me A Freelancer”. Paul’s presentation included some R-Rated illustrations he had created and also a screen filled with dildos with hats photoshopped on them.

Take a look at Paul’s slides and decide for yourself if you find them offensive. [Edit: These are not the original slides. They have been replaced on Speakerdeck. I do not currently have access to a link to the original slides]

  • I was not personally offended by the content of the slides
  • Other people were clearly offended by the content of the slides

The real shame here, is that #dildogate did two things:

  1. It eclipsed in attention an otherwise brilliant presentation. I was genuinely wrapped the entire time Paul was speaking and I found him to be easily one of the best presenters.
  2. It affected the external perception of EECI2011. There were 300 of us in attendance, but there were also thousands of others following the #eeci2011 hashtag.

It is the latter that I am most concerned with. I am afraid that this years EECI may have seemed like a toxic environment filled with angry rioters carrying pitchforks. It wasn’t, and believe me, I know toxic environments (I was at EECI2010). The reason this is such a shame, is that what should have been coming across was the feeling of renewed hope that I sensed among the developer community. The sense of faith in what EllisLab is doing and the direction they are steering this ship.

It important to note that #dildogate was not the fault of either Whoooz! Webmedia or EllisLab. They didn’t screen the speaker’s presentations – which was the right thing to do. If you were pissed off by what Paul had to say – be pissed off at Paul. Send him an email, tweet at him, DM him and explain what you found inappropriate about his presentation.

The problem right now, is that people seem to be directing their anger at EECI, Whoooz, or EllisLab which isn’t fair to any of them, and more importantly it isn’t fair to the community.

Occupy EllisLab

I’ll say this again, because I think it is wildly important. EllisLab & Whoooz! better not screen future presentations for content.

EECI is vital to us. It is vital because of what it isn’t.

  • EECI is not a conference for us to pat ourselves on the back for how well we are doing.
  • EECI is not a conference for us to go hear things we already know.
  • EECI is not a place for us to go have smoke blown up our ass

EECI2010 in San Francisco was exactly what EECI should be about. It was my first EECI and I wasn’t sure what to expect. It felt more like Occupy EllisLab than it did like a bunch of people hugging and telling each other how great they are. Look at what it accomplished! Noone will argue that EllisLab isn’t in a better state in 2011 than it was in 2010. Everyone needs to remember that many of the changes since EECI2010, are thanks in part to the very toxic nature of that event.

The presenters in San Francisco didn’t hold back. Many of them included very direct comments for EllisLab expressing their disaproval with the state of EE. This is why it’s vital that we don’t restrain our presenters in any way. When things go wrong, we need to make sure that a platform still exists for EE users to be pissed off at EllisLab (or anyone else).

I realize that developers voicing their discontent with EllisLabs in 2010 and Paul Burton putting R-Rated pictures in his slides in 2011 are not the same thing. However, giving the conference creators any say in what the presenters can and cannot discuss is a slippery slope that I am not willing to go down.

If You’re Pissed Off…

Be pissed off. It’s ok. Just focus your anger in the right direction. If Paul offended you, be pissed off at Paul. Something tells me he will be ok with that.

It is our responsibility as those in attendance at EECI2011 to reflect the positivity that was very much present in Brooklyn this week.

Better Workflow - Thank You Electric Labs

One of the things that scared me to death about trying ExpressionEngine in the first place, was the lack of any real workflow tools. This was a gaping hole that I was somewhat shocked nobody was really freaking out about. Working with primarily larger corporate clients – I knew full well that this omission would eventually bite me in the ass. There is just too much process and approval that goes into decentralizing content creation for it not to.

And so a few years back – while working on a site for a large hospital I got the email I had been dreading. It was days before the launch and our client reached out to us asking how they submit something for approval.

It literally just hadn’t come up in conversation – and I knew from the tone of the email that this wasn’t something to which I could respond, “Well, erm, EE doesn’t do that.”.

Enter NSM Publish Plus

So I spent a night freaking out – starting to pull together my own little hack to make this work. I resigned myself to the fact that I was probably going to be awake for the next week trying to pull something together to get even the most basic workflow in place.

I was still pretty new to ExpressionEngine and so I didn’t immediately go out searching for an existing addon. But about halfway through building my own I was chatting with someone at a Build Guild about it and they said, “Oh, you mean like Leevi Graham’s NSM Publish Plus?”. I’m pretty sure I dropped the beer in my hand, ran home, installed it and sent Leevi a tweet threatening to hug him if/when I met him in person.

And it was good.

ExpressionEngine 2.0

When ExpressionEngine 2.0 release, I just assumed there would be some kind of workflow in place. No such luck. I waited patiently for NSM Publish Plus 2 to be announced and somewhere around Septemper of last year I couldn’t wait anymore and emailed Leevi. He told me he was planning on developing it, but there was no set launch date.

I wanted nothing more than to avoid the “pit-in-my-stomach” feeling I had the last time I was in a workflow-less environment. But I figured I’d sit tight.

In the Forums

On April 24th of this year, I posted this to the forums. It was sparked by the following quick exchange with @EllisLab.

At least I wasn’t the only person who was a little concerned with this issue.

Better Workflow

You know that feeling which follows you around when you KNOW something is going to come back to haunt you? It’s not an immediate and pressing feeling, but more like “impending doom” if I can quote from Goodfellas.

Today, finally, I can release the knot from my stomach – and send a hearty “thank you” to Electric Labs for creating their new Addon Better Workflow.

I haven’t tried it yet, but when I do – I will certainly follow this post up with my initial reactions. From what I can see in their documentation it looks fantastic.

At the very least, I am certain that Better Workflow will live up to it’s name. Then again, ANY workflow will certainly be better.

Thank You Electric Labs

Launching an addon as critical as Better Workflow be to many future ExpressionEngine builds was almost certainly an exhausting undertaking. So please join me in sending Electric Labs a thank-you tweet for their hard work. And make sure to check out their intro pricing ($15 off right now.)

EECI 2011 - Let Me Buy You a Beer

The only thing I am really looking to get out of this year’s EECI is to put faces to as many of the Twitter/EE Forum/GetSatisfaction avatars as possible. And then, to buy a beer for as many of those new faces as possible.

I’m not planning anything, scheduling anything or expecting anything. My rough agenda looks something like this:

Agenda

  • Hop the Acela from Boston to New York with Kyle Ridolfo (@yaykyle) at around noon on Wednesday the 19th.
  • Staying at the Nu Hotel (@nuhotel) Wednesday & Thursday nights
  • Heading home from Brooklyn after Friday’s session

So that leaves me two full nights to meet (and have a drink with) as many of you as possible. As I mentioned, I’m not really much for making plans as to where I’ll be. I’d much rather just go with the flow and see where that leaves me.

How To Find Me

I’m going to be tweeting the different places I find myself through my personal @michaelwitwicki account. So if you only follow @booyant and want to meet up for a beer – please follow my personal account as well. If possible, hit me with a quick @ telling me you are going to EECI too, so I can follow you back.

Very much looking forward to finally meeting many of you in person.

NavEE 2.2 - Ready for Testing

NavEE 2.2 is just about ready for testing and we’ve got a bunch of improvements, all of which (as per usual) came from awesome NavEE users out there. We really do appreciate and keep track of all the ideas that come in, so please keep ‘em coming.

NavEE 2.2 Features

  • Limit which navs each Member Group can access

  • Limit which templates appear in the Guided Method

  • New parameter (reverse=“true”) which reverses the order of all nav items or breadcrumbs

  • New {count} variable available for {exp:navee:custom} which outputs the count of the current item.

Let Us Know What You Need

I guess the point of this entry is two-fold – first, to announce the new changes in 2.2.0, but more importantly to solicit new ideas from everyone out there. We may not be able to get to all of them straight away, certain requests are big enough to warrant being part of 3.0, where smaller things like the ones listed above can often be knocked out fairly quickly.

We are really committed to continually improving NavEE and we really appreciate the feedback.

Here Beta-tester-tester-tester..

So if anyone out there wants to BETA test 2.2.0 – send me an email with your NavEE license key to its.go.time [at] booyant [.] com.