All entries posted in 2011
Stefan Rechsteiner reminded me with his tweet that today, December 5th, is the day that EE1 is no longer offered as a license option when you buy ExpressionEngine. Almost 2 years to the day, EllisLab released the ExpressionEngine 2 Public beta. It is certainly due time to retire the old and focus solely on the new.
The blog post last month from EllisLab with the detail has all the information you’ll need. Including important bits:
If you absolutely must start projects on EE 1.x, please email sales and we’ll work out a solution for you.
Please note that if you already own ExpressionEngine 1.x, download access will not be affected by this change.
Of course, support isn’t gone immediately but it won’t be around forever:
Second, as of April 23rd 2012, ExpressionEngine 1.x will no longer be publicly supported. If you have mission critical projects that need support, we’re happy to continue supporting EE 1.x through private & enterprise support contracts.
Our friends (and long time advertiser on the site) Pixel & Tonic are hiring a PHP Developer on a contract-to-hire basis. Do you love their add-ons and want to help make them better? Well, time to spit shine your resume and apply for the position.
Pixel & Tonic is looking for PHP developer who’s a diehard fan of ExpressionEngine and CodeIgniter to help us develop and support our ExpressionEngine add-ons.
Make sure you have great PHP chops and experience developing for EE. Is that you? Apply for the job.
Everyone’s favorite add-on developer with the last name Lewis, Stephen Lewis, says it’s important for add-on developers to include hooks in their add-ons to allow for custom extensions.
Not all feature requests are created equal. Some are extremely insightful and far-reaching, and improve the add-on in ways you never imagined. Most are narrow, case-specific, and don’t belong in the core product.
Extension hooks provide a means of dealing with the latter in a way that doesn’t adversely affect the core add-on.
He continues with an example of his Campaigner add-on and how allowing for custom extensions lets him, in his own words, abdicate responsibility, for special features or customizations that a developer might need for their project.
It’s well known that if you don’t change your member profile trigger word from the default of “member,” that anyone can browse to your site and see a list of members.
This recently came up again in a tweet from Ryan Masuga and what followed were some good suggestions on what to do make the issue of inadvertently exposing your member list go away.
(My favorite is AJ Penniga’s highly technical solution to the problem.)
Read a full list of the suggestions
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.
Oliver Lindberg at .net magazine compiled a fun list of potential gifts for yourself or your favorite web designer. Or maybe your favorite writer at your favorite publication on ExpressionEngine.
We’ve asked some of the industry’s leading designers to recommend their favourite Christmas gifts. So if you’re still stuck and don’t know what to get for your geek friends, here are more than 50 gift ideas for your inspiration
Participants included: Paul Boag, our own Fred Boyle, Andy Budd, the wonderful Veerle Pieters and Austinites Trent Walton and Tim Van Damme.
My favorite? The educational mug set suggested by Meagan Fisher.
Read the entire guide: The web designers’ gift guide 2011
King of the Parse Order, Low Schutte, digs up an interesting example where an EE conditional isn’t treated as you might expect. Low skirts around the issue with a preload replace variable. Sneaky, sneaky.
I won’t spoil it here, so first check out the code that Low posted as a gist and then read his explanation below it. But, try to figure it out on your own first before looking at the answer.
Think you know variables? Think again! EE Podcast’s 57th episode, All About Variables, tackles one of the most used and integral parts of ExpressionEngine. We talk native functionality, touch on optimization, as well as the the variety of third-party add-ons that make the control panel interaction more user-friendly and development a lot more efficient.
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
In an announcement on the ExpressionEngine blog, EllisLab CEO Leslie Camacho talked about the EE Reactor project and the people involved. Some of this was announced previously at the EECI conference last month in Brooklyn. Leslie also announced that the team already has code ready for an upcoming release of EE:
As of the time of publication, the EE Reactor Team has nine confirmed contributions scheduled for release in EE 2.4 (late January).
The team is focused on “code that makes life better for the EE dev community.” It’ll be interesting to see what they have planned. I suspect that the tweaks made are directly related to problems those developers have run into while working on client projects at their respective agencies or while writing add-ons.
Greg Ferrell, Leevi Graham, Brian Litzinger, Jack McDade, Erik Reagan and Rob Sanchez are all members of the team.
I look forward to seeing how this new experiment works out and hopefully I can get some of the members to share their experiences working on the team and code after the 2.4 release is out.
- Get Thumbnail (for EE2) by Johan Strömqvist
The “Get thumbnail” plugin let’s you get the path to any autogenerated thumbnail from a default “File” field within your channel entries tag that you’ve defined yourself.
- Export It ($, for EE2) by mithra62 (Eric Lamb)
The goal of Export It is to allow ExpressionEngine developers the ability to take their data out of ExpressionEngine. Export It does this through 2 unique tools; the CP module and the REST API.
- Affiliator ($, for EE2) by Chris Newton (BarrettNewton.com)
Add affiliate marketing capabilities to your ExpressionEngine website. Tracks payments and conversions, allows you to set the commission rate of each affiliate, and pay affiliates via PayPal MassPay with the click of a button. Includes template tags for affiliate account management, payment history, and current unpaid commission. Supports CartThrob2, Brilliant Retail and Simple Commerce.
- Profile:Edit ($, for EE2) by Chris Newton (BarrettNewton.com)
ExpressionEngine member data is now insanely easy to manage and edit! Store & edit member profile data directly in ExpressionEngine Channel entries, with all of the power that channels provide. Administrative privileges, custom fields, SafeCracker forms, and getting to ditch the troublesome member templates and tags. Super easy and leverages what you already know and love.
- Disable Template Editor (for EE2) by Jesse Bunch
Makes the ExpressionEngine template editor read-only for templates under source control.
The king of the EE parse order, Low Schutte, has dazzled us once again with a great way to leverage the EE parse order to make your templates even more flexible and reusable than you thought possible. What do you get when take Snippets, Preload Replace Variables and the Parse Order? Super flexible templates that don’t have the overhead of embed templates. That’s what.
According to EE’s parse order, snippets are parsed first, before preload replace variables. These, in turn, are parsed before plugin and module tags, so both can be used as early parsed variables. This combination makes it possible to change the content of your snippet on a per template basis. Much like embeds and embed variables, but without the performance hit.
A series of Preload Replace Variables set your template values and then the snippet just uses those variables to pull in the right data. Read the entire blog post from Low (or, if you’re like me, read it twice) to get all of the details, including some sample code.
Jesse Bunch describes a problem that you’ve probably faced before. You have a great workflow set up with Git, SVN or another VCS and then someone goes into the EE Control Panel and edits the templates, completely bypassing the workflow.
Obviously, this is a huge problem because our production severs don’t commit changes back to the repository for obvious reasons. So when someone edits a template on the production server, nobody knows it happened and when we deploy a change to that template, it is very likely that the change will be lost or our working copy will become out of sync (depending on how we deploy the project).
To help fix this problem, Jesse created an extension that disables the template editor in the Control Panel.
This extension makes the templates and template groups in EE read-only. It doesn’t affect things like synchronization, PHP input/output parsing, and access control.
You can get the extension at Devot-ee. It’s only available for EE2 right now (although a EE1 version is planned) and is free to download.
Today the United States Congress begins hearings on a new proposed law called the PROTECT IP Act (how does it work?). This law is aimed at protecting intellectual property and preventing copyright infringement online. Without surprise to you I’m sure, this law has been spearheaded by the entertainment industry. The same people that tried to kill VCRs, MP3 players, DVRs and more. The same people that sued grandmothers and little kids.
To make it worse, the law is also supported by politicians who, to be frank, don’t know shit about how the internet works, what makes it so successful and just how damaging an over-reaching law like PROTECT IP would be.
This video sums it up nicely:
I’m in a unique position because I would actually benefit from this law. The ExpressionEngine training videos I create at Mijingo are widely pirated online. Fighting the people that pirate the videos (and, sadly, those that do are part of our community) would be a full-time job. So, I choose to do everything I can to protect the videos without ruining the experience for legitimate customers (or treating them like criminals). That’s why my videos don’t have DRM or a complicated scheme to protect them from being copied.
I don’t think, however, that it’s worth ruining and censoring the Internet to prevent my videos from being pirated. And that is exactly what the entertainment industry wants to see happen; a nuclear option to protect their latest cream puff blockbuster movie from being pirated online or streamed in parts on video sites.
For those of you who live in the United States, please take the time to learn more about these proposed laws and how they can hurt you and the Internet.
The annual A List Apart Web Design Survey is up and waiting for you to share your experience as a web professional. The goal of the survey is to gather as much information about our industry and the people who make it work. The data is analyzed and the findings will be presented in a future issues of A List Apart. Additionally, the data is released its raw form, so anyone can take it and make cool graphics, charts or–most importantly–teach us something new about our industry.
Here’s the pitch from the ALA article about why you should take the survey:
Just who are these people who make websites? What are their titles? What kind of education have they had? What skills do they possess and what skills do their employers imagine they possess? How do they stay current? How happy are they? How well are they paid? How mobile are they, creatively and economically?
That’s where you come in. You are the world’s foremost expert on the topic of you. Only you know how you do what you do, who you do it with, how well you do it, and how satisfying (or otherwise) you find it
Take the survey now.