The Technology Architect will have responsibilities covering many aspects of software development, from maintaining the current code base for ExpressionEngine and CodeIgniter to developing new tools and applications under the direction of the CTO. The Technology Architect will also be required to help keep documentation for products up to date.
The Technology Architect is a full-time position (part-time is also available).
Full job descriptions and qualifications are available on the EllisLab Jobs page.
To apply email jobs at ellislab dot com. Your email will include a formal resume, examples of previous work, and be a showcase of your use of email as a primary communication tool.
]]>Post Permalink or Show Us Your Mug page for details.
]]>Primarily, 1.6.4 brings a number of bug fixes and performance enhancements, continuing to improve and refine existing features. As always, the details of these changes can be found in the Change Log.
Additionally, with the assistance of a dedicated CodeIgniter user, Pascal Kriete, the development team has identified and fixed a potential cross-site scripting vulnerability. No sites are known to have been affected, and the circumstances required to successfully execute an exploit on a live ExpressionEngine installation are quite uncommon. However, it is still a possibility, and therefore this update is recommended for all users.
]]>Stop by the forums and join us in giving Ingmar an official welcome.
]]>You can find all of the details regarding the changes to 1.6.3 in the Change Log, and likewise for Discussion Forum version 2.1.0 in its own Change Log.
Please follow 1.6.3’s Version Update Instructions closely, as well as the Discussion Forum 2.1.0 Update Instructions.
]]>The first is for Code Mechanic, a new development team position:
The Code Mechanic will be responsible for escalated support issues and bug investigation, and will be actively engaged with the community of third party developers. The Code Mechanic will become responsible for maintaining the current code base for ExpressionEngine and all of its First Party Add-Ons. The Code Mechanic will also be required to help keep the User Guide and Add-on documentation up to date.
Code Mechanic is a full time salaried position with benefits.
The second opening is for the Senior Technical Support Specialist position:
The Senior Technical Support Specialist (STSS) is the link between the support staff, the development team, and customer service. The STSS is responsible for ensuring that all support requests are resolved in a timely and expedient manner, and that no issues are missed or left unresolved. This includes properly categorizing issues, following up on open issues, and escalating issues to the development team or customer service as necessary. The STSS will also help manage support related materials (such as the Knowledge Base and wiki), and help identify and create ways to improve our support and customer interactions.
The STSS is a part-time position.
Full job descriptions and qualifications are available on the EllisLab Jobs page.
To apply email jobs at ellislab dot com. Your email will include a formal resume, examples of previous work, and be a showcase of your use of email as a primary communication tool.
]]>If you are live blogging (or just plain blogging) the ExpressionEngine 2.0 Preview please post a link to your blog in this thread to make it easy for the community to find. Thanks!
]]>1. The Database Backup Utility has been disabled in ExpressionEngine. On large databases and certain shared hosting set ups, it was not reliable and had caused a couple notable losses of data for our users. With our development of ExpressionEngine 2.0, we did not have the resources to do a complete rewrite in order to make it more efficient and reliable for every possible situation. And even with a rewrite, its abilities would still have been greatly limited by the hosting environment. We still strongly encourage you to backup your database regularly and always before an upgrade using a tool like phpMyAdmin or a service provided by your web host.
2. Due to a certain Chief Technology Officer being absentminded, our Copyright sprinkled throughout the program was not updated to include the year 2008. Who knew the New Year was coming up so fast in mid-November?
3. Thanks to the assistance of one of our users, we discovered within ExpressionEngine a possible XSS vulnerability caused by some old code for a feature removed back in ExpressionEngine 1.2. We have removed that code in this version and while it has never been known to be exploited, we suggest everyone update to this version to insure that it never will be.
Read more about 1.6.2 in the Change Log for more details.
Make sure to follow the Version Update Instructions closely.
]]>