Supported Fields

Starting with iExpression 1.3 we will be (through the use of the custom iExpression ExpressionEngine module) support custom field groups as configured in ExpressionEngine. It should be noted that whilst we do support some third party fields, and that that list will grow from release to release, we cannot support every field type available.

The table below shows which field types are supported, where they can be downloaded from, and which versions of iExpression and EE work with that field type. Again, in general if we don’t support a field type in a particular version it is because the developer does not support that field type in that version of ExpressionEngine. Users of third-party field types should also let us know if there is a field type they would like us to support, and in many ways this is the most interesting feedback there is.

If you are the supplier of a custom field type, and would like us to include support for it in iExpression we are always delighted to consider new opportunities to improve the scope and applicability of our tool. Please use our contact form to let us know you would like your field type (or types!) to be considered. Before you do this, we would like to request at least the following information:

  • Which versions of ExpressionEngine does your field type support?
  • How many web-sites do you think your field type is used by?
  • Do you have specific requirements on how the field type is presented in iExpression?
  • How is the data stored (for example, is it serialised into a database field)?
  • Would you be interested in any cross promotional activities, and if so what would you like to do?
 

Please note that we simply cannot support every field type that this very productive community produces, and have to focus on the most popular. Even if we cannot add your field-type immediately, please keep us up-to-date with your progress.

Notes

Where there are restrictions for a particular field-type, or something we just think you’ll need to know, you’ll find them detailed here.

Wygwam

Wygwam fields are treated as TextArea fields, and do not offer the same rich text editing facilities. This is something we are considering for both TextArea and other rich-text capable fields, please let us know if this is something you would like us to prioritize!

News & Blogs

	Minor update to iExpression module for #eecms - 1 year, 2 months, 2 days, 3 hours, 43 minutes ago
	There is a small bug in the compatibility checker between the App and the module. We’ve addressed it with a workaround for now. Just go to http://www.rwe-uk.com/iexpression/module and download the latest version to get rid of the warning.
	iExpression 1.4.1 available to download from the App Store now - 1 year, 2 months, 3 days, 4 hours, 14 minutes ago
	We are pleased to announce the immediate availability of iExpression 1.4.1 from the App Store. 1.4.1 is a defect fixing release resolving a number of minor issues and one major one. We should also note that all users should update to the latest version of the module as the two together should resolve all known issues with iExpression.
	Minor bug-fix update to iExpression for #eecms uploaded to App Store - 1 year, 2 months, 4 days, 10 hours, 28 minutes ago
	Just wanted to let you know we’ve just pushed a minor update to the App Store containing a few small bug-fixes. There’s a very small number (less than 4) customers impacted by these, but they are pretty important if you are affected. We’ll let you know when it’s been reviewed and made available.
	iExpression Module updated to 1.4c, all users should update as soon as possible - 1 year, 2 months, 4 days, 11 hours, 56 minutes ago
	The iExpression Module for both ExpressionEngine 1.6.8+ and 2.1+ has been updated to version 1.4c. All users should update to this version as it addresses a number of issues where un-supported field data could be modified. No update to the iExpression App itself is required. The module can be downloaded from the iExpression module page.
	Well that’s a relief, iExpression builds again! - 1 year, 3 months, 3 weeks, 2 days, 3 hours, 14 minutes ago
	Seeing as 4.3 Apps are being approved onto the App Store (see the full story from MacRumors here), we decided it was high time to get some 4.3 testing done. It’s normally a pretty simple process… Get XCode installed. Run tests. Wait. Check Results. Cool. This time… Linker errors… No build. It’s taken all day to figure out what it was (and it’s sooooo tempting to imagine it’s an XCode bug). Anyhow, nerdy short story…. Update github repo’s, rebuild, tweak, rebuild, and eventually ta-da… Just somethings were out of date. How can something be tedious and stressful at the same time? Posted by iExpression