All entries filed under “What They're Saying About EE”
This is a on-going series of entries where I highlight EE experiences.
I believe the proper term is tweakalicious.
Isn’t that why you use ExpressionEngine? Because of its extensibility and relative ease of use when developing add-ons?
From EllisLab CEO Leslie Camacho:
And that makes for a better community, too.
This is a on-going series of entries where I highlight EE experiences.
Kaboom.
This is a on-going series of entries where I highlight EE experiences.
Probably why no one has done a news site for the community either.
Update: In the comments, Adam points out the this was probably meany literally, not as a snark. We regret the jump to conclusions.
This is a on-going series of entries where I highlight EE experiences.
I think the public member profiles should just be eliminated completely. Who uses them?
(Here’s a good tip for setting the trigger word)
This is a on-going series of entries where I highlight EE experiences.
This is a on-going series of entries where I highlight EE experiences.
Excellent advice!
This is a on-going series of entries where I highlight EE experiences.
OK, no more #eecms tweets, I losing friends.
Asher Awelan via Twitter
Keep tweeting away using the hashtag. We don’t mind.
This is a on-going series of entries where I highlight EE experiences.
A lot of agencies still think that #eecms is poor for SEO, e-commerce, rich media etc. Time do something about that!
Hambo via Twitter
Take every opportunity to educate them.
Any #eecms 1.x to 2.x upgrade that doesn’t kill me makes me stronger. #fairytalesitellmyself
Mr. Wilson via Twitter
Client’s in-house dev: “I bought a personal license of EE over the weekend and have become mildly obsessed. I envy your expertise.” #eecms
Jeff Claeson via Twitter
This is a on-going series of entries where I highlight EE experiences.
Another win for #eecms over Wordpress. I especially love helping out a fellow dev make the transition. Pro bono evangelism is the best!
Christopher Kennedy via Twitter
This is a on-going series of entries where I highlight EE experiences.
Why the hell is the Emoticon Module still installed by default!
Justin Long via Twitter
I heard that Kelsey Martens pays good money to EllisLab for that module to remain installed by default. Just a rumor though.
This is a on-going series of entries where I highlight EE experiences.
eecms allows one to delete the date tab when customizing the publish layout and then tells us it’s required when saving changes. Backwards!
Pixogee via Twitter
I ran into this just this weekend running EE 2.2.2 and it certainly was frustrating. It only took me a minute to figure out what was going on. To fix the problem I had to drag the entry date field back into one of the tabs.
I was certain that someone had already filed this bug but I wasn’t able to find a report. So I filed a bug.
This is a on-going series of entries where I highlight EE experiences.
If we had built a content management system, this would have been it!
Deckchair via their blog
(They say many more nice things about EE in the blog post.)
This is a on-going series of entries where I highlight EE experiences.
Dear @ellislab, the three pages of “New” bug reports is becoming worrisome. #eecms #development
Paul Burdick via Twitter
Paul’s tweet set off a small discussion on Twitter about the bug list, some talk of “perspective” and even a comparison of EE to a situation Drupal.
I looked through the list and there are definitely some bugs that haven’t been assigned that were filed back in August. It’s hard to say what this means, if anything, because I don’t have insight into how the development team at EllisLab handles bug reports and assignments.
There are definitely some bugs from EE 2.2.1 that weren’t fixed in EE 2.2.2. But let’s not forget that EE 2.2.2 was a maintenance update to fix an issue with how new member accounts are created. It only includes a small set of bugs compared to the previous EE 2.2.1. All that to say, I’m hopeful that the next release will contain an entire batch of fixes to address some of the minor yet annoying issues from EE 2.2.1 and previous.
What’s your take? Do you feel like you’re bug reports aren’t being addressed or that you’re fighting the same bugs in every release? Or are things running smoothly? My experience has been that EE 2.2.2 is a very nice release and has been running great for me at mijingo.com (Publish Layouts notwithstanding).
A Triple Edition Special
This is a on-going series of entries where I highlight EE experiences.
ExpressionEngine should be easier to update…at least to the latest build.
hungrysquirrel via Twitter
Not only that but EE should fix my morning Americano, too!
Okay, seriously, I do agree. Automatic build updates would be spectacular. For now, however, I’ll take a delta updates.
It’s getting harder and harder for me to hold my tongue over some of the “whine” that gets posted to #eecms. I’m holding it though! #winning
Anna Brown via Twitter.
Last week I had an internal debate about what’s better: the whining or the spam in the #eecms tag stream. The answer is: neither. The worst is the use of the #eecms tag to tear down and rant against other people’s work. That, I think, is the biggest threat. No one wants to play in a sandbox full of cat turds.
Okay, now let’s swing it back around to something positive.
Just gave a 1 1/2 hour ExpressionEngine content admin training session to a client. “This is incredible… way beyond what we were expecting.”
Ryan James via Twitter
If you build a site with care using ExpressionEngine, this is the reaction you’ll get. My mantra is: Easy for the client, not for me. Nice work, Ryan!