Recently I was asked to build a multi-lingual site that involved each language having its own domain, rather than separate subdomains or subfolders as is often the case. I knew that I would be using ExpressionEngine, I just needed to then decide which multi-lingual add-on would fit the bill.
As you may have noticed, this site has been redesigned recently, and I mentioned in the announcement that I'd talk about some of the work that went into the process. So in this first instalment of what might be a two or three-part series, I'm going to talk about some of what's going on under the hood in (the) ExpressionEngine. In the other parts, I'll cover topics relating to design in general, and aspects of the front-end development. In terms of how sites normally get built, that's a bit backwards, as integrating your design and content into the CMS usually comes last, but most of what I'm going to discuss here relates to Stash, which seems to be a bit of a hot topic at the moment.
Yesterday I was working on the planning of a new site to be built with ExpressionEngine and was wondering about the best way to let editors link to other entries from within the body of an entry they're creating or editing. ExpressionEngine doesn't have this sort of functionality built into it by default so I asked on Twitter to find out if anyone knew of any add-ons that had been created that might do this.
With ExpressionEngine you give your clients a lot of power and flexibility to update the content of their own site, but at some point in a site's life there's going to come a time when changes will be required that the site owner or his/her staff can't do themselves via the control panel. Changes to a logo or other graphical elements of the site, adding new sections or functionality, giving the site a new 'skin' or theme, or completely rebuilding from the ground up will require a designer of developer to get involved.
- The client specifically asked for AJAX to be used.
I've come across a few little solutions/fixes recently to various problems I've encountered when building sites with ExpressionEngine (EE) that I thought it would be worth sharing. A couple of these were tips I picked up from other posters on the EE forums and the third was one I came up with myself to solve a particular problem I had.
Recently I had to add basic shopping cart functionality to a site that had been built with ExpressionEngine (my CMS of choice). “No problem,” I thought; I can use the Simple Commerce Module (SCM), which as the names suggests, is ideally suited to simple ecommerce requirements, and which I had used before on other EE sites.
I just encountered a problem installing the TinyMCE editor on an install of ExpressionEngine – all the files were uploaded correctly and the extension to get it working in ExpressionEngine was uploaded and properly activated, but the editor wouldn't appear in Firefox 2 (other browsers were fine).