Hi !
It has been a while I am around here and I always get the same issues when I try to export webforms in an industrial way.
UUID and Node export provide some workarounds to put the webform in code but they are not really environment-proof has they always have to deal with a lot of numeric identifiers.
(Pro tip : you can also use the machine name in a lot of hooks to help you making really custom webforms)
So, tired, I made a little module to make usage of machine names in webforms and build a custom Features integration using them to replace all common numeric identifiers. It is currently in a sandbox because I would love to have a kind of webforms' king (or queen) validation about my model.
I hope this will suit you.
Thank you !
Comments
Comment #1
quicksketchOverall it looks like a good implementation. I haven't installed it locally, but I like the general approach you've taken here. I haven't seen similar modules with this kind of functionality, and it's been regularly requested (see #837594: Give a machine name to webform and use it for theming, exports, features, form IDs, etc.). I'd recommend you promote it to a full project if there aren't any similar modules out there and possibly write up a child page under the Webform handbook: http://drupal.org/handbook/modules/webform
Comment #2
DuaelFrThank you comforting me !
I just released a beta version including some of my "can't-sleep" ideas.
Feel free to let me some comments in the issue list.
I will work for a 4.x port when I will find a bit of time.