Found via webankit the Webform Entity module

The biggest difference is that Webform Entity attaches forms to nodes. Forms does not attach to anything and has no dependencies. IMHO a cleaner approach.


webankit’s picture

Project: Forms (FSE) »

Please collaborate your efforts if possible

scottrigby’s picture

Project: » Forms (FSE)
Version: » 7.x-1.x-dev
lsolesen’s picture

What about entityforms in comparison.

Frans’s picture

I don't know. I think you should ask the maintainer of entityforms.
I see one difference, FSE doesn't have a requirement for entityapi, one of the design goals was to have as little dependencies as possible. Although I must admit that if entityAPI was more mature when I wrote the basics, I probably would have used it.

mesr01’s picture

F.Y.I. I found a quite concise comparison at

scottrigby’s picture

@mesr01 AFAIK there isn't a comparison for D7 formbuilder modules yet. If you're interested in starting one, that would be a handy page to create on g.d.o (and link from each applicable module's projet page):

Kristen Pol’s picture

Title: Has Forms similiair functionality as Webform Entity? » Does the Forms (FSE) module have similar functionality as Webform Entity?
PieterDC’s picture

Thanks for that link mesr01

rooby’s picture

Title: Does the Forms (FSE) module have similar functionality as Webform Entity? » Does the Forms (FSE) module have similar functionality as Webform Entity & Entityforms?

Seems very much like entityforms ( from the description.

Any chance of joining forces with them?

Of all things to have a dependency on I would say the entity api module is not an issue,
because so many other common modules rely on it and it provides useful code that would otherwise be duplicated.

scottrigby’s picture

@rooby is there any functionality in FSE that you would like to see included in Entityforms?

rooby’s picture

Not specifically, I'm just not generally a fan of having two modules that are almost the same if it can be avoided.
It fragments developer resources and helps confuse prospective users.

It's not the end of the world though and I realise that there are many duplicate modules and that's the way it will always be.

Although I'd be happy to be educated about any differences (aside from usage of entity api).

scottrigby’s picture

Assigned: Frans » Unassigned
Category: support » task
Status: Active » Postponed (maintainer needs more info)

@rooby I agree that dman's Open Letter for module maintainers to consolidate is still relevant, even though the contribution model on d.o has changed since then.

Entityform has more development effort behind it, and I know it does things that FSE does not. To me the main question is whether FSE module does anything that Entityform currently does not? I'd suggest outlining those things (as i mentioned last year in #6) and adding issues to the Entityform queue (And track them here). Once those are done - if they're deemed appropriate to include in Entityform (i.e. not marked w'on't fix) - then it would make sense to request changing the FSE project page to recommend using Entityform instead. It doesn't really make sense until all these steps have happened.

I'm going to unassign this so anyone who feels motivated can work on the tasks. I think Frans needs help gathering more info before he can do anything so also marking this ticket as such.

tizzo’s picture

Webform Entity creates a base form out of form fields that can be augmented on a one off basis. This is different then an entity form in that you don't have to create (or reuse) a system wide form for every single field on every single form. System wide forms get loaded into lots of admin UIs and caches and (by default in D7) they also create a new table for every single field. On sites that have hundreds or thousands of one-off forms this becomes a big problem. This is the issue webform was originally created to resolve, however webform fields integrate poorly with views and panels.

Webform Entity attempts to give you the best of both worlds by allowing you to create a base form that has a fixed set of fields and then allowing you to extend that form with webform components on a one-off basis for each of your thousands of variations on the base form.

I hope that helps to clear up webform entity's role.