Will the Real SAEF Please Stand Up?
It’s no secret that the release of ExpressionEngine 2 revealed some limitations in our current Stand Alone Entry Form (SAEF). In large part, this is due to our new approach to custom fields and the resulting variety and potential complexity of new field types. Believe me, we are as frustrated with it as you are.
The current approach just isn’t cutting it and putting band-aids on the code isn’t a ‘fix’ we find acceptable. We also have to acknowledge that Add-ons have been needed in the past to get the most out of even the 1.x version. So we’ve decided to step back, take a deep breath, and look at the SAEF with fresh eyes.
Here’s where we need your help, and where you can help us shape the next incarnation of the SAEF.
Our short list of goals:
- Third-party field type support
- Allow editing entries from the SAEF
- Easier to customize the form into your site’s design.
We have a few things to think about in particular: What obstacles do you find when trying to ‘skin’ the SAEF? How do you typically use CSS to style a form? Do you prefer more required template tags or more predefined markup? How do you feel about adding your own javascript interactions? Have examples of complex issues where the SAEF (1.x or 2.x) lets you down? Lay them out. The more information we have the better.
We can’t promise that each and every request here is going to make it into the final product, but rest assured that we will consider every suggestion.
Until next time…
